Hi Andrew,
Andrew Lunn writes:
> This seems to be more than renaming a few functions. There looks to be
> real changes here. I think these changes should be split out into a
> separate patch with an explanation what is being changed. Keep this
> patch for plain renames.
>
> It
Hi Andrew,
Andrew Lunn writes:
> This seems to be more than renaming a few functions. There looks to be
> real changes here. I think these changes should be split out into a
> separate patch with an explanation what is being changed. Keep this
> patch for plain renames.
>
> It would also be
On Fri, Feb 17, 2017 at 11:14 AM, Li, Yi wrote:
> hi Alan
>
>
> On 2/15/2017 10:14 AM, Alan Tull wrote:
>>
>> Document that getting a reference to a FPGA Manager has been
>> separated from locking the FPGA Mangager for use.
>>
>> fpga_mgr_lock/unlock functions get/release
On Fri, Feb 17, 2017 at 11:14 AM, Li, Yi wrote:
> hi Alan
>
>
> On 2/15/2017 10:14 AM, Alan Tull wrote:
>>
>> Document that getting a reference to a FPGA Manager has been
>> separated from locking the FPGA Mangager for use.
>>
>> fpga_mgr_lock/unlock functions get/release mutex.
>>
>>
On Tue, Feb 7, 2017 at 11:51 AM, Dmitry Vyukov wrote:
> On Tue, Feb 7, 2017 at 11:43 AM, Greg Kroah-Hartman
> wrote:
>> On Tue, Feb 07, 2017 at 11:24:13AM +0100, Dmitry Vyukov wrote:
>>> On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
>>>
On Tue, Feb 7, 2017 at 11:51 AM, Dmitry Vyukov wrote:
> On Tue, Feb 7, 2017 at 11:43 AM, Greg Kroah-Hartman
> wrote:
>> On Tue, Feb 07, 2017 at 11:24:13AM +0100, Dmitry Vyukov wrote:
>>> On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
>>> wrote:
>>> > On Thu, Feb 02, 2017 at 07:03:41PM
On February 17, 2017 1:10:27 PM PST, Linus Torvalds
wrote:
>On Fri, Feb 17, 2017 at 1:04 PM, Dave Hansen
>wrote:
>>
>> Is this likely to break anything in practice? Nah. But it would
>nice
>> to avoid it.
>
>So I go the other way: what *I*
On February 17, 2017 1:10:27 PM PST, Linus Torvalds
wrote:
>On Fri, Feb 17, 2017 at 1:04 PM, Dave Hansen
>wrote:
>>
>> Is this likely to break anything in practice? Nah. But it would
>nice
>> to avoid it.
>
>So I go the other way: what *I* would like to avoid is odd code that
>is hard to
On Fri, Feb 17, 2017 at 10:05:30AM -0500, Vivien Didelot wrote:
> Because there are several variant of the VTU operations and because
> checking for the presence of an STU is not enough, add new ops to the
> info structure to describe the VTU operations that a chip supports.
>
> Signed-off-by:
On Fri, Feb 17, 2017 at 10:05:30AM -0500, Vivien Didelot wrote:
> Because there are several variant of the VTU operations and because
> checking for the presence of an STU is not enough, add new ops to the
> info structure to describe the VTU operations that a chip supports.
>
> Signed-off-by:
On Fri, Feb 17, 2017 at 10:05:29AM -0500, Vivien Didelot wrote:
> Move the Global (1) VTU related code to its own file.
>
> Use this opportunity to provide a cleaner API for the VTU, by renaming a
> few underscore prefixed functions, split the data member of the
> mv88e6xxx_vtu_entry structure
On Fri, Feb 17, 2017 at 10:05:29AM -0500, Vivien Didelot wrote:
> Move the Global (1) VTU related code to its own file.
>
> Use this opportunity to provide a cleaner API for the VTU, by renaming a
> few underscore prefixed functions, split the data member of the
> mv88e6xxx_vtu_entry structure
On Fri, 17 Feb 2017 11:01:10 +
"Jon Medhurst (Tixy)" wrote:
> On Wed, 2017-02-15 at 09:27 +0900, Masami Hiramatsu wrote:
> > Hi,
> >
> > Here is the 2nd version of the patches which improve kprobe
> > on arm implementation (a kind of bugfix). Version 1 is here;
> >
> >
On Fri, 17 Feb 2017 11:01:10 +
"Jon Medhurst (Tixy)" wrote:
> On Wed, 2017-02-15 at 09:27 +0900, Masami Hiramatsu wrote:
> > Hi,
> >
> > Here is the 2nd version of the patches which improve kprobe
> > on arm implementation (a kind of bugfix). Version 1 is here;
> >
> >
Braces should be used on all arms of these statements (CHECK)..
Signed-off-by: Shiva Kerdel
---
drivers/staging/ks7010/ks_hostif.c | 6 --
drivers/staging/ks7010/ks_wlan_net.c | 42 +++-
2 files changed, 31 insertions(+), 17 deletions(-)
Braces should be used on all arms of these statements (CHECK)..
Signed-off-by: Shiva Kerdel
---
drivers/staging/ks7010/ks_hostif.c | 6 --
drivers/staging/ks7010/ks_wlan_net.c | 42 +++-
2 files changed, 31 insertions(+), 17 deletions(-)
diff --git
On 02/17/2017 12:09 PM, Florian Fainelli wrote:
On 02/17/2017 12:04 PM, David Daney wrote:
Some Cavium dev boards have firmware which doesn't supply a proper
ethernet-phy-ieee802.3-c22" compatible property. Restore these boards
to working order by whitelisting this compatible value.
On 02/17/2017 12:09 PM, Florian Fainelli wrote:
On 02/17/2017 12:04 PM, David Daney wrote:
Some Cavium dev boards have firmware which doesn't supply a proper
ethernet-phy-ieee802.3-c22" compatible property. Restore these boards
to working order by whitelisting this compatible value.
On Fri, Feb 17, 2017 at 10:05:28AM -0500, Vivien Didelot wrote:
> The 6390 family of Marvell chips uses 5 bits to describe the ToPort and
> FromPort values of PortVec in the ATU Move operation, while older
> switches use 0xf.
Hi Vivien
Since you say 5 bits for 6390, it would be better to say 4
On Fri, Feb 17, 2017 at 10:05:28AM -0500, Vivien Didelot wrote:
> The 6390 family of Marvell chips uses 5 bits to describe the ToPort and
> FromPort values of PortVec in the ATU Move operation, while older
> switches use 0xf.
Hi Vivien
Since you say 5 bits for 6390, it would be better to say 4
On Fri, Feb 17, 2017 at 10:05:27AM -0500, Vivien Didelot wrote:
> Move the Global (1) ATU related code in its own file, and export the
> necessary primitives.
>
> Use that opportunity to provide a cleaner API for the ATU, by renaming a
> few underscore prefixed functions, and members of the
>
On Fri, Feb 17, 2017 at 10:05:27AM -0500, Vivien Didelot wrote:
> Move the Global (1) ATU related code in its own file, and export the
> necessary primitives.
>
> Use that opportunity to provide a cleaner API for the ATU, by renaming a
> few underscore prefixed functions, and members of the
>
On Fri, Feb 17, 2017 at 01:08:55PM -0800, Andrew Morton wrote:
> I had a bunch more rejects to fix in that function. Below is the final
> result - please check it carefully.
Sure, reviewed and this is the diff that remains (vm_shared assignment
location is irrelevant, I put it at the end as it's
On Fri, Feb 17, 2017 at 01:08:55PM -0800, Andrew Morton wrote:
> I had a bunch more rejects to fix in that function. Below is the final
> result - please check it carefully.
Sure, reviewed and this is the diff that remains (vm_shared assignment
location is irrelevant, I put it at the end as it's
Hi all,
while poking at a different issue I found the following on my logs :
[85362.132770] BUG: sleeping function called from invalid context at
kernel/irq/manage.c:110
[85362.132771] in_atomic(): 1, irqs_disabled(): 1, pid: 1153, name:
systemd-journal
[85362.132772] no locks held by
Hi all,
while poking at a different issue I found the following on my logs :
[85362.132770] BUG: sleeping function called from invalid context at
kernel/irq/manage.c:110
[85362.132771] in_atomic(): 1, irqs_disabled(): 1, pid: 1153, name:
systemd-journal
[85362.132772] no locks held by
On Fri, Feb 17, 2017 at 11:08:59AM +0800, Chen-Yu Tsai wrote:
> On Fri, Feb 17, 2017 at 5:16 AM, Rask Ingemann Lambertsen
> wrote:
> > In summary: I'll propose a new property "extended-address" or so to the
> > existing "x-powers,axp806" compatible, because the axp808 does seem
On Fri, Feb 17, 2017 at 11:08:59AM +0800, Chen-Yu Tsai wrote:
> On Fri, Feb 17, 2017 at 5:16 AM, Rask Ingemann Lambertsen
> wrote:
> > In summary: I'll propose a new property "extended-address" or so to the
> > existing "x-powers,axp806" compatible, because the axp808 does seem to have
> > the
On Fri, Dec 30, 2016 at 08:36:30PM +, Jonathan Cameron wrote:
> On 28/12/16 14:53, H. Nikolaus Schaller wrote:
> > The tsc2007 chip not only has a resistive touch screen controller but
> > also an external AUX adc imput which can be used for an ambient
> > light sensor, battery voltage
On Fri, Dec 30, 2016 at 08:36:30PM +, Jonathan Cameron wrote:
> On 28/12/16 14:53, H. Nikolaus Schaller wrote:
> > The tsc2007 chip not only has a resistive touch screen controller but
> > also an external AUX adc imput which can be used for an ambient
> > light sensor, battery voltage
On Fri, Feb 17, 2017 at 10:05:26AM -0500, Vivien Didelot wrote:
> Add a mv88e6xxx_port_mask() helper to get the bitmask of ports in a
> switch chip, that will be used in several features.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
On Fri, Feb 17, 2017 at 10:05:26AM -0500, Vivien Didelot wrote:
> Add a mv88e6xxx_port_mask() helper to get the bitmask of ports in a
> switch chip, that will be used in several features.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Andrew
From: "Steven Rostedt (VMware)"
While looking into optimizations for the RT scheduler IPI logic, I realized
that the comments are lacking to describe it efficiently. It deserves a
lengthy description describing its design.
Signed-off-by: Steven Rostedt (VMware)
From: "Steven Rostedt (VMware)"
While looking into optimizations for the RT scheduler IPI logic, I realized
that the comments are lacking to describe it efficiently. It deserves a
lengthy description describing its design.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/sched/rt.c | 63
On Fri, Feb 17, 2017 at 03:26:36PM +0100, Jiri Slaby wrote:
> On 02/17/2017, 03:07 PM, Josh Poimboeuf wrote:
> > On Fri, Feb 17, 2017 at 02:36:15PM +0100, Jiri Slaby wrote:
> >> On 02/17/2017, 02:16 PM, Josh Poimboeuf wrote:
> >>> On Fri, Feb 17, 2017 at 11:47:57AM +0100, Jiri Slaby wrote:
>
On Fri, Feb 17, 2017 at 03:26:36PM +0100, Jiri Slaby wrote:
> On 02/17/2017, 03:07 PM, Josh Poimboeuf wrote:
> > On Fri, Feb 17, 2017 at 02:36:15PM +0100, Jiri Slaby wrote:
> >> On 02/17/2017, 02:16 PM, Josh Poimboeuf wrote:
> >>> On Fri, Feb 17, 2017 at 11:47:57AM +0100, Jiri Slaby wrote:
>
Greetings,
Running ltp on master.today, I received the splat (from hell) below.
[ 5015.128458] =
[ 5015.128458] [ INFO: possible irq lock inversion dependency detected ]
[ 5015.128458] 4.10.0-default #119 Tainted: GE
[
Greetings,
Running ltp on master.today, I received the splat (from hell) below.
[ 5015.128458] =
[ 5015.128458] [ INFO: possible irq lock inversion dependency detected ]
[ 5015.128458] 4.10.0-default #119 Tainted: GE
[
On Fri, Feb 17, 2017 at 1:04 PM, Dave Hansen wrote:
>
> Is this likely to break anything in practice? Nah. But it would nice
> to avoid it.
So I go the other way: what *I* would like to avoid is odd code that
is hard to follow. I'd much rather make the code be simple and
On Fri, Feb 17, 2017 at 1:04 PM, Dave Hansen wrote:
>
> Is this likely to break anything in practice? Nah. But it would nice
> to avoid it.
So I go the other way: what *I* would like to avoid is odd code that
is hard to follow. I'd much rather make the code be simple and the
rules be
On Fri, 17 Feb 2017 21:51:24 +0100 Andrea Arcangeli wrote:
> On Fri, Feb 17, 2017 at 12:17:38PM -0800, Andrew Morton wrote:
> > I merged this up and a small issue remains:
>
> Great!
>
> > The value of `err' here is EINVAL. That sems appropriate, but it only
> > happens
On Fri, 17 Feb 2017 21:51:24 +0100 Andrea Arcangeli wrote:
> On Fri, Feb 17, 2017 at 12:17:38PM -0800, Andrew Morton wrote:
> > I merged this up and a small issue remains:
>
> Great!
>
> > The value of `err' here is EINVAL. That sems appropriate, but it only
> > happens by sheer luck.
>
> It
On 02/17/2017 12:02 PM, Linus Torvalds wrote:
> So if you use MAP_FIXED and give an address in the high range, it will
> just always work, and the MM will always consider the task size to be
> the full address space.
>
> But for the common case where a process does no use MAP_FIXED, the
> kernel
On 02/17/2017 12:02 PM, Linus Torvalds wrote:
> So if you use MAP_FIXED and give an address in the high range, it will
> just always work, and the MM will always consider the task size to be
> the full address space.
>
> But for the common case where a process does no use MAP_FIXED, the
> kernel
On Fri, Feb 17, 2017 at 12:12 PM, Andy Lutomirski wrote:
>
> At the very least, I'd want to see
> MAP_FIXED_BUT_DONT_BLOODY_UNMAP_ANYTHING. I *hate* the current
> interface.
That's unrelated, but I guess w could add a MAP_NOUNMAP flag, and then
you can use MAP_FIXED |
On Fri, Feb 17, 2017 at 12:12 PM, Andy Lutomirski wrote:
>
> At the very least, I'd want to see
> MAP_FIXED_BUT_DONT_BLOODY_UNMAP_ANYTHING. I *hate* the current
> interface.
That's unrelated, but I guess w could add a MAP_NOUNMAP flag, and then
you can use MAP_FIXED | MAP_NOUNMAP or something.
On Thu, 2017-02-16 at 19:06 +0100, Mike Galbraith wrote:
> On Thu, 2017-02-16 at 15:53 +0100, Sebastian Andrzej Siewior wrote:
> > On 2017-02-16 15:42:59 [+0100], Mike Galbraith wrote:
> > >
> > > Weeell, I'm trying to cobble something kinda like that together using
> > > __RT_SPIN_INITIALIZER()
On Thu, 2017-02-16 at 19:06 +0100, Mike Galbraith wrote:
> On Thu, 2017-02-16 at 15:53 +0100, Sebastian Andrzej Siewior wrote:
> > On 2017-02-16 15:42:59 [+0100], Mike Galbraith wrote:
> > >
> > > Weeell, I'm trying to cobble something kinda like that together using
> > > __RT_SPIN_INITIALIZER()
ip/x86/core kvm/linux-next tip/auto-latest v4.9-rc8
>> v4.9-rc7 v4.9-rc6]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>> help improve the system]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/Thomas-Garnier/x86-mm-Ada
9-rc6]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>> help improve the system]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/Thomas-Garnier/x86-mm-Adapt-MODULES_END-based-on-Fixmap-section-size/20170217-072759
>> config: x86_64
On Wed, Dec 28, 2016 at 03:53:17PM +0100, H. Nikolaus Schaller wrote:
> 1. check if chip is really present and don't succeed if it isn't.
> 2. if it succeeds, power down the chip until accessed
>
> Signed-off-by: H. Nikolaus Schaller
Applied, thank you.
> ---
>
On Wed, Dec 28, 2016 at 03:53:17PM +0100, H. Nikolaus Schaller wrote:
> 1. check if chip is really present and don't succeed if it isn't.
> 2. if it succeeds, power down the chip until accessed
>
> Signed-off-by: H. Nikolaus Schaller
Applied, thank you.
> ---
>
On Fri, Feb 17, 2017 at 12:17:38PM -0800, Andrew Morton wrote:
> I merged this up and a small issue remains:
Great!
> The value of `err' here is EINVAL. That sems appropriate, but it only
> happens by sheer luck.
It might have been programmer luck but just for completeness, at
runtime no luck
On Fri, Feb 17, 2017 at 12:17:38PM -0800, Andrew Morton wrote:
> I merged this up and a small issue remains:
Great!
> The value of `err' here is EINVAL. That sems appropriate, but it only
> happens by sheer luck.
It might have been programmer luck but just for completeness, at
runtime no luck
On Fri, 2017-02-17 at 17:51 +, Al Viro wrote:
> On Fri, Feb 17, 2017 at 09:24:40AM -0800, James Bottomley wrote:
>
> > > What happens when somebody comes along and creates the damn thing
> > > on
> > > the underlying fs? _Not_ via your code, that is - using the
> > > underlying fs mounted
On Fri, 2017-02-17 at 17:51 +, Al Viro wrote:
> On Fri, Feb 17, 2017 at 09:24:40AM -0800, James Bottomley wrote:
>
> > > What happens when somebody comes along and creates the damn thing
> > > on
> > > the underlying fs? _Not_ via your code, that is - using the
> > > underlying fs mounted
From: Colin Ian King
trivial fix to spelling mistake in debhg message
Signed-off-by: Colin Ian King
---
fs/ext4/move_extent.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/move_extent.c b/fs/ext4/move_extent.c
From: Colin Ian King
trivial fix to spelling mistake in debhg message
Signed-off-by: Colin Ian King
---
fs/ext4/move_extent.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/move_extent.c b/fs/ext4/move_extent.c
index 578f8c3..ae4d1b6 100644
---
On Wed, Feb 15, 2017 at 03:03:07PM +0100, H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Am 12.02.2017 um 16:18 schrieb H. Nikolaus Schaller :
> >
> > Hi Dmitry,
> >
> >> Am 28.01.2017 um 19:16 schrieb H. Nikolaus Schaller :
> >>
> >> Hi Dmitry,
> >>
On Wed, Feb 15, 2017 at 03:03:07PM +0100, H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Am 12.02.2017 um 16:18 schrieb H. Nikolaus Schaller :
> >
> > Hi Dmitry,
> >
> >> Am 28.01.2017 um 19:16 schrieb H. Nikolaus Schaller :
> >>
> >> Hi Dmitry,
> >> there have been no further
All the locking related cmpxchg's in the following functions are
replaced with the _acquire variants:
- pv_queued_spin_steal_lock()
- trylock_clear_pending()
This change should help performance on architectures that use LL/SC.
On a 2-core 16-thread Power8 system with pvqspinlock explicitly
The buffer is used by virtio console driver as DMA buffer. Since v4.9
(if VMAP_STACK is enabled) we shouldn't use the stack for DMA.
Signed-off-by: Jan Dakinevich
---
drivers/tty/hvc/hvc_console.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
All the locking related cmpxchg's in the following functions are
replaced with the _acquire variants:
- pv_queued_spin_steal_lock()
- trylock_clear_pending()
This change should help performance on architectures that use LL/SC.
On a 2-core 16-thread Power8 system with pvqspinlock explicitly
The buffer is used by virtio console driver as DMA buffer. Since v4.9
(if VMAP_STACK is enabled) we shouldn't use the stack for DMA.
Signed-off-by: Jan Dakinevich
---
drivers/tty/hvc/hvc_console.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
Em Fri, Feb 17, 2017 at 07:44:33PM +0900, Masami Hiramatsu escreveu:
> On Thu, 16 Feb 2017 13:47:37 +0530
> "Naveen N. Rao" wrote:
>
> > I am posting the powerpc bits in the same thread so as to keep these
> > changes together. I am not sure how this should be
Em Fri, Feb 17, 2017 at 07:44:33PM +0900, Masami Hiramatsu escreveu:
> On Thu, 16 Feb 2017 13:47:37 +0530
> "Naveen N. Rao" wrote:
>
> > I am posting the powerpc bits in the same thread so as to keep these
> > changes together. I am not sure how this should be taken upstream as
> > there are
In others board we have the sata led set to funcion with the sata led trigger
by default.
This patch makes the same for these board that have sata led but disabled by
not associating it to any trigger
Signed-off-by: Ansuel Smith
---
In others board we have the sata led set to funcion with the sata led trigger
by default.
This patch makes the same for these board that have sata led but disabled by
not associating it to any trigger
Signed-off-by: Ansuel Smith
---
arch/arm/boot/dts/armada-385-linksys-caiman.dts | 1 +
Hi Marc Zyngier,
Verifying this RFC series on Cavium ThunderX board to validate the
GICV3 changes, noticed host crash as below.
Host booted fine with this change
"gic_flush_dcache_to_poc(page_address(prop_page), LPI_PROPBASE_SZ);"
Loading Linux 4.10.0-rc3-mz-rfc1+ ...
Loading initial ramdisk
Hi Marc Zyngier,
Verifying this RFC series on Cavium ThunderX board to validate the
GICV3 changes, noticed host crash as below.
Host booted fine with this change
"gic_flush_dcache_to_poc(page_address(prop_page), LPI_PROPBASE_SZ);"
Loading Linux 4.10.0-rc3-mz-rfc1+ ...
Loading initial ramdisk
Hi Nikolaus,
On Sat, Jan 28, 2017 at 10:44:35PM +0100, H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Am 28.01.2017 um 20:33 schrieb Dmitry Torokhov :
> >
> > Hi Nikolaus,
> >
> > On Wed, Dec 28, 2016 at 03:53:16PM +0100, H. Nikolaus Schaller wrote:
> >> commit
Hi Nikolaus,
On Sat, Jan 28, 2017 at 10:44:35PM +0100, H. Nikolaus Schaller wrote:
> Hi Dmitry,
>
> > Am 28.01.2017 um 20:33 schrieb Dmitry Torokhov :
> >
> > Hi Nikolaus,
> >
> > On Wed, Dec 28, 2016 at 03:53:16PM +0100, H. Nikolaus Schaller wrote:
> >> commit b98abe52fa8e ("Input: add common
On 02/17/2017 02:23 PM, Colin King wrote:
From: Colin Ian King
trivial fix to spelling mistakes of "palette"
Signed-off-by: Colin Ian King
Acked-by: Timur Tabi
On 02/17/2017 02:23 PM, Colin King wrote:
From: Colin Ian King
trivial fix to spelling mistakes of "palette"
Signed-off-by: Colin Ian King
Acked-by: Timur Tabi
Hi Maxime,
As I feared things have taken a turn for the bitter end :-]
It seems that this is a heated topic, so I'l kindly ask that we try
the following:
- For people such as myself/Tobias/others who feel that driver and DT
bindings should go hand in hand, prove them wrong.
But please, do so
Hi Maxime,
As I feared things have taken a turn for the bitter end :-]
It seems that this is a heated topic, so I'l kindly ask that we try
the following:
- For people such as myself/Tobias/others who feel that driver and DT
bindings should go hand in hand, prove them wrong.
But please, do so
On Fri, Feb 17, 2017 at 7:51 PM, Cong Wang wrote:
>
> This code was changed a long time ago :
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ed2e923945892a8372ab70d2f61d364b0b6d9054
>
> So I suspect a recent patch
On Fri, Feb 17, 2017 at 7:51 PM, Cong Wang wrote:
>
> This code was changed a long time ago :
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ed2e923945892a8372ab70d2f61d364b0b6d9054
>
> So I suspect a recent patch broke the logic.
>
Hi Bjorn,
Can you give us an idea of when you might be able to comment on our
patchset? We've addressed all the outstanding issues and have a couple
of reviewed and tested tags. So we'd like to see this move forward as
soon as possible.
I can do a respin with the tags collected or address any
Hi Bjorn,
Can you give us an idea of when you might be able to comment on our
patchset? We've addressed all the outstanding issues and have a couple
of reviewed and tested tags. So we'd like to see this move forward as
soon as possible.
I can do a respin with the tags collected or address any
On Fri, Feb 17, 2017 at 09:34:07AM -0800, James Bottomley wrote:
> On Fri, 2017-02-17 at 02:55 +, Al Viro wrote:
> > On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote:
> >
> > > > Hi James,
> > > >
> > > > Should it be "return d_splice_alias()" so that if we find an
> > > >
On Fri, Feb 17, 2017 at 09:34:07AM -0800, James Bottomley wrote:
> On Fri, 2017-02-17 at 02:55 +, Al Viro wrote:
> > On Thu, Feb 16, 2017 at 07:56:30AM -0800, James Bottomley wrote:
> >
> > > > Hi James,
> > > >
> > > > Should it be "return d_splice_alias()" so that if we find an
> > > >
On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote:
> To enable eventual removal of pr_warning
>
> This makes pr_warn use consistent for sound/soc
>
> Prior to this patch, there were 5 uses of pr_warning and
> 10 uses of pr_warn in sound/soc
>
> Signed-off-by: Joe Perches
On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote:
> To enable eventual removal of pr_warning
>
> This makes pr_warn use consistent for sound/soc
>
> Prior to this patch, there were 5 uses of pr_warning and
> 10 uses of pr_warn in sound/soc
>
> Signed-off-by: Joe Perches
For
On Fri, Feb 17, 2017 at 05:51:18PM +, Al Viro wrote:
> On Fri, Feb 17, 2017 at 09:24:40AM -0800, James Bottomley wrote:
>
> > > What happens when somebody comes along and creates the damn thing on
> > > the underlying fs? _Not_ via your code, that is - using the
> > > underlying fs mounted
On Fri, Feb 17, 2017 at 05:51:18PM +, Al Viro wrote:
> On Fri, Feb 17, 2017 at 09:24:40AM -0800, James Bottomley wrote:
>
> > > What happens when somebody comes along and creates the damn thing on
> > > the underlying fs? _Not_ via your code, that is - using the
> > > underlying fs mounted
From: Arnd Bergmann
Date: Fri, 17 Feb 2017 16:08:30 +0100
> I got a warning about broken code on ARM64 with 64K pages:
>
> drivers/net/vmxnet3/vmxnet3_drv.c: In function 'vmxnet3_rq_init':
> drivers/net/vmxnet3/vmxnet3_drv.c:1679:29: error: large integer implicitly
> truncated
From: Arnd Bergmann
Date: Fri, 17 Feb 2017 16:08:30 +0100
> I got a warning about broken code on ARM64 with 64K pages:
>
> drivers/net/vmxnet3/vmxnet3_drv.c: In function 'vmxnet3_rq_init':
> drivers/net/vmxnet3/vmxnet3_drv.c:1679:29: error: large integer implicitly
> truncated to unsigned type
From: Markus Mayer
Add maintainer information for bmips-cpufreq.c.
Signed-off-by: Markus Mayer
Acked-by: Florian Fainelli
---
This is based on PM's linux-next from today (February 17).
This patch could be squashed into patch
From: Markus Mayer
Add maintainer information for bmips-cpufreq.c.
Signed-off-by: Markus Mayer
Acked-by: Florian Fainelli
---
This is based on PM's linux-next from today (February 17).
This patch could be squashed into patch 3/4 of the original series if that
is acceptable (see [1]) or it
On Fri, 17 Feb 2017 16:52:41 +0100 Andrea Arcangeli wrote:
> Everything else is identical which is great. Mike Rapoport could you
> verify the below hunk is missing in mm?
>
> Once it'll all be merged upstream then there will be less merge crunch
> as we've been working
On Fri, 17 Feb 2017 16:52:41 +0100 Andrea Arcangeli wrote:
> Everything else is identical which is great. Mike Rapoport could you
> verify the below hunk is missing in mm?
>
> Once it'll all be merged upstream then there will be less merge crunch
> as we've been working somewhat in parallel on
From: Colin Ian King
trivial fix to spelling mistakes of "palette"
Signed-off-by: Colin Ian King
---
drivers/video/fbdev/fsl-diu-fb.c | 4 ++--
include/linux/fsl-diu-fb.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff
From: Colin Ian King
trivial fix to spelling mistakes of "palette"
Signed-off-by: Colin Ian King
---
drivers/video/fbdev/fsl-diu-fb.c | 4 ++--
include/linux/fsl-diu-fb.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/video/fbdev/fsl-diu-fb.c
On Fri, Feb 17, 2017 at 12:02 PM, Linus Torvalds
wrote:
> On Fri, Feb 17, 2017 at 6:13 AM, Kirill A. Shutemov
> wrote:
>> This patch introduces two new prctl(2) handles to manage maximum virtual
>> address available to userspace to
On Fri, Feb 17, 2017 at 12:02 PM, Linus Torvalds
wrote:
> On Fri, Feb 17, 2017 at 6:13 AM, Kirill A. Shutemov
> wrote:
>> This patch introduces two new prctl(2) handles to manage maximum virtual
>> address available to userspace to map.
>
> So this is my least favorite patch of the whole series,
Fix checkpatch.pl warning of the form "WARNING: line over 80 characters."
Signed-off-by: Nathan Howard
---
drivers/staging/bcm2835-audio/bcm2835.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/bcm2835-audio/bcm2835.h
Fix checkpatch.pl warning of the form "WARNING: Use of volatile is
usually wrong: see Documentation/process/volatile-considered-harmful.rst."
Signed-off-by: Nathan Howard
---
drivers/staging/bcm2835-audio/bcm2835.h | 4 ++--
1 file changed, 2 insertions(+), 2
Fix checkpatch.pl warning of the form "WARNING: line over 80 characters."
Signed-off-by: Nathan Howard
---
drivers/staging/bcm2835-audio/bcm2835.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/bcm2835-audio/bcm2835.h
Fix checkpatch.pl warning of the form "WARNING: Use of volatile is
usually wrong: see Documentation/process/volatile-considered-harmful.rst."
Signed-off-by: Nathan Howard
---
drivers/staging/bcm2835-audio/bcm2835.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
201 - 300 of 1398 matches
Mail list logo