Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, 24 Aug 2016 16:50:11 +0200 Thomas Petazzoni wrote: > Hello, > > On Sun, 21 Aug 2016 15:11:58 +0200, Ralph Sennhauser wrote: > > > Commit cb4f71c4298853db0c6751b1209e4535956f136c changes the order of > > the network interfaces for armada-38x. As a

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, Aug 24, 2016 at 06:43:34PM +0200, Thomas Petazzoni wrote: > Well, just like the for the documentation aspect, you're seeing this > from the OpenWRT/LEDE angle only. Other people are using plenty of > other things. > > We knew it would potentially cause some breakage, so it was a >

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, 24 Aug 2016 16:50:11 +0200 Thomas Petazzoni wrote: > Hello, > > On Sun, 21 Aug 2016 15:11:58 +0200, Ralph Sennhauser wrote: > > > Commit cb4f71c4298853db0c6751b1209e4535956f136c changes the order of > > the network interfaces for armada-38x. As a special exception to the > > "order by

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, Aug 24, 2016 at 06:43:34PM +0200, Thomas Petazzoni wrote: > Well, just like the for the documentation aspect, you're seeing this > from the OpenWRT/LEDE angle only. Other people are using plenty of > other things. > > We knew it would potentially cause some breakage, so it was a >

Re: [PATCH] mm: memcontrol: avoid unused function warning

On Wed, Aug 24, 2016 at 10:22:43AM +0200, Arnd Bergmann wrote: > A bugfix in v4.8-rc2 introduced a harmless warning when CONFIG_MEMCG_SWAP > is disabled but CONFIG_MEMCG is enabled: > > mm/memcontrol.c:4085:27: error: 'mem_cgroup_id_get_online' defined but not > used [-Werror=unused-function] >

Re: [PATCH] mm: memcontrol: avoid unused function warning

On Wed, Aug 24, 2016 at 10:22:43AM +0200, Arnd Bergmann wrote: > A bugfix in v4.8-rc2 introduced a harmless warning when CONFIG_MEMCG_SWAP > is disabled but CONFIG_MEMCG is enabled: > > mm/memcontrol.c:4085:27: error: 'mem_cgroup_id_get_online' defined but not > used [-Werror=unused-function] >

Re: [PATCH net-next 0/2] rxrpc: More fixes

From: David Howells <dhowe...@redhat.com> Date: Wed, 24 Aug 2016 15:59:46 +0100 > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20160824-1 Both -1 and -2 pulled, thanks David!

Re: [PATCH net-next 0/2] rxrpc: More fixes

From: David Howells Date: Wed, 24 Aug 2016 15:59:46 +0100 > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20160824-1 Both -1 and -2 pulled, thanks David!

Re: [RFC][PATCH 1/3] locking/mutex: Rework mutex::owner

On Wed, Aug 24, 2016 at 05:34:12PM +0200, Peter Zijlstra wrote: > On Wed, Aug 24, 2016 at 10:56:59AM +0100, Will Deacon wrote: > > > + owner = atomic_long_read(>owner); > > > + for (;;) { > > > + unsigned long old; > > > + > > > + old = atomic_long_cmpxchg_release(>owner, owner,

[PATCH 1/6] perf/x86: check perf_callchain_store() error

Add a check to perf_callchain_kernel() so that it returns early if the callchain entry array is already full. Signed-off-by: Josh Poimboeuf --- arch/x86/events/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/x86/events/core.c

Re: [RFC][PATCH 1/3] locking/mutex: Rework mutex::owner

On Wed, Aug 24, 2016 at 06:52:44PM +0200, Peter Zijlstra wrote: > On Wed, Aug 24, 2016 at 05:34:12PM +0200, Peter Zijlstra wrote: > > On Wed, Aug 24, 2016 at 10:56:59AM +0100, Will Deacon wrote: > > > > + owner = atomic_long_read(>owner); > > > > + for (;;) { > > > > +

[PATCH 3/6] x86/dumpstack: make printk_stack_address() more generally useful

Change printk_stack_address() to be useful when called by an unwinder outside the context of dump_trace(). Specifically: - printk_stack_address()'s 'data' argument is always used as the log level string. Make that explicit. - Call touch_nmi_watchdog(). Signed-off-by: Josh Poimboeuf

Re: [RFC][PATCH 1/3] locking/mutex: Rework mutex::owner

On Wed, Aug 24, 2016 at 05:34:12PM +0200, Peter Zijlstra wrote: > On Wed, Aug 24, 2016 at 10:56:59AM +0100, Will Deacon wrote: > > > + owner = atomic_long_read(>owner); > > > + for (;;) { > > > + unsigned long old; > > > + > > > + old = atomic_long_cmpxchg_release(>owner, owner,

[PATCH 1/6] perf/x86: check perf_callchain_store() error

Add a check to perf_callchain_kernel() so that it returns early if the callchain entry array is already full. Signed-off-by: Josh Poimboeuf --- arch/x86/events/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c index

Re: [RFC][PATCH 1/3] locking/mutex: Rework mutex::owner

On Wed, Aug 24, 2016 at 06:52:44PM +0200, Peter Zijlstra wrote: > On Wed, Aug 24, 2016 at 05:34:12PM +0200, Peter Zijlstra wrote: > > On Wed, Aug 24, 2016 at 10:56:59AM +0100, Will Deacon wrote: > > > > + owner = atomic_long_read(>owner); > > > > + for (;;) { > > > > +

[PATCH 3/6] x86/dumpstack: make printk_stack_address() more generally useful

Change printk_stack_address() to be useful when called by an unwinder outside the context of dump_trace(). Specifically: - printk_stack_address()'s 'data' argument is always used as the log level string. Make that explicit. - Call touch_nmi_watchdog(). Signed-off-by: Josh Poimboeuf ---

[PATCH 0/6] x86/dumpstack: more stack dump improvements

Some more preparatory patches for the new x86 unwinder (though these generally stand alone as improvements in their own right). Josh Poimboeuf (6): perf/x86: check perf_callchain_store() error oprofile/x86: add regs->ip to oprofile trace x86/dumpstack: make printk_stack_address() more

[PATCH 4/6] x86/dumpstack: add get_stack_pointer() and get_frame_pointer()

The various functions involved in dumping the stack all do similar things with regard to getting the stack pointer and the frame pointer based on the regs and task arguments. Create helper functions to do that instead. Reviewed-by: Andy Lutomirski Signed-off-by: Josh Poimboeuf

[PATCH 0/6] x86/dumpstack: more stack dump improvements

Some more preparatory patches for the new x86 unwinder (though these generally stand alone as improvements in their own right). Josh Poimboeuf (6): perf/x86: check perf_callchain_store() error oprofile/x86: add regs->ip to oprofile trace x86/dumpstack: make printk_stack_address() more

[PATCH 4/6] x86/dumpstack: add get_stack_pointer() and get_frame_pointer()

The various functions involved in dumping the stack all do similar things with regard to getting the stack pointer and the frame pointer based on the regs and task arguments. Create helper functions to do that instead. Reviewed-by: Andy Lutomirski Signed-off-by: Josh Poimboeuf ---

[PATCH 6/6] x86/dumpstack: allow preemption in show_stack_log_lvl() and dump_trace()

show_stack_log_lvl() and dump_trace() are already preemption safe: - If they're running in irq or exception context, preemption is already disabled and the percpu stack pointers can be trusted. - If they're running with preemption enabled, they must be running on the task stack anyway, so it

[PATCH 6/6] x86/dumpstack: allow preemption in show_stack_log_lvl() and dump_trace()

show_stack_log_lvl() and dump_trace() are already preemption safe: - If they're running in irq or exception context, preemption is already disabled and the percpu stack pointers can be trusted. - If they're running with preemption enabled, they must be running on the task stack anyway, so it

[PATCH 2/6] oprofile/x86: add regs->ip to oprofile trace

dump_trace() doesn't add the interrupted instruction's address to the trace, so add it manually. This makes the profile more useful, and also makes it more consistent with what perf profiling does. Cc: Robert Richter Signed-off-by: Josh Poimboeuf ---

[PATCH 5/6] x86/dumpstack: remove unnecessary stack pointer arguments

When calling show_stack_log_lvl() or dump_trace() with a regs argument, providing a stack pointer or frame pointer is redundant. Reviewed-by: Andy Lutomirski Signed-off-by: Josh Poimboeuf d --- arch/x86/kernel/dumpstack.c| 2 +-

[PATCH 2/6] oprofile/x86: add regs->ip to oprofile trace

dump_trace() doesn't add the interrupted instruction's address to the trace, so add it manually. This makes the profile more useful, and also makes it more consistent with what perf profiling does. Cc: Robert Richter Signed-off-by: Josh Poimboeuf --- arch/x86/oprofile/backtrace.c | 13

[PATCH 5/6] x86/dumpstack: remove unnecessary stack pointer arguments

When calling show_stack_log_lvl() or dump_trace() with a regs argument, providing a stack pointer or frame pointer is redundant. Reviewed-by: Andy Lutomirski Signed-off-by: Josh Poimboeuf d --- arch/x86/kernel/dumpstack.c| 2 +- arch/x86/kernel/dumpstack_32.c | 2 +-

Re: [LKP] [lkp] [f2fs] ec795418c4: fsmark.files_per_sec -36.3% regression

Hi, Jaegeuk, On Thu, Aug 11, 2016 at 6:22 PM, Jaegeuk Kim wrote: > On Thu, Aug 11, 2016 at 03:49:41PM -0700, Huang, Ying wrote: >> Hi, Kim, >> >> "Huang, Ying" writes: >> >> >> >> [lkp] [f2fs] 3bdad3c7ee: aim7.jobs-per-min -25.3% regression >> >> [lkp]

Re: [LKP] [lkp] [f2fs] ec795418c4: fsmark.files_per_sec -36.3% regression

Hi, Jaegeuk, On Thu, Aug 11, 2016 at 6:22 PM, Jaegeuk Kim wrote: > On Thu, Aug 11, 2016 at 03:49:41PM -0700, Huang, Ying wrote: >> Hi, Kim, >> >> "Huang, Ying" writes: >> >> >> >> [lkp] [f2fs] 3bdad3c7ee: aim7.jobs-per-min -25.3% regression >> >> [lkp] [f2fs] b93f771286: aim7.jobs-per-min

Re: [PATCH v2 1/2] PCI: quirk fixup for cavium invalid sriov link value.

On Tue, Aug 23, 2016 at 04:27:14PM -0700, Omer Khaliq wrote: > From: Ananth Jasty > > Cavium cn88xx hardware presents an incorrect SR-IOV Function > Dependency Link, add a fixup quirk for the affected devices. > > Acked-by: David Daney >

Re: [PATCH v2 1/2] PCI: quirk fixup for cavium invalid sriov link value.

On Tue, Aug 23, 2016 at 04:27:14PM -0700, Omer Khaliq wrote: > From: Ananth Jasty > > Cavium cn88xx hardware presents an incorrect SR-IOV Function > Dependency Link, add a fixup quirk for the affected devices. > > Acked-by: David Daney > Signed-off-by: Ananth Jasty > Signed-off-by: Omer

Re: [Patch v8] driver/clk/clk-si5338: Add common clock framework driver for si5338

On 08/23/2016 09:48 PM, Stephen Boyd wrote: > On 08/24, kbuild test robot wrote: >> >> 2827 if (drv_type < 0) >> 2828 return drv_type; >> 2829 >> 2830 drv_vdd = get_drv_vdd(drvdata, i); >> 2831 if (drv_vdd < 0) >>

Re: [Patch v8] driver/clk/clk-si5338: Add common clock framework driver for si5338

On 08/23/2016 09:48 PM, Stephen Boyd wrote: > On 08/24, kbuild test robot wrote: >> >> 2827 if (drv_type < 0) >> 2828 return drv_type; >> 2829 >> 2830 drv_vdd = get_drv_vdd(drvdata, i); >> 2831 if (drv_vdd < 0) >>

Re: [PATCH] scripts: add ksymbolize.py

Hello, Alexander. On Wed, Aug 24, 2016 at 06:37:35PM +0200, Alexander Potapenko wrote: > Commit the script that symbolizes BUG messages and KASAN error reports > by adding file:line information to each stack frame. > The script is a copy of >

Re: [PATCH] scripts: add ksymbolize.py

Hello, Alexander. On Wed, Aug 24, 2016 at 06:37:35PM +0200, Alexander Potapenko wrote: > Commit the script that symbolizes BUG messages and KASAN error reports > by adding file:line information to each stack frame. > The script is a copy of >

[PATCH] MAINTAINERS: Update video4linux patterns

Various commits have moved around the file directories, update the patterns. There are likely other v4l patterns that could be updated, these are just the existing ones that got moved around. Signed-off-by: Joe Perches cc: Mauro Carvalho Chehab ---

[PATCH] MAINTAINERS: Update video4linux patterns

Various commits have moved around the file directories, update the patterns. There are likely other v4l patterns that could be updated, these are just the existing ones that got moved around. Signed-off-by: Joe Perches cc: Mauro Carvalho Chehab --- MAINTAINERS | 20 ++-- 1

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

Hello, On Wed, 24 Aug 2016 12:19:33 -0400, Lennart Sorensen wrote: > > So having things match the documentation numbering was in our opinion > > the least confusing thing moving forward. We should have done it > > earlier, but we thought that the rule "order by register address" was a > > very

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

Hello, On Wed, 24 Aug 2016 12:19:33 -0400, Lennart Sorensen wrote: > > So having things match the documentation numbering was in our opinion > > the least confusing thing moving forward. We should have done it > > earlier, but we thought that the rule "order by register address" was a > > very

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

On 08/04/2016 06:30 AM, Rich Felker wrote: > At the hardware level, the J-Core PIT is integrated with the interrupt > controller, but it is represented as its own device and has an > independent programming interface. It provides a 12-bit countdown > timer, which is not presently used, and a

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

On 08/04/2016 06:30 AM, Rich Felker wrote: > At the hardware level, the J-Core PIT is integrated with the interrupt > controller, but it is represented as its own device and has an > independent programming interface. It provides a 12-bit countdown > timer, which is not presently used, and a

[PATCH] scripts: add ksymbolize.py

Commit the script that symbolizes BUG messages and KASAN error reports by adding file:line information to each stack frame. The script is a copy of https://github.com/google/sanitizers/blob/master/address-sanitizer/tools/kasan_symbolize.py , originally written by Andrey Konovalov. Cc: Andrey

[PATCH] scripts: add ksymbolize.py

Commit the script that symbolizes BUG messages and KASAN error reports by adding file:line information to each stack frame. The script is a copy of https://github.com/google/sanitizers/blob/master/address-sanitizer/tools/kasan_symbolize.py , originally written by Andrey Konovalov. Cc: Andrey

Re: [RFC PATCH 0/5] Add CONFIG symbol as module attribute

On Wed, Aug 24, 2016 at 01:05:04PM +0200, Michal Marek wrote: > On 2016-08-23 23:32, Luis R. Rodriguez wrote: > > On Fri, Aug 19, 2016 at 11:07:36AM +0200, Michal Marek wrote: > >> On 2016-08-18 19:55, Luis R. Rodriguez wrote: > >>> On Wed, Aug 17, 2016 at 09:26:58PM +0200, Cristina Moraru wrote:

Re: [RFC PATCH 0/5] Add CONFIG symbol as module attribute

On Wed, Aug 24, 2016 at 01:05:04PM +0200, Michal Marek wrote: > On 2016-08-23 23:32, Luis R. Rodriguez wrote: > > On Fri, Aug 19, 2016 at 11:07:36AM +0200, Michal Marek wrote: > >> On 2016-08-18 19:55, Luis R. Rodriguez wrote: > >>> On Wed, Aug 17, 2016 at 09:26:58PM +0200, Cristina Moraru wrote:

Re: next-20160804: Build error when building xtensa images

esting. Bisect points to 'xtensa: cleanup MMU setup and kernel layout macros'. Thanks for the report. The default kernel load address in this patch was wrong. Fix posted. xtensa builds still fails with that same error. Did the fix make its way to linux-next? xtensa defconfig for next-20160824 is at:

Re: next-20160804: Build error when building xtensa images

: cleanup MMU setup and kernel layout macros'. Thanks for the report. The default kernel load address in this patch was wrong. Fix posted. xtensa builds still fails with that same error. Did the fix make its way to linux-next? xtensa defconfig for next-20160824 is at: https://travis-ci.org

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, Aug 24, 2016 at 04:50:11PM +0200, Thomas Petazzoni wrote: > We had many many users getting confused by the fact that the order of > the network interfaces was inverted compared to: > > * The board documentations > * The U-Boot numbering > * And to a lesser extent, the vendor kernel >

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, Aug 24, 2016 at 04:50:11PM +0200, Thomas Petazzoni wrote: > We had many many users getting confused by the fact that the order of > the network interfaces was inverted compared to: > > * The board documentations > * The U-Boot numbering > * And to a lesser extent, the vendor kernel >

RE: [patch 2/2] i2c: mux: mellanox: add driver

Hi Peter, Thank you very much for your review. > -Original Message- > From: Peter Rosin [mailto:p...@axentia.se] > Sent: Wednesday, August 24, 2016 4:55 PM > To: Vadim Pasternak ; w...@the-dreams.de > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;

RE: [patch 2/2] i2c: mux: mellanox: add driver

Hi Peter, Thank you very much for your review. > -Original Message- > From: Peter Rosin [mailto:p...@axentia.se] > Sent: Wednesday, August 24, 2016 4:55 PM > To: Vadim Pasternak ; w...@the-dreams.de > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; j...@resnulli.us; >

[PATCH] dax: fix device-dax region base

The data offset for a dax region needs to account for a reservation in the resource range. Otherwise, device-dax is allowing mappings directly into the memmap or device-info-block area with crash signatures like the following: BUG: unable to handle kernel NULL pointer dereference at

[PATCH] dax: fix device-dax region base

The data offset for a dax region needs to account for a reservation in the resource range. Otherwise, device-dax is allowing mappings directly into the memmap or device-info-block area with crash signatures like the following: BUG: unable to handle kernel NULL pointer dereference at

[PATCH v2 1/2] ASoC: simple-card-utils: add __printf attribute

asoc_simple_card_set_dailink_name() uses devm_kvasprintf() to format some of its arguments. Adding a __printf attribute to this function makes it possible to detect at compile-time errors related to format strings. Signed-off-by: Nicolas Iooss ---

[PATCH v2 2/2] MAINTAINERS: document ASoC header files

include/sound/simple_card_utils.h is handled by ASoC maintainers, as stated in https://lkml.org/lkml/2016/8/22/307, and include/sound/simple_card.h seems to be an ASoC file too. In the future there will be more files named like these ones so introduce a pattern to match them. Signed-off-by:

[PATCH v2 1/2] ASoC: simple-card-utils: add __printf attribute

asoc_simple_card_set_dailink_name() uses devm_kvasprintf() to format some of its arguments. Adding a __printf attribute to this function makes it possible to detect at compile-time errors related to format strings. Signed-off-by: Nicolas Iooss --- include/sound/simple_card_utils.h | 1 + 1

[PATCH v2 2/2] MAINTAINERS: document ASoC header files

include/sound/simple_card_utils.h is handled by ASoC maintainers, as stated in https://lkml.org/lkml/2016/8/22/307, and include/sound/simple_card.h seems to be an ASoC file too. In the future there will be more files named like these ones so introduce a pattern to match them. Signed-off-by:

Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)

On Tue, Jul 5, 2016 at 8:42 AM, Grant Likely wrote: > > On 22/06/16 06:40, Srinivas Pandruvada wrote: >> >> Change log >> v2: >> - Overview in documentation show analogy with usbhid implementation >> - sparse errors for statics. Also pointed by Jiri >> - Clearly marking

Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)

On Tue, Jul 5, 2016 at 8:42 AM, Grant Likely wrote: > > On 22/06/16 06:40, Srinivas Pandruvada wrote: >> >> Change log >> v2: >> - Overview in documentation show analogy with usbhid implementation >> - sparse errors for statics. Also pointed by Jiri >> - Clearly marking exported function header

Re: wan-cosa: Use memdup_user() rather than duplicating its implementation

> What about the GFP_DMA attribute, which your patch deletes? > The buffer in question has to be ISA DMA-able. Thanks for your constructive feedback. Would you be interested in using a variant of the function "memdup_…" with which the corresponding memory allocation option can be

Re: wan-cosa: Use memdup_user() rather than duplicating its implementation

> What about the GFP_DMA attribute, which your patch deletes? > The buffer in question has to be ISA DMA-able. Thanks for your constructive feedback. Would you be interested in using a variant of the function "memdup_…" with which the corresponding memory allocation option can be

Re: [RFC] mm: Don't use radix tree writeback tags for pages in swap cache

"Huang, Ying" writes: > Hi, Dave, > > Dave Hansen writes: > >> On 08/09/2016 09:17 AM, Huang, Ying wrote: >>> File pages uses a set of radix tags (DIRTY, TOWRITE, WRITEBACK) to >>> accelerate finding the pages with the specific tag in the the radix

Re: [PATCH v6 1/3] fork: Add generic vmalloced stack support

On Wed, Aug 24, 2016 at 3:03 AM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> +config VMAP_STACK >> + default y >> + bool "Use a virtually-mapped stack" >> + depends on HAVE_ARCH_VMAP_STACK && !KASAN >> + ---help--- >> + Enable

Re: [RFC] mm: Don't use radix tree writeback tags for pages in swap cache

"Huang, Ying" writes: > Hi, Dave, > > Dave Hansen writes: > >> On 08/09/2016 09:17 AM, Huang, Ying wrote: >>> File pages uses a set of radix tags (DIRTY, TOWRITE, WRITEBACK) to >>> accelerate finding the pages with the specific tag in the the radix tree >>> during writing back an inode. But

Re: [PATCH v6 1/3] fork: Add generic vmalloced stack support

On Wed, Aug 24, 2016 at 3:03 AM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> +config VMAP_STACK >> + default y >> + bool "Use a virtually-mapped stack" >> + depends on HAVE_ARCH_VMAP_STACK && !KASAN >> + ---help--- >> + Enable this if you want the use

Re: [PATCH v1 01/10] sched/fair: Chance LOAD_AVG_MAX_N from 345 to 347

On 10 August 2016 at 02:14, Yuyang Du wrote: > In commit 5b51f2f80b3b906ce59bd4dce6eca3c7f34cb1b9 > Author: Paul Turner > Date: Thu Oct 4 13:18:32 2012 +0200 > > sched: Make __update_entity_runnable_avg() fast > > Paul has a program to compute

Re: [PATCH v1 01/10] sched/fair: Chance LOAD_AVG_MAX_N from 345 to 347

On 10 August 2016 at 02:14, Yuyang Du wrote: > In commit 5b51f2f80b3b906ce59bd4dce6eca3c7f34cb1b9 > Author: Paul Turner > Date: Thu Oct 4 13:18:32 2012 +0200 > > sched: Make __update_entity_runnable_avg() fast > > Paul has a program to compute LOAD_AVG_MAX_N, which basically means > how

[PATCH] ARM: plat-pxa: Use kmalloc_array() in pxa_dma_init_debugfs()

From: Markus Elfring Date: Wed, 24 Aug 2016 17:45:51 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kmalloc_array". This issue was detected

[PATCH] ARM: plat-pxa: Use kmalloc_array() in pxa_dma_init_debugfs()

From: Markus Elfring Date: Wed, 24 Aug 2016 17:45:51 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

Re: [PATCH 5/5] arm64: Add uprobe support

On Wed, Aug 24, 2016 at 05:47:11PM +0200, Oleg Nesterov wrote: > On 08/24, Pratyush Anand wrote: > > > > > I don't think we want user_{enable,disable{_single_step in the long term, > > > please look at 9bd1190a11c9d2 "uprobes/x86: Do not (ab)use TIF_SINGLESTEP > > > /user_*_single_step() for

Re: [PATCH v2 3/6] dt/bindings: Add bindings for Tegra GMI controller

On 24/08/16 14:37, Mirza Krak wrote: > From: Mirza Krak > > Document the devicetree bindings for the Generic Memory Interface (GMI) > bus driver found on Tegra SOCs. > > Signed-off-by: Mirza Krak > --- > Changes in v2: > - Updated examples and some

Re: [PATCH 5/5] arm64: Add uprobe support

On Wed, Aug 24, 2016 at 05:47:11PM +0200, Oleg Nesterov wrote: > On 08/24, Pratyush Anand wrote: > > > > > I don't think we want user_{enable,disable{_single_step in the long term, > > > please look at 9bd1190a11c9d2 "uprobes/x86: Do not (ab)use TIF_SINGLESTEP > > > /user_*_single_step() for

Re: [PATCH v2 3/6] dt/bindings: Add bindings for Tegra GMI controller

On 24/08/16 14:37, Mirza Krak wrote: > From: Mirza Krak > > Document the devicetree bindings for the Generic Memory Interface (GMI) > bus driver found on Tegra SOCs. > > Signed-off-by: Mirza Krak > --- > Changes in v2: > - Updated examples and some information based on comments from Jon

Re: [PATCH 5/5] arm64: Add uprobe support

Hi Pratyush, On 08/24, Pratyush Anand wrote: > > > I don't think we want user_{enable,disable{_single_step in the long term, > > please look at 9bd1190a11c9d2 "uprobes/x86: Do not (ab)use TIF_SINGLESTEP > > /user_*_single_step() for single-stepping". it seems that ARM64 sets/clears > >

Re: [PATCH 5/5] arm64: Add uprobe support

Hi Pratyush, On 08/24, Pratyush Anand wrote: > > > I don't think we want user_{enable,disable{_single_step in the long term, > > please look at 9bd1190a11c9d2 "uprobes/x86: Do not (ab)use TIF_SINGLESTEP > > /user_*_single_step() for single-stepping". it seems that ARM64 sets/clears > >

Re: [PATCH 01/10] reset: ath79: add driver Kconfig option

On Wednesday, August 24, 2016 3:28:53 PM CEST Philipp Zabel wrote: > if RESET_CONTROLLER > > +config RESET_ATH79 > + bool "AR71xx Reset Driver" if COMPILE_TEST > + default ATH79 > + help > + This enables the ATH79 reset controller driver that supports the > +

Re: [PATCH 01/10] reset: ath79: add driver Kconfig option

On Wednesday, August 24, 2016 3:28:53 PM CEST Philipp Zabel wrote: > if RESET_CONTROLLER > > +config RESET_ATH79 > + bool "AR71xx Reset Driver" if COMPILE_TEST > + default ATH79 > + help > + This enables the ATH79 reset controller driver that supports the > +

Re: [PATCH] wan-cosa: Use memdup_user() rather than duplicating its implementation

Hello, SF Markus Elfring wrote: : From: Markus Elfring : Date: Sat, 20 Aug 2016 10:10:12 +0200 : : Reuse existing functionality from memdup_user() instead of keeping : duplicate source code. : : This issue was detected by using the Coccinelle software.

Re: [PATCH] wan-cosa: Use memdup_user() rather than duplicating its implementation

Hello, SF Markus Elfring wrote: : From: Markus Elfring : Date: Sat, 20 Aug 2016 10:10:12 +0200 : : Reuse existing functionality from memdup_user() instead of keeping : duplicate source code. : : This issue was detected by using the Coccinelle software. What about the GFP_DMA

Re: [PATCH v2] kernel/fork: fix CLONE_CHILD_CLEARTID regression in nscd

On Wed 24-08-16 17:32:00, Oleg Nesterov wrote: > On 08/24, Michal Hocko wrote: > > > > Sounds better? > > diff --git a/kernel/fork.c b/kernel/fork.c > > index b89f0eb99f0a..ddde5849df81 100644 > > --- a/kernel/fork.c > > +++ b/kernel/fork.c > > @@ -914,7 +914,8 @@ void mm_release(struct

Re: [PATCH v2] kernel/fork: fix CLONE_CHILD_CLEARTID regression in nscd

On Wed 24-08-16 17:32:00, Oleg Nesterov wrote: > On 08/24, Michal Hocko wrote: > > > > Sounds better? > > diff --git a/kernel/fork.c b/kernel/fork.c > > index b89f0eb99f0a..ddde5849df81 100644 > > --- a/kernel/fork.c > > +++ b/kernel/fork.c > > @@ -914,7 +914,8 @@ void mm_release(struct

Re: [PATCH v2] misc: retire the old BMP085 driver

On Wednesday, August 24, 2016 4:38:52 PM CEST Linus Walleij wrote: > Patches merged to the IIO BMP085 driver makes it fully compliant > with all features found in this old misc driver. Retire this old > driver in favor of the new one in the proper subsystem. > > Cc: Arnd Bergmann

Re: [PATCH v2] misc: retire the old BMP085 driver

On Wednesday, August 24, 2016 4:38:52 PM CEST Linus Walleij wrote: > Patches merged to the IIO BMP085 driver makes it fully compliant > with all features found in this old misc driver. Retire this old > driver in favor of the new one in the proper subsystem. > > Cc: Arnd Bergmann > Acked-by:

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

Hi, Mel, Mel Gorman writes: > On Wed, Aug 17, 2016 at 04:49:07PM +0100, Mel Gorman wrote: >> > Yes, we could try to batch the locking like DaveC already suggested >> > (ie we could move the locking to the caller, and then make >> > shrink_page_list() just try to

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

Hi, Mel, Mel Gorman writes: > On Wed, Aug 17, 2016 at 04:49:07PM +0100, Mel Gorman wrote: >> > Yes, we could try to batch the locking like DaveC already suggested >> > (ie we could move the locking to the caller, and then make >> > shrink_page_list() just try to keep the lock held for a few

Re: [patch 2/2] i2c: mux: mellanox: add driver

On 2016-08-24 15:56, Vadim Pasternak wrote: > From: Vadim Pasternak > > This driver allows I2C routing controlled through CPLD select registers on > wide > range of Mellanox systems (CPLD Lattice device). > MUX selection is provided by digital and analog HW. Analog part is

Re: [patch 2/2] i2c: mux: mellanox: add driver

On 2016-08-24 15:56, Vadim Pasternak wrote: > From: Vadim Pasternak > > This driver allows I2C routing controlled through CPLD select registers on > wide > range of Mellanox systems (CPLD Lattice device). > MUX selection is provided by digital and analog HW. Analog part is not under > SW >

Re: [PATCH 3/4] dt-binding: remoteproc: venus rproc dt binding document

Hi Rob, On 08/23/2016 08:32 PM, Rob Herring wrote: > On Fri, Aug 19, 2016 at 06:53:19PM +0300, Stanimir Varbanov wrote: >> Add devicetree binding document for Venus remote processor. >> >> Signed-off-by: Stanimir Varbanov >> --- >>

Re: [PATCH 3/4] dt-binding: remoteproc: venus rproc dt binding document

Hi Rob, On 08/23/2016 08:32 PM, Rob Herring wrote: > On Fri, Aug 19, 2016 at 06:53:19PM +0300, Stanimir Varbanov wrote: >> Add devicetree binding document for Venus remote processor. >> >> Signed-off-by: Stanimir Varbanov >> --- >> .../devicetree/bindings/remoteproc/qcom,venus.txt | 33 >>

Re: [PATCH v2] kernel/fork: fix CLONE_CHILD_CLEARTID regression in nscd

On 08/24, Michal Hocko wrote: > > Sounds better? > diff --git a/kernel/fork.c b/kernel/fork.c > index b89f0eb99f0a..ddde5849df81 100644 > --- a/kernel/fork.c > +++ b/kernel/fork.c > @@ -914,7 +914,8 @@ void mm_release(struct task_struct *tsk, struct mm_struct > *mm) > > /* >*

Re: [PATCH v2] kernel/fork: fix CLONE_CHILD_CLEARTID regression in nscd

On 08/24, Michal Hocko wrote: > > Sounds better? > diff --git a/kernel/fork.c b/kernel/fork.c > index b89f0eb99f0a..ddde5849df81 100644 > --- a/kernel/fork.c > +++ b/kernel/fork.c > @@ -914,7 +914,8 @@ void mm_release(struct task_struct *tsk, struct mm_struct > *mm) > > /* >*

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, 2016-08-23 at 22:48 -0700, Dan Williams wrote: > On Tue, Aug 23, 2016 at 8:58 PM, Dan Williams > > > > Does the attached patch fix this for you? > > Sorry, should be this much simpler patch that also mirrors what > driver/nvdimm/pmem.c is doing... Yes, this

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, 2016-08-23 at 22:48 -0700, Dan Williams wrote: > On Tue, Aug 23, 2016 at 8:58 PM, Dan Williams > > > > Does the attached patch fix this for you? > > Sorry, should be this much simpler patch that also mirrors what > driver/nvdimm/pmem.c is doing... Yes, this change works fine. :-)

Re: linux kernel 3.19.X does not load when compiled with binutils 2.6, works fine when compiled with binutils 2.22

On Wed, Aug 24, 2016 at 04:42:20PM +0200, luigi.gen...@it.telecomitalia.it wrote: > Hi all, > > recentrly I was in need to compile and run linux kernel 3.19.8 on some > servers, with different bios and cpus. > > so i noticed that If i compile this kernel with binutils 2.6 (and 2.7) it > does

Re: linux kernel 3.19.X does not load when compiled with binutils 2.6, works fine when compiled with binutils 2.22

On Wed, Aug 24, 2016 at 04:42:20PM +0200, luigi.gen...@it.telecomitalia.it wrote: > Hi all, > > recentrly I was in need to compile and run linux kernel 3.19.8 on some > servers, with different bios and cpus. > > so i noticed that If i compile this kernel with binutils 2.6 (and 2.7) it > does

Re: [PATCH 2/2] arm64: dts: set UART1 clock frequency to 150MHz

Hi Jorge, On 08/07/2016 09:11, Jorge Ramirez-Ortiz wrote: > Enable support for higher baud rates (up to 3Mbps) in UART1 - required > for bluetooth transfers. > > Signed-off-by: Jorge Ramirez-Ortiz > Tested-by: Jorge Ramirez-Ortiz

Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier)

On Thursday, August 18, 2016 3:46:17 AM CEST Masahiro Yamada wrote: > 2016-01-18 22:49 GMT+09:00 Arnd Bergmann : > > On Monday 18 January 2016 19:54:08 Masahiro Yamada wrote: > > I collected a couple of GPG signatures and > finally, I managed to host my git tree in the kernel.org

Re: [PATCH 2/2] arm64: dts: set UART1 clock frequency to 150MHz

Hi Jorge, On 08/07/2016 09:11, Jorge Ramirez-Ortiz wrote: > Enable support for higher baud rates (up to 3Mbps) in UART1 - required > for bluetooth transfers. > > Signed-off-by: Jorge Ramirez-Ortiz > Tested-by: Jorge Ramirez-Ortiz > --- Applied to the hisi-dt-4.9 branch. Thanks! Best Regards,

Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier)

On Thursday, August 18, 2016 3:46:17 AM CEST Masahiro Yamada wrote: > 2016-01-18 22:49 GMT+09:00 Arnd Bergmann : > > On Monday 18 January 2016 19:54:08 Masahiro Yamada wrote: > > I collected a couple of GPG signatures and > finally, I managed to host my git tree in the kernel.org site. > > From

Re: [PATCH v05 14/72] include/uapi/asm-generic/ipcbuf.h: include linux/posix_types.h

On Monday, August 22, 2016 8:32:31 PM CEST Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘__kernel_key_t’ > > Signed-off-by: Mikko Rapeli > Looks good. I was on Cc for patches 14, 15, 16, 17, 18, 35, 65 and 71. They all seem

Re: [PATCH v05 14/72] include/uapi/asm-generic/ipcbuf.h: include linux/posix_types.h

On Monday, August 22, 2016 8:32:31 PM CEST Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘__kernel_key_t’ > > Signed-off-by: Mikko Rapeli > Looks good. I was on Cc for patches 14, 15, 16, 17, 18, 35, 65 and 71. They all seem reasonable to me, the only

<    2   3   4   5   6   7   8   9   10   11   >