The previous limits were estimated locally in a single step
basead on bound values, however it was not correct since
when given certain scatterlist the function nx_build_sg_lists
was consuming more sg entries than allocated causing a
memory corruption and crashes.
- This patch removes the old
Hi!
> When IOAPIC is disabled, acpi_gsi_to_irq() should return gsi directly
> instead of calling mp_map_gsi_to_irq() to translate gsi to IRQ by IOAPIC.
> It fixes https://bugzilla.kernel.org/show_bug.cgi?id=84381.
>
> Reported-by: Thomas Richter
> Signed-off-by: Jiang Liu
> Cc:
The previous limits were estimated locally in a single step
basead on bound values, however it was not correct since
when given certain scatterlist the function nx_build_sg_lists
was consuming more sg entries than allocated causing a
memory corruption and crashes.
This patch removes the old logic
On 10/24/2014 05:08 AM, Thomas Gleixner wrote:
> On Sun, 12 Oct 2014, Qiaowei Ren wrote:
>> +/*
>> + * Go poke the address of the new bounds table in to the
>> + * bounds directory entry out in userspace memory. Note:
>> + * we may race with another CPU instantiating the same
The previous limits were estimated locally in a single step
basead on bound values, however it was not correct since
when given certain scatterlist the function nx_build_sg_lists
was consuming more sg entries than allocated causing a
memory corruption and crashes.
This patch removes the old logic
Hello.
On 10/28/2014 07:35 PM, Antoine Tenart wrote:
Move the usb_otg member from struct usb_phy to struct ci_hdrc. Rework
You're not reallky touching 'struct usb_phy'. ;-)
its initialization taking in account this modification.
Signed-off-by: Antoine Tenart
Acked-by: Peter Chen
On Tue, 28 Oct 2014 12:58:27 -0400
Jason Cooper wrote:
> At the risk of upsetting the apple cart, I'd prefer we downplay anything
> that walks down the path of gamification (by focusing on credit).
>
> As best anyone has ever explained it to me, the Acked-by, Reviewed-by,
> etc are there to
On Tue, 28 Oct 2014 22:03:02 +0530
Pramod Gurav wrote:
> Michael had suggested to do away with this function if not being used.
> Good to go?
>
> Michale can you provide acked-by?
Yes, this looks good.
Acked-by: Michael Büsch
> On Wed, Oct 1, 2014 at 10:58 PM, Pramod Gurav
> wrote:
> > This
This patch set fixes the follow issues in NX crypto driver:
- Bound limit issue that causes a memory crash
- SHA concurrence issue
- IV vector fix with the correct bit order
- NX CCM does not support keys larger than 128 causing
crashes in fips mode.
Leonidas S. Barbosa (9):
Moving
On Tue, Oct 28, 2014 at 04:59:45PM +0300, Timofey Titovets wrote:
> 2014-10-28 16:31 GMT+03:00 Marco A Benatto :
> > Hi All,
> >
> > I'm not mantainer at all, but I've being using UKSM for a long time and
> > remember
> > to port it to 3.16 family once.
> > UKSM seems good and stable and, at
On Tue, Oct 28, 2014 at 08:00:45PM +0300, Max Filippov wrote:
> On Tue, Oct 28, 2014 at 6:42 PM, Mark Brown wrote:
> > Then this just shouldn't exist at all, adding Kconfig entries for all
> > the simple-card devices would defeat the point of having simple-card
> > which is why we don't do it
Can these patches be split up? They're hard to review as-is. e.g., the
changes to page allocation look they could be split out.
On 27/10/14 14:52, Juergen Gross wrote:
> Early in the boot process the memory layout of a pv-domain is changed
> to match the E820 map (either the host one for Dom0
On Tue, 2014-10-28 at 13:32 -0400, Steven Rostedt wrote:
> On Tue, 28 Oct 2014 10:27:40 -0700 Joe Perches wrote:
> > On Tue, 2014-10-28 at 12:05 -0400, Steven Rostedt wrote:
> > > I would like to get this done before I do my merge of trace_seq and
> > > seq_file, but I'm thinking I may have to do
On Tue, Oct 28, 2014 at 10:32 AM, Steven Rostedt wrote:
> On Tue, 28 Oct 2014 10:27:40 -0700
> Joe Perches wrote:
>> On Tue, 2014-10-28 at 12:05 -0400, Steven Rostedt wrote:
>> > On Tue, 28 Oct 2014 08:57:57 -0700
>> > Joe Perches wrote:
>> >
>> > > On Tue, 2014-10-28 at 11:13 -0400, Steven
Signed-off-by: Eric W. Biederman
---
man2/umount.2 | 18 ++
1 file changed, 18 insertions(+)
diff --git a/man2/umount.2 b/man2/umount.2
index aea39d8306fe..a0120b2fc811 100644
--- a/man2/umount.2
+++ b/man2/umount.2
@@ -97,6 +97,24 @@ Don't dereference
if it is a symbolic
On Tue, 28 Oct 2014 10:27:40 -0700
Joe Perches wrote:
> On Tue, 2014-10-28 at 12:05 -0400, Steven Rostedt wrote:
> > On Tue, 28 Oct 2014 08:57:57 -0700
> > Joe Perches wrote:
> >
> > > On Tue, 2014-10-28 at 11:13 -0400, Steven Rostedt wrote:
> > > > I'm going to be working on changes to remove
"Michael Kerrisk (man-pages)" writes:
> Hi Eric,
>
> I'm still hoping for a revised patch from you in the light
> of Andy's comments and question.
Andy's concerns are orthogonal to my original patch, and
actually have nothing to do with MNT_DETACH.
Which was my point but here I will send a
On Mon, Oct 20, 2014 at 04:24:27PM -0200, Henrique de Moraes Holschuh wrote:
> Over time, grepping for that information on reports and logs all over the
> net has helped me a great deal.
Helped you how, for what? I still am searching for a justification to
bother the user with the fact that her
[Oops, re-send remembering to turn on plaintext mode -- sorry]
On Mon, Oct 27, 2014 at 6:47 PM, Andy Lutomirski wrote:
> On Mon, Oct 27, 2014 at 11:03 AM, David Drysdale wrote:
>> On Wed, Oct 22, 2014 at 7:44 PM, Andy Lutomirski wrote:
>>> On Wed, Oct 22, 2014 at 4:44 AM, David Drysdale
On Tue, 28 Oct 2014, H. Peter Anvin wrote:
> On 10/28/2014 04:06 AM, Thomas Gleixner wrote:
> >>
> >> The available address we can use is lower than FIXADDR_BOOT_START. So
> >> We will set the kmap boundary below the FIXADDR_BOOT_START, if configure
> >> the high memory.
> >>
> >> If we configure
On Tue, 2014-10-28 at 12:05 -0400, Steven Rostedt wrote:
> On Tue, 28 Oct 2014 08:57:57 -0700
> Joe Perches wrote:
>
> > On Tue, 2014-10-28 at 11:13 -0400, Steven Rostedt wrote:
> > > I'm going to be working on changes to remove the return value of
> > > seq_printf() and friends.
> >
> > I'm
On Tue, 28 Oct 2014 10:14:09 -0700
Brian Norris wrote:
> On Tue, Oct 28, 2014 at 12:05:52PM -0400, Steven Rostedt wrote:
> > On Tue, 28 Oct 2014 08:57:57 -0700
> > Joe Perches wrote:
> >
> > > On Tue, 2014-10-28 at 11:13 -0400, Steven Rostedt wrote:
> > > > I'm going to be working on changes
On 2014-10-28 11:22, Sudip Mukherjee wrote:
On Thu, Oct 23, 2014 at 10:16:48PM +0530, Sudip Mukherjee wrote:
while compiling integer err was showing as a set but unused variable.
elevator_init_fn can be either cfq_init_queue or deadline_init_queue
or noop_init_queue.
all three of these
On 10/28/2014 04:06 AM, Thomas Gleixner wrote:
>>
>> The available address we can use is lower than FIXADDR_BOOT_START. So
>> We will set the kmap boundary below the FIXADDR_BOOT_START, if configure
>> the high memory.
>>
>> If we configure the high memory, the vmalloc reserve area should end
>>
I see no point in having an unusable read-only page sitting at
0xff60 when vsyscall=none. Instead, skip mapping it and
remove it from /proc/PID/maps.
I kept the ratelimited warning when programs try to use a vsyscall
in this mode, since it may help admins avoid confusion.
On Thu, Oct 23, 2014 at 10:16:48PM +0530, Sudip Mukherjee wrote:
> while compiling integer err was showing as a set but unused variable.
> elevator_init_fn can be either cfq_init_queue or deadline_init_queue
> or noop_init_queue.
> all three of these functions are returning -ENOMEM if they fail to
vsyscall_64.c is just vsyscall emulation. Tidy it up accordingly.
If my comment editing offends anyone, let me know and I can fix it.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/vsyscall_64.c | 51 +++
1 file changed, 18 insertions(+), 33
This adds CONFIG_X86_VSYSCALL_EMULATION, guarded by CONFIG_EXPERT.
Turning it off completely disables vsyscall emulation, saving ~3.5k
for vsyscall_64.c, 4k for vsyscall_emu_64.S (the fake vsyscall
page), some tiny amount of core mm code that supports a gate area,
and possibly 4k for a wasted
Now that arch/x86/kernel/vsyscall_64.c contains only vsyscall
emulation code, clean it up and make it optional.
Patch 1 makes vsyscall=none work be a bit more self-consistent: it
actually removes the fake vsyscall page instead of just segfaulting
anyone who tries to use it.
Patch 2 is pure
The comma after --no-includes makes coccinelle to not run the script:
/usr/bin/spatch -D report --very-quiet --no-show-diff --cocci-file
./scripts/coccinelle/misc/bugon.cocci --no-includes, --include-headers --patch
. --dir drivers/media/platform/coda/ -I ./arch/x86/include -I
From: Joerg Roedel
Now that the mmu_notifier_invalidate_range() calls are in
place, add the call-back to allow subsystems to register
against it.
Reviewed-by: Andrea Arcangeli
Reviewed-by: Jérôme Glisse
Signed-off-by: Joerg Roedel
---
include/linux/mmu_notifier.h | 37
Hi Lars-Peter,
On Tue, Oct 28, 2014 at 6:58 PM, Lars-Peter Clausen wrote:
> On 10/27/2014 08:07 PM, Max Filippov wrote:
>
> A few minor things.
>
> [...]
>
>> +static irqreturn_t xtfpga_i2s_interrupt(int irq, void *dev_id)
>> + if (tx_active) {
>> + if (i2s->tx_fifo_high <
For the `COMEDI_LOCK`, `COMEDI_UNLOCK`, `COMEDI_CANCEL`, and
`COMEDI_POLL` ioctls the third argument is a comedi subdevice number.
This is passed as an `unsigned long`, but when it is passed down to the
ioctl command-specific handler functions `do_lock_ioctl()`,
`do_unlock_ioctl()`,
On Tue, Oct 28, 2014 at 9:05 AM, Marc Zyngier wrote:
> On 28/10/14 15:41, Bjorn Andersson wrote:
>> On Sat, Oct 25, 2014 at 2:22 AM, Marc Zyngier wrote:
[..]
>> In the Qualcomm pmic we have two interrupt status registers
>> "interrupt" and "real-time". I think the "interrupt" status register
>>
From: Joerg Roedel
Changes V3->V4:
* Rebased to v3.18-rc2
* Updated patch description and some comments
Changes V2->V3:
* Rebased to v3.17-rc4
* Fixed compile error because pmdp_get_and_clear_notify was
missing
Changes V1->V2:
* Rebase to v3.16-rc7
* Added call of ->invalidate_range to
From: Joerg Roedel
This notifier closes an important gap in the current
mmu_notifier implementation, the existing call-backs are
called too early or too late to reliably manage a non-CPU
TLB. Specifically, invalidate_range_start() is called when
all pages are still mapped and
From: Joerg Roedel
Add calls to the new mmu_notifier_invalidate_range()
function to all places in the VMM that need it.
Reviewed-by: Andrea Arcangeli
Reviewed-by: Jérôme Glisse
Signed-off-by: Joerg Roedel
---
include/linux/mmu_notifier.h | 41 +
Various drivers implement architecture and/or device specific means to
power off the system. For the most part, those drivers set the global
variable pm_power_off to point to a function within the driver.
This mechanism has a number of drawbacks. Typically only one scheme
to remove power is
On Tue, Oct 28, 2014 at 12:05:52PM -0400, Steven Rostedt wrote:
> On Tue, 28 Oct 2014 08:57:57 -0700
> Joe Perches wrote:
>
> > On Tue, 2014-10-28 at 11:13 -0400, Steven Rostedt wrote:
> > > I'm going to be working on changes to remove the return value of
> > > seq_printf() and friends.
> >
> >
This commit:
commit 783c8f4c84451bc444e314a71b447239c6ef6fd9
Author: Peter De Schrijver
Date: Thu Jun 12 18:36:37 2014 +0300
soc/tegra: Add efuse driver for Tegra
introduced a fuse driver in drivers/soc. While at it, an unused file
drivers/misc/fuse/Makefile sneaked in, apparently as a
On Tue, 28 Oct 2014, Arnd Bergmann wrote:
> On Tuesday 28 October 2014 16:43:42 Thomas Gleixner wrote:
> > >
> > > +time64_t ktime_get_real_seconds(void)
> > > +{
> > > + time64_t seconds;
> > > + struct timekeeper *tk = _core.timekeeper;
> > > + unsigned int seq;
> > > +
> > > +
On Tue, 2014-10-28 at 08:58 +0100, Krzysztof Kozlowski wrote:
> On pon, 2014-10-27 at 11:57 -0700, Kamal Mostafa wrote:
> > 3.13.11.10 -stable review patch. If anyone has any objections, please let
> > me know.
> >
> > --
> >
> > From: Krzysztof Kozlowski
> >
> > commit
On Tue, 2014-10-28 at 08:58 +0100, Krzysztof Kozlowski wrote:
> On pon, 2014-10-27 at 11:57 -0700, Kamal Mostafa wrote:
> > 3.13.11.10 -stable review patch. If anyone has any objections, please let
> > me know.
> >
> > --
> >
> > From: Krzysztof Kozlowski
> >
> > commit
On Tue, Oct 28, 2014 at 05:39:13PM +0100, Lars-Peter Clausen wrote:
> On 10/28/2014 05:04 PM, Mark Brown wrote:
> >Is that going to play nicely with the fact that the interrupt can be
> >shared and the desire to (AFAICT) do NAPI style stuff with the interrupt
> >disabled for long periods?
>
On Tue, Oct 28, 2014 at 04:25:35PM +, Linus Torvalds wrote:
> On Tue, Oct 28, 2014 at 9:07 AM, Will Deacon wrote:
> > I was certainly seeing this issue trigger regularly when running firefox,
> > but I'll need to dig and find out the differences in range size.
>
> I'm wondering whether that
On Mon, 27 Oct 2014, Juergen Gross wrote:
> At the moment there are a lot of places that handle setting or getting
> the page cache mode by treating the pgprot bits equal to the cache mode.
> This is only true because there are a lot of assumptions about the setup
> of the PAT MSR. Otherwise the
On Thu, Oct 23, 2014 at 6:26 PM, Heiko Stübner wrote:
> Am Dienstag, 21. Oktober 2014, 10:47:34 schrieb Doug Anderson:
>> Just like in (529301c pinctrl: samsung: Parse pin groups before
>> calling pinctrl_register()), Rockchip also needs to parse pin groups
>> earlier to make hogs work.
>>
>>
I believe commit 0d961b3b52f566f823070ce2366511a7f64b928c made a mistake
while correcting a bug.
It was correct to fix (which applies only in dual_emac mode):
@@ -554,7 +554,7 @@ static void cpsw_set_promiscious(struct net_device *ndev,
bool enable)
* common for both the
On Thu, Oct 23, 2014 at 3:23 PM, Sascha Hauer wrote:
> Most iomux controllers allow a configuration per pin. These currently
> have no common device tree binding. There are many different SoC
> specific bindings for this class of iomux controllers. Some controllers
> artificially group pins
On 10/28/2014 05:41 PM, Pramod Gurav wrote:
Hi Ulf,
Is this good to go?
Uhm, no it isn't. pxav3 needs a special set_uhs_signaling handler,
remove the standard sdhci provided instead.
Sebastian
On Mon, Sep 29, 2014 at 6:55 PM, Pramod Gurav
wrote:
This fixes below sparse warning:
On some chips it is possible to access the switch eeprom.
Add infrastructure support for it.
Signed-off-by: Guenter Roeck
---
v3:
- Fix bug seen if devicetree is enabled; eeprom-length property is
attached to switch devicetree node, not to dsa node.
v2:
- Add support for configuring switch
On Tue, Oct 28, 2014 at 6:42 PM, Mark Brown wrote:
> On Mon, Oct 27, 2014 at 11:38:53PM +0300, Max Filippov wrote:
>> On Mon, Oct 27, 2014 at 10:32 PM, Mark Brown wrote:
>> > On Mon, Oct 27, 2014 at 10:07:05PM +0300, Max Filippov wrote:
>
>> >> +config SND_SOC_XTENSA_XTFPGA
>> >> + tristate
On Tue, Oct 28, 2014 at 09:04:51AM -0400, Jonathan Corbet wrote:
> On Fri, 14 Feb 2014 12:30:01 +0300
> Dan Carpenter wrote:
>
> > -If this patch fixes a problem reported by somebody else, consider adding a
> > -Reported-by: tag to credit the reporter for their contribution. Please
> > -note
> On 10/28/2014 08:38 AM, Michal Nazarewicz wrote:
>> Like Laura wrote, the message is not (should not be) a problem in
>> itself:
>
> [...]
>
>> So as you can see cma_alloc will try another part of the cma region if
>> test_pages_isolated fails.
>>
>> Obviously, if CMA region is fragmented or
On Tue, Oct 28, 2014 at 04:10:26PM +0100, Linus Walleij wrote:
> On Fri, Oct 17, 2014 at 3:53 AM, David Cohen
> wrote:
> > On Thu, Oct 16, 2014 at 11:01:23AM +0300, Mika Westerberg wrote:
>
> >> In an ideal world, yes. However, the reality has shown that BIOS/FW gets
> >> these wrong and we need
The dsa core now supports reading from and writing to a switch EEPROM
if connected. Describe optional devicetree property indicating that
an EEPROM is present and its size.
Signed-off-by: Guenter Roeck
---
v3:
- eeprom-length property is attached to switch devicetree node,
not to dsa node.
v2:
On Sat, 2014-10-25 at 14:42 +0800, Wang Nan wrote:
> This patch use previous introduced checker on store instructions,
> record stack consumption informations to arch_probes_insn. With such
> information, kprobe opt can decide how much stack needs to be
> protected.
>
> Signed-off-by: Wang Nan
At Tue, 28 Oct 2014 17:39:13 +0100,
Lars-Peter Clausen wrote:
>
> On 10/28/2014 05:04 PM, Mark Brown wrote:
> > On Tue, Oct 28, 2014 at 04:58:24PM +0100, Lars-Peter Clausen wrote:
> >> On 10/27/2014 08:07 PM, Max Filippov wrote:
> >
> >>> + if (tx_active) {
> >>> + if (i2s->tx_fifo_high <
Expression haptic->pwm_dev->period * haptic->magnitude is of type 'unsigned
int' and may overflow. We need to convert one of the operands to u64 before
multiplying, instead of casting result (potentially overflown) to u64.
Reported by Coverity: CID 1248753
Signed-off-by: Dmitry Torokhov
---
Since commit 9447057eaff8 ("platform_device: use a macro instead of
platform_driver_register"), platform_driver_register() always overwrites
the .owner field of a platform_driver with THIS_MODULE. This breaks
platform_driver_probe() which uses it from within the platform core
instead of the module
Hi Ulf,
Is this good to go?
On Mon, Sep 29, 2014 at 6:55 PM, Pramod Gurav
wrote:
> This fixes below sparse warning:
> drivers/mmc/host/sdhci-pxav3.c:227:10: warning: Initializer entry defined
> twice
> drivers/mmc/host/sdhci-pxav3.c:232:10: also defined here
>
> by removing duplicate
There are calls which silently set the owner of a module. This is the
preferred way [1], so avoid setting it manually. Currently, we only care
about platform drivers, but there might be more calls to be added later.
[1] https://lkml.org/lkml/2014/10/12/87
Signed-off-by: Wolfram Sang
---
Since platform_register_driver() was converted to set the .owner of a driver,
there was a codepath on which the owner would have been erased. This series
fixes that and adds a warning to prevent such cases go unnoticed in the future.
For consistency, a semantic patch is also added which reports
-- Forwarded message --
From: Rogelio Serrano
Date: Tue, Oct 28, 2014 at 4:40 PM
Subject: Re: A desktop environment[1] kernel wishlist
To: Bastien Nocera
On Tue, Oct 28, 2014 at 12:36 PM, Bastien Nocera wrote:
>
> How do I detect that the screen is visible on a tablet? I
Commit 9447057eaff8 ("platform_device: use a macro instead of
platform_driver_register") introduced a codepath which could result into
drivers having no owner. This went unnoticed for months, so add a
warning in case this happens again somewhere else somewhen.
Signed-off-by: Wolfram Sang
---
Since commit 9447057eaff8 ("platform_device: use a macro instead of
platform_driver_register"), platform_driver_register() always overwrites
the .owner field of a platform_driver with THIS_MODULE. This breaks
platform_create_bundle() which uses it via platform_driver_probe() from
within the
On Tue, Oct 28, 2014 at 5:54 AM, Huang Rui wrote:
> This patch adds disscramble quirk, and it only needs to be enabled at fpga
"disscramble" (in subject and above) is not a real word.
I see that DWC3_GCTL_DISSCRAMBLE is already defined in
drivers/usb/dwc3/core.h even before your patches, so I
On 10/28/2014 05:04 PM, Mark Brown wrote:
On Tue, Oct 28, 2014 at 04:58:24PM +0100, Lars-Peter Clausen wrote:
On 10/27/2014 08:07 PM, Max Filippov wrote:
+ if (tx_active) {
+ if (i2s->tx_fifo_high < 256)
+ xtfpga_i2s_refill_fifo(i2s);
+
On Tue, Oct 28, 2014 at 10:47:42AM +, Mark Brown wrote:
> On Mon, Oct 27, 2014 at 09:26:26PM -0700, Nicolin Chen wrote:
> > On Tue, Oct 28, 2014 at 12:19:04AM +, Mark Brown wrote:
>
> > > It's not a bug, it's not reasonable to default allocations to atomic and
> > > we can't really tell
Move the usb_otg member from struct usb_phy to struct ci_hdrc. Rework
its initialization taking in account this modification.
Signed-off-by: Antoine Tenart
Acked-by: Peter Chen
---
drivers/usb/chipidea/ci.h | 1 +
drivers/usb/chipidea/debug.c | 2 +-
drivers/usb/chipidea/host.c|
This patch adds support of the PHY framework in OTG and keeps the USB
PHY compatibility. Here the only modification is to add PHY member in
the OTG structure, along with the USB PHY one.
Signed-off-by: Antoine Tenart
---
include/linux/usb/otg.h | 3 +++
1 file changed, 3 insertions(+)
diff
This patch modify the generic code handling PHYs to allow them to be
supplied from the drivers. This adds checks to ensure no PHY was already
there when looking for one in the generic code. This also makes sure we
do not modify its state in the generic HCD functions, it was provided by
the driver.
On Tue, 2014-10-28 at 04:16PM +0100, Lothar Waßmann wrote:
> Hi,
>
> Soren Brinkmann wrote:
> > Signed-off-by: Soren Brinkmann
> > ---
> > changes since RFC:
> > - use syscon/regmap to access registers in SLCR space
> > - add pinctrl to zc702 DT
> > - rebase to 3.18: rename enable -> set_mux
This patch adds support of the PHY framework for ChipIdea drivers.
Changes are done in both the ChipIdea common code and in the drivers
accessing the PHY. This is done by adding a new PHY member in
ChipIdea's structures and by taking care of it in the code.
Signed-off-by: Antoine Tenart
---
This patch prepares the introduction of the generic PHY support in the
USB OTG common functions. The USB PHY member of the OTG structure is
renamed to 'usb_phy' and modifications are done in all drivers accessing
it. Renaming this pointer will allow to keep the compatibility for USB
PHY drivers.
Before using the PHY framework instead of the USB PHY one, we need to
move the OTG state into another place, since it won't be available when
USB PHY isn't used. This patch moves the OTG state into the OTG
structure, and makes all the needed modifications in the drivers
using the OTG state.
This patch prepares the introduction of the generic PHY support in the
USB ChipIdea common functions. The USB PHY member of the ChipIdea
structure ('transceiver') is renamed to 'usb_phy', the 'phy' member of
the ChipIdea pdata structure is renamed to 'usb_phy' and modifications
are done in all
The series can be found at:
git://git.free-electrons.com:users/antoine-tenart/linux.git usb-phy
Changes since v6:
- rebased on top of v3.18-rc2
Changes since v5:
- rebased on the latest version of Sergei's series[1]
- fixed one modifiaction made in the wrong patch
Michael had suggested to do away with this function if not being used.
Good to go?
Michale can you provide acked-by?
On Wed, Oct 1, 2014 at 10:58 PM, Pramod Gurav
wrote:
> This change fixes below sparse error:
> drivers/ssb/main.c:94:16: warning: symbol 'ssb_sdio_func_to_bus'
> was not
On 10/28/2014 09:07 AM, Murali Karicheri wrote:
On 10/28/2014 12:06 PM, Murali Karicheri wrote:
On 10/24/2014 01:51 PM, Murali Karicheri wrote:
Now that Keystone PCI driver is merged to v3.18, this patch series
add build options and DTS bindings to enable the driver for Keystone
SoCs.
CC :
On Thu, Oct 23, 2014 at 10:27 AM, Alexandre Courbot wrote:
> This function actually operates on a gpio_chip, so its prefix should
> reflect that fact for consistency with other functions defined in
> gpio/driver.h.
>
> Signed-off-by: Alexandre Courbot
> ---
> Just a consistency change ;
On Tue, Oct 28, 2014 at 5:54 AM, Huang Rui wrote:
> When parameter DWC_USB3_LPM_ERRATA_ENABLE is enabled in Andvanced
"Advanced"
> Configuration of coreConsultant, it supports of xHCI BESL Errata Dated
I can't parse "is supports of" and I don't know enough to suggest an
alternate wording.
>
On Wed, Oct 22, 2014 at 11:58 AM, Ivan T. Ivanov wrote:
> Changes since v4:
>
> - Rebased on v3.18-rc1:
> pinmux_ops.enable is now pinmux_ops.set_mux
> gpiochip_remove() did not return a value.
> - Added Ack's from Bjorn
Thanks guys, I have applied the latest version of the v6 patch series,
On Tue, Oct 28, 2014 at 10:16:43AM +0200, Meelis Roos wrote:
> > rcu: Make rcu_barrier() understand about missing rcuo kthreads
>
> I can not trigger the previous problem at will so my testing is not very
> useful. I tested the previous patch that you sent but the problem did
> not trigger, and
On Tue, Oct 28, 2014 at 5:54 AM, Huang Rui wrote:
> This patch adds Tx demphasis quirk, and the Tx demphasis value is
"demphasis" (above and in subject) should be "de-emphasis" as used in
the code and comments below.
> configurable according to PIPE3 specification.
>
> Value
On Tue, Oct 28, 2014 at 9:07 AM, Will Deacon wrote:
>
> Ok, that's useful, thanks. Out of curiosity, what *is* the current intention
> of __tlb_remove_tlb_entry, if start/end shouldn't be touched by
> architectures? Is it just for the PPC hash thing?
I think it's both the PPC hash, and for
On Tue, Oct 28, 2014 at 10:11 AM, Johannes Thumshirn
wrote:
> Currently it is not possible to have a kernel with built-in MCB attached
> devices. This results out of the fact that mcb-pci requests PCI BAR 0, then
> parses the chameleon table and calls the driver's probe function before
>
On Wed, Oct 22, 2014 at 1:19 AM, Chris Zhong wrote:
> From: Chris
>
> support suspend/resume of pinctrl, it allows handling sleep mode
> for hogged pins in pinctrl
>
> Signed-off-by: Chris Zhong
Looks good but I'm delegating to Heiko to collect and review patches
on the Rockchip pin control
Hi guys,
with all the rockchip patches and cross-review going on may I ask
that you decide on a person to collect and send pull requests to me
for the Rockchip patch stack?
Preferably Heiko.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
[+cc Alex Williamson, Rajat]
On Tue, Oct 28, 2014 at 9:45 AM, Alex Deucher wrote:
> On Mon, Oct 27, 2014 at 12:44 PM, Bjorn Helgaas wrote:
>> On Sun, Oct 26, 2014 at 11:31 AM, Alex Deucher wrote:
>>> On Mon, Oct 13, 2014 at 12:11 PM, Bjorn Helgaas wrote:
[+cc Alex, Christian, dri-devel]
Currently it is not possible to have a kernel with built-in MCB attached
devices. This results out of the fact that mcb-pci requests PCI BAR 0, then
parses the chameleon table and calls the driver's probe function before
releasing BAR 0 again. When building the kernel with modules this is not a
On Tue, Oct 28, 2014 at 09:54:28AM -0600, Kevin Fenzi wrote:
> Just FYI, this solves the orig issue for me as well. ;)
>
> Thanks for all the work in tracking it down...
>
> Tested-by: Kevin Fenzi
And thank you for testing as well!
On Fri, Oct 17, 2014 at 11:49 AM, Alexandre Belloni
wrote:
> Copy the mach/at91_pio.h header locally and use it for pinctrl-at91.c. This
> allows to remove the dependency on mach/at91_pio.h to be able to move at91 to
> multiplatform.
>
> Signed-off-by: Alexandre Belloni
Patch applied to the
On 10/27/2014 09:35 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.59 release.
> There are 43 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 10/27/2014 09:33 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.16.7 release.
> There are 127 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 10/27/2014 09:34 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.23 release.
> There are 100 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 10/27/2014 09:32 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.17.2 release.
> There are 146 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Tue, 2014-10-28 at 03:53PM +0100, Linus Walleij wrote:
> On Thu, Oct 16, 2014 at 7:11 PM, Soren Brinkmann
> wrote:
>
> > Signed-off-by: Soren Brinkmann
> > ---
> > changes since RFC:
> > - use syscon/regmap to access registers in SLCR space
> > - add pinctrl to zc702 DT
> > - rebase to
Linus,
On Tue, Oct 28, 2014 at 8:51 AM, Linus Walleij wrote:
> On Tue, Oct 21, 2014 at 1:27 AM, Doug Anderson wrote:
>
>> The rockchip pinctrl driver uses irq_gc_set_wake() but doesn't setup
>> the .wake_enabled member. That means that we can never actually use a
>> pin for wakeup. When
On Wednesday 22 October 2014 13:57:51 Scott Branden wrote:
> +
> + aliases {
> + serial0 =
> + serial1 =
> + };
> +
> + chosen {
> + bootargs = "console=ttyS0,115200 earlyprintk debug";
> + };
>
Please move the 'aliases' and
501 - 600 of 2840 matches
Mail list logo
