[PATCH] device probe: add self triggered delayed work request

In normal condition, the device probe requests kept in deferred queue would only be triggered for re-probing when another new device probe is finished successfully. This change will set up a delayed trigger work request if the current deferred probe being added is the only one in the queue. This

[PATCH] device probe: add self triggered delayed work request

In normal condition, the device probe requests kept in deferred queue would only be triggered for re-probing when another new device probe is finished successfully. This change will set up a delayed trigger work request if the current deferred probe being added is the only one in the queue. This

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Fri 29 Jul 21:39 PDT 2016, John Stultz wrote: > Hey Jon, > So after rebasing my nexus7 patch stack onto pre-4.8-rc1 tree, I > noticed the power/volume buttons stopped working. > +Linus, as that's gpio-keys on top of two fairly standard gpio/pinctrl drivers (8064 TLMM and SSBI). Regards,

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Fri 29 Jul 21:39 PDT 2016, John Stultz wrote: > Hey Jon, > So after rebasing my nexus7 patch stack onto pre-4.8-rc1 tree, I > noticed the power/volume buttons stopped working. > +Linus, as that's gpio-keys on top of two fairly standard gpio/pinctrl drivers (8064 TLMM and SSBI). Regards,

[Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

Hey Jon, So after rebasing my nexus7 patch stack onto pre-4.8-rc1 tree, I noticed the power/volume buttons stopped working. I did a manual rebased bisection and chased it down to your commit 1e2a7d78499e ("irqdomain: Don't set type when mapping an IRQ"). Reverting that patch makes things work

[Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

Hey Jon, So after rebasing my nexus7 patch stack onto pre-4.8-rc1 tree, I noticed the power/volume buttons stopped working. I did a manual rebased bisection and chased it down to your commit 1e2a7d78499e ("irqdomain: Don't set type when mapping an IRQ"). Reverting that patch makes things work

Re: [GIT PULL] usercopy protection for v4.8

On Tue, Jul 26, 2016 at 8:53 PM, Kees Cook wrote: > On Tue, Jul 26, 2016 at 2:55 PM, Kees Cook wrote: >> Hi, >> >> This is my next pull request for v4.8, which introduces a kernel self >> protection of copy_to_user/copy_from_user that has been under

Re: [GIT PULL] usercopy protection for v4.8

On Tue, Jul 26, 2016 at 8:53 PM, Kees Cook wrote: > On Tue, Jul 26, 2016 at 2:55 PM, Kees Cook wrote: >> Hi, >> >> This is my next pull request for v4.8, which introduces a kernel self >> protection of copy_to_user/copy_from_user that has been under review and >> test on the kernel-hardening

Re: Build failure in linux mainline when building arcv2 images

On 07/29/2016 03:46 PM, Vineet Gupta wrote: What you want is 2016-05-19 09439560b9f9 toolchain: bump ARC tools to arc-2016.03 release which seems to be present in released 2016.05, but when I checkout 2016.05 tag (or aa6fd11feebff) that patch is not there ! A toolchain build off SHA

Re: Build failure in linux mainline when building arcv2 images

On 07/29/2016 03:46 PM, Vineet Gupta wrote: What you want is 2016-05-19 09439560b9f9 toolchain: bump ARC tools to arc-2016.03 release which seems to be present in released 2016.05, but when I checkout 2016.05 tag (or aa6fd11feebff) that patch is not there ! A toolchain build off SHA

[PATCH] fs: fix a bug when new_insert_key is not initialization

From: zhong jiang when compile the kenrel code, I happens to the following warn. fs/reiserfs/ibalance.c:1156:2: warning: ‘new_insert_key’ may be used uninitialized in this function. memcpy(new_insert_key_addr, _insert_key, KEY_SIZE); The patch fix it by check the

[PATCH] fs: fix a bug when new_insert_key is not initialization

From: zhong jiang when compile the kenrel code, I happens to the following warn. fs/reiserfs/ibalance.c:1156:2: warning: ‘new_insert_key’ may be used uninitialized in this function. memcpy(new_insert_key_addr, _insert_key, KEY_SIZE); The patch fix it by check the new_insert_ptr. if

Re: [PATCH] perf/core: Add a tracepoint for perf sampling

On 2016/7/30 2:05, Brendan Gregg wrote: On Tue, Jul 19, 2016 at 4:20 PM, Brendan Gregg wrote: When perf is performing hrtimer-based sampling, this tracepoint can be used by BPF to run additional logic on each sample. For example, BPF can fetch stack traces and frequency

Re: [PATCH] perf/core: Add a tracepoint for perf sampling

On 2016/7/30 2:05, Brendan Gregg wrote: On Tue, Jul 19, 2016 at 4:20 PM, Brendan Gregg wrote: When perf is performing hrtimer-based sampling, this tracepoint can be used by BPF to run additional logic on each sample. For example, BPF can fetch stack traces and frequency count them in kernel

Re: [PATCH v4 2/2] spi: add driver for J-Core SPI controller

On Thu, Jul 28, 2016 at 08:51:25PM +0100, Mark Brown wrote: > On Thu, Jul 28, 2016 at 03:40:45PM -0400, Rich Felker wrote: > > On Thu, Jul 28, 2016 at 08:11:53PM +0100, Mark Brown wrote: > > > > An architecture or SoC dependency with || COMPILE_TEST would be useful > > > for avoiding cluttering

Re: [PATCH v4 2/2] spi: add driver for J-Core SPI controller

On Thu, Jul 28, 2016 at 08:51:25PM +0100, Mark Brown wrote: > On Thu, Jul 28, 2016 at 03:40:45PM -0400, Rich Felker wrote: > > On Thu, Jul 28, 2016 at 08:11:53PM +0100, Mark Brown wrote: > > > > An architecture or SoC dependency with || COMPILE_TEST would be useful > > > for avoiding cluttering

[PATCH] MAINTAINERS: update email for Sasha Levin

New position, new email address. Signed-off-by: Sasha Levin --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 8c20323..85fd4ee 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -6802,7 +6802,7 @@ S:

[PATCH 0/8] liblockdep fixes for 3.8

Hi Ingo, A bunch of fixes that I dropped the ball on back in 3.7. Mostly compilation fixes for errors that have happened due to changes on the kernel side in 3.7. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32

From: Ben Hutchings __lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled.

[PATCH] MAINTAINERS: update email for Sasha Levin

New position, new email address. Signed-off-by: Sasha Levin --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 8c20323..85fd4ee 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -6802,7 +6802,7 @@ S:Maintained F:

[PATCH 0/8] liblockdep fixes for 3.8

Hi Ingo, A bunch of fixes that I dropped the ball on back in 3.7. Mostly compilation fixes for errors that have happened due to changes on the kernel side in 3.7. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32

From: Ben Hutchings __lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled. Fixes: e7904a28f533

[PATCH 8/8] liblockdep: Remove -lpthread compiler option

From: Vishal Thanki With -lpthread option, the test for ABBA_2threads was failing, and test passed if it was removed. Since -pthread compiler option is sufficient for linking to pthread libraries, this patch removes -lpthread. Signed-off-by: Vishal Thanki

Re: [RFC] perf uprobe: Skip prologue if program compiled without optimization

On Thu, 28 Jul 2016 20:01:51 +0530 Ravi Bangoria wrote: > Function prologue prepares stack and registers before executing function > logic. When target program is compiled without optimization, function > parameter information is only valid after prologue. When

[PATCH 6/8] liblockdep: Fix 'set but not used' warnings

From: Ben Hutchings liblockdep defines trivial macros for working with interrupt flags, as interrupts are never disabled in userland. This results in warnings from gcc when -Wunused-but-set-variable is enabled, and it is enabled by -Wall. Fix this by evaluating the flags

[PATCH resend 0/8] liblockdep fixes for 3.8

Hi Ingo, A bunch of fixes that I dropped the ball on back in 3.7. Mostly compilation fixes for errors that have happened due to changes on the kernel side in 3.7. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 8/8] liblockdep: Remove -lpthread compiler option

From: Vishal Thanki With -lpthread option, the test for ABBA_2threads was failing, and test passed if it was removed. Since -pthread compiler option is sufficient for linking to pthread libraries, this patch removes -lpthread. Signed-off-by: Vishal Thanki Signed-off-by: Sasha Levin ---

Re: [RFC] perf uprobe: Skip prologue if program compiled without optimization

On Thu, 28 Jul 2016 20:01:51 +0530 Ravi Bangoria wrote: > Function prologue prepares stack and registers before executing function > logic. When target program is compiled without optimization, function > parameter information is only valid after prologue. When we probe entrypc > of the

[PATCH 6/8] liblockdep: Fix 'set but not used' warnings

From: Ben Hutchings liblockdep defines trivial macros for working with interrupt flags, as interrupts are never disabled in userland. This results in warnings from gcc when -Wunused-but-set-variable is enabled, and it is enabled by -Wall. Fix this by evaluating the flags parameter and casting

[PATCH resend 0/8] liblockdep fixes for 3.8

Hi Ingo, A bunch of fixes that I dropped the ball on back in 3.7. Mostly compilation fixes for errors that have happened due to changes on the kernel side in 3.7. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 5/8] liblockdep: Fix 'unused value' warnings

From: Ben Hutchings liblockdep defines various macros that may expand to an expression with no effect, while the in-kernel definition does have an effect. This results in warnings from gcc when -Wunused-value is enabled, and is is enabled by -Wall. Fix this by introducing

[PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32

From: Ben Hutchings __lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled.

[PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32

From: Ben Hutchings __lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled.

[PATCH 5/8] liblockdep: Fix 'unused value' warnings

From: Ben Hutchings liblockdep defines various macros that may expand to an expression with no effect, while the in-kernel definition does have an effect. This results in warnings from gcc when -Wunused-value is enabled, and is is enabled by -Wall. Fix this by introducing trivial functions, as

[PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32

From: Ben Hutchings __lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled. Fixes: e7904a28f533

[PATCH 1/8] liblockdep: Fix undefined symbol prandom_u32

From: Ben Hutchings __lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled. Fixes: e7904a28f533

[PATCH resend 0/8] liblockdep fixes for 3.8

Hi Ingo, A bunch of fixes that I dropped the ball on back in 3.7. Mostly compilation fixes for errors that have happened due to changes on the kernel side in 3.7. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 4/8] liblockdep: Enable -Wall by default

From: Ben Hutchings Regressions in liblockdep may be missed because it doesn't enable warnings. Adding -Wall immediately introduces a lot of warnings, but those will be fixed by the following commits. Signed-off-by: Ben Hutchings Signed-off-by:

[PATCH resend 0/8] liblockdep fixes for 3.8

Hi Ingo, A bunch of fixes that I dropped the ball on back in 3.7. Mostly compilation fixes for errors that have happened due to changes on the kernel side in 3.7. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 4/8] liblockdep: Enable -Wall by default

From: Ben Hutchings Regressions in liblockdep may be missed because it doesn't enable warnings. Adding -Wall immediately introduces a lot of warnings, but those will be fixed by the following commits. Signed-off-by: Ben Hutchings Signed-off-by: Sasha Levin --- tools/lib/lockdep/Makefile | 1

[PATCH 2/8] liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth

From: Ben Hutchings liblockdep has been broken since commit 75dd602a5198 ("lockdep: Fix lock_chain::base size"), as that adds a check that MAX_LOCK_DEPTH is within the range of lock_chain::depth and in liblockdep it is much too large. That should have resulted in a

[PATCH 2/8] liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth

From: Ben Hutchings liblockdep has been broken since commit 75dd602a5198 ("lockdep: Fix lock_chain::base size"), as that adds a check that MAX_LOCK_DEPTH is within the range of lock_chain::depth and in liblockdep it is much too large. That should have resulted in a compiler error, but didn't

[PATCH 3/8] liblockdep: Define the ARRAY_SIZE() macro

From: Ben Hutchings lockdep.c now uses ARRAY_SIZE(). Fixes: 75dd602a5198 ("lockdep: Fix lock_chain::base size") Signed-off-by: Ben Hutchings Signed-off-by: Sasha Levin --- tools/lib/lockdep/uinclude/linux/kernel.h | 2

[PATCH 7/8] liblockdep: Fix 'defined but not used' warning for init_utsname()

From: Ben Hutchings We define init_utsname() as static but not inline, resulting in a warning for every source file that includes lockdep.h but doesn't call it. Since it is only used by lockdep.c, define it in there. Signed-off-by: Ben Hutchings

[PATCH 3/8] liblockdep: Define the ARRAY_SIZE() macro

From: Ben Hutchings lockdep.c now uses ARRAY_SIZE(). Fixes: 75dd602a5198 ("lockdep: Fix lock_chain::base size") Signed-off-by: Ben Hutchings Signed-off-by: Sasha Levin --- tools/lib/lockdep/uinclude/linux/kernel.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 7/8] liblockdep: Fix 'defined but not used' warning for init_utsname()

From: Ben Hutchings We define init_utsname() as static but not inline, resulting in a warning for every source file that includes lockdep.h but doesn't call it. Since it is only used by lockdep.c, define it in there. Signed-off-by: Ben Hutchings Signed-off-by: Sasha Levin ---

Re: [PATCH] fs: wipe off the compiler warn

On 2016/7/30 7:02, Andrew Morton wrote: > On Fri, 29 Jul 2016 22:46:39 +0800 zhongjiang wrote: > >> From: zhong jiang >> >> when compile the kenrel code, I happens to the following warn. >> fs/reiserfs/ibalance.c:1156:2: warning: ___new_insert_key___

Re: [PATCH] fs: wipe off the compiler warn

On 2016/7/30 7:02, Andrew Morton wrote: > On Fri, 29 Jul 2016 22:46:39 +0800 zhongjiang wrote: > >> From: zhong jiang >> >> when compile the kenrel code, I happens to the following warn. >> fs/reiserfs/ibalance.c:1156:2: warning: ___new_insert_key___ may be used >> uninitialized in this

Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues

On Fri, 29 Jul 2016 19:50:59 -0500 Josh Poimboeuf wrote: > BTW, it would be really nice if ftrace_graph_ret_addr() were idempotent > so we could get the "real" return address without having to pass in a > state variable. > > For example we could add an "unsigned long *retp"

Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues

On Fri, 29 Jul 2016 19:50:59 -0500 Josh Poimboeuf wrote: > BTW, it would be really nice if ftrace_graph_ret_addr() were idempotent > so we could get the "real" return address without having to pass in a > state variable. > > For example we could add an "unsigned long *retp" pointer to >

Re: [PATCH 1/2] Documentation: kdump: update maxcpus to nr_cpus

On 07/29/16 at 11:23am, Zhou Wenjian wrote: > Parameter nr_cpus is used to bring up a SMP dump-capture kernel, > instead of the old parameter maxcpus. This commit update it in > Documentation/kdump/kdump.txt. > > Signed-off-by: Zhou Wenjian > --- >

Re: [PATCH 1/2] Documentation: kdump: update maxcpus to nr_cpus

On 07/29/16 at 11:23am, Zhou Wenjian wrote: > Parameter nr_cpus is used to bring up a SMP dump-capture kernel, > instead of the old parameter maxcpus. This commit update it in > Documentation/kdump/kdump.txt. > > Signed-off-by: Zhou Wenjian > --- > Documentation/kdump/kdump.txt | 2 +- > 1 file

Re: [Query] Preemption (hogging) of the work handler

On (07/29/16 13:42), Viresh Kumar wrote: [..] > I haven't seen any issues with it yet and it works just fine. Please feel free > to add below for the entire series including this hunk. > > Tested-by: Viresh Kumar Thanks a lot! will refresh the series next week. sorry,

Re: [Query] Preemption (hogging) of the work handler

On (07/29/16 13:42), Viresh Kumar wrote: [..] > I haven't seen any issues with it yet and it works just fine. Please feel free > to add below for the entire series including this hunk. > > Tested-by: Viresh Kumar Thanks a lot! will refresh the series next week. sorry, haven't gotten many

[PATCH] staging: ion: remove __GFP_NOWARN when use low order gfp flags

It's useful to show the current memory in detail when alloc failed. And, there may be a lot of high order alloc failed, just show memory when an order 0 alloc failed. Signed-off-by: Chen Feng --- drivers/staging/android/ion/ion_system_heap.c | 2 +- 1 file changed, 1

[PATCH] staging: ion: remove __GFP_NOWARN when use low order gfp flags

It's useful to show the current memory in detail when alloc failed. And, there may be a lot of high order alloc failed, just show memory when an order 0 alloc failed. Signed-off-by: Chen Feng --- drivers/staging/android/ion/ion_system_heap.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

On Fri, 2016-07-29 at 21:41 -0400, Allen Hubbe wrote: > Mystery solved... and drop this patch. > > My 'master' on this system was set to an old ref, v4.2-rc1.  There are > no perl warnings as of v4.7. OK great, thanks. I had just built and tested with 5.24 and didn't see any warnings and

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

On Fri, 2016-07-29 at 21:41 -0400, Allen Hubbe wrote: > Mystery solved... and drop this patch. > > My 'master' on this system was set to an old ref, v4.2-rc1.  There are > no perl warnings as of v4.7. OK great, thanks. I had just built and tested with 5.24 and didn't see any warnings and

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

On Fri, Jul 29, 2016 at 7:57 PM, Allen Hubbe wrote: > On Fri, Jul 29, 2016 at 7:06 PM, Joe Perches wrote: >> On Fri, 2016-07-29 at 18:27 -0400, Allen Hubbe wrote: >>> Perl warns: >>> >>> Unescaped left brace in regex is deprecated, passed through in regex >>>

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

On Fri, Jul 29, 2016 at 7:57 PM, Allen Hubbe wrote: > On Fri, Jul 29, 2016 at 7:06 PM, Joe Perches wrote: >> On Fri, 2016-07-29 at 18:27 -0400, Allen Hubbe wrote: >>> Perl warns: >>> >>> Unescaped left brace in regex is deprecated, passed through in regex >>> >>> This is explained under

Re: [PATCH v2 1/5] ethernet: add sun8i-emac driver

On Sat, Jul 30, 2016 at 1:25 AM, Maxime Ripard wrote: > On Thu, Jul 28, 2016 at 04:57:34PM +0200, LABBE Corentin wrote: >> > > +static int sun8i_mdio_write(struct mii_bus *bus, int phy_addr, int >> > > phy_reg, >> > > + u16 data) >> > > +{ >>

Re: [PATCH v2 1/5] ethernet: add sun8i-emac driver

On Sat, Jul 30, 2016 at 1:25 AM, Maxime Ripard wrote: > On Thu, Jul 28, 2016 at 04:57:34PM +0200, LABBE Corentin wrote: >> > > +static int sun8i_mdio_write(struct mii_bus *bus, int phy_addr, int >> > > phy_reg, >> > > + u16 data) >> > > +{ >> > > + struct net_device *ndev =

[RFC][PATCH] pstore: use DT reserved-memory bindings

Instead of a ramoops-specific node, use a child node of /reserved-memory. This requires that of_platform_populate() be called for the node, though, since it does not have its own "compatible" property. Suggested-by: Rob Herring Signed-off-by: Kees Cook

[RFC][PATCH] pstore: use DT reserved-memory bindings

Instead of a ramoops-specific node, use a child node of /reserved-memory. This requires that of_platform_populate() be called for the node, though, since it does not have its own "compatible" property. Suggested-by: Rob Herring Signed-off-by: Kees Cook --- Here's what I've got for moving

Re: [PATCH] arm64: dts: rockchip: add spiX aliases for rk3399

On Fri, Jul 29, 2016 at 04:39:51PM -0700, Brian Norris wrote: > + Mark I very nearly deleted this unread based on the subject line... > I had read that already. I figured that was just rationale for not > documenting the feature (still silly IMO), and not for avoiding using > the existing

Re: [PATCH] arm64: dts: rockchip: add spiX aliases for rk3399

On Fri, Jul 29, 2016 at 04:39:51PM -0700, Brian Norris wrote: > + Mark I very nearly deleted this unread based on the subject line... > I had read that already. I figured that was just rationale for not > documenting the feature (still silly IMO), and not for avoiding using > the existing

[PATCH] Networking: Core: netpoll: Fixed a missing spin_unlock

In the case when the loop breaks at line 390, the txq lock is not released. Added an unlock statement before the break statement. Signed-off-by: Salil Kapur --- net/core/netpoll.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/net/core/netpoll.c

[PATCH] Networking: Core: netpoll: Fixed a missing spin_unlock

In the case when the loop breaks at line 390, the txq lock is not released. Added an unlock statement before the break statement. Signed-off-by: Salil Kapur --- net/core/netpoll.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/net/core/netpoll.c b/net/core/netpoll.c

Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues

On Fri, Jul 29, 2016 at 06:55:21PM -0400, Steven Rostedt wrote: > On Thu, 21 Jul 2016 16:21:42 -0500 > Josh Poimboeuf wrote: > > > When function graph tracing is enabled for a function, its return > > address on the stack is replaced with the address of an ftrace handler > >

Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues

On Fri, Jul 29, 2016 at 06:55:21PM -0400, Steven Rostedt wrote: > On Thu, 21 Jul 2016 16:21:42 -0500 > Josh Poimboeuf wrote: > > > When function graph tracing is enabled for a function, its return > > address on the stack is replaced with the address of an ftrace handler > > (return_to_handler).

Re: [PATCH] Revert "pstore/ram: add Device Tree bindings"

On Thu, Jul 28, 2016 at 3:44 PM, Kees Cook wrote: > On Thu, Jul 28, 2016 at 2:10 PM, Rob Herring wrote: >> On Thu, Jul 28, 2016 at 3:50 PM, Kees Cook wrote: >>> On Thu, Jul 28, 2016 at 1:25 PM, Rob Herring wrote:

Re: [PATCH] Revert "pstore/ram: add Device Tree bindings"

On Thu, Jul 28, 2016 at 3:44 PM, Kees Cook wrote: > On Thu, Jul 28, 2016 at 2:10 PM, Rob Herring wrote: >> On Thu, Jul 28, 2016 at 3:50 PM, Kees Cook wrote: >>> On Thu, Jul 28, 2016 at 1:25 PM, Rob Herring wrote: This reverts commit 35da60941e44dbf57868e67686dd24cc1a33125a. ---

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

This system has v5.22.1. I don't know exactly how this perl was configured. I didn't see the warning on other systems. Strangely, I don't remember seeing it yesterday on this system, either. I might try to reproduce the warning on another system and let you know. The warning and this fix seem

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

This system has v5.22.1. I don't know exactly how this perl was configured. I didn't see the warning on other systems. Strangely, I don't remember seeing it yesterday on this system, either. I might try to reproduce the warning on another system and let you know. The warning and this fix seem

Re: [PATCH] arm64: dts: rockchip: add spiX aliases for rk3399

+ Mark On Wed, Jul 20, 2016 at 10:11:11AM +0200, Heiko Stuebner wrote: > Am Mittwoch, 20. Juli 2016, 00:18:40 schrieb Heiko Stübner: > > Am Dienstag, 19. Juli 2016, 12:29:14 schrieb Brian Norris: > > > On Tue, Jul 19, 2016 at 12:27:54PM -0700, Brian Norris wrote: > > > > On Tue, Jul 19, 2016 at

Re: [PATCH] arm64: dts: rockchip: add spiX aliases for rk3399

+ Mark On Wed, Jul 20, 2016 at 10:11:11AM +0200, Heiko Stuebner wrote: > Am Mittwoch, 20. Juli 2016, 00:18:40 schrieb Heiko Stübner: > > Am Dienstag, 19. Juli 2016, 12:29:14 schrieb Brian Norris: > > > On Tue, Jul 19, 2016 at 12:27:54PM -0700, Brian Norris wrote: > > > > On Tue, Jul 19, 2016 at

Re: [PATCH] checkpatch: if no filenames then read stdin

On Fri, 2016-07-29 at 18:27 -0400, Allen Hubbe wrote: > If no filenames are given, then read the patch from stdin. Yes, that should work. Thanks Allen. Acked-by: Joe Perches Got anymore? > Signed-off-by: Allen Hubbe > --- >  scripts/checkpatch.pl | 4

Re: [PATCH] checkpatch: if no filenames then read stdin

On Fri, 2016-07-29 at 18:27 -0400, Allen Hubbe wrote: > If no filenames are given, then read the patch from stdin. Yes, that should work. Thanks Allen. Acked-by: Joe Perches Got anymore? > Signed-off-by: Allen Hubbe > --- >  scripts/checkpatch.pl | 4 ++-- >  1 file changed, 2 insertions(+),

Re: [PATCH v3 1/4] iio: adc: rockchip_saradc: reset saradc controller before programming it

On 2016年07月27日 22:47, Peter Meerwald-Stadler wrote: SARADC controller needs to be reset before programming it, otherwise it will not function properly. nitpicking on wording below Signed-off-by: Caesar Wang Cc: Jonathan Cameron Cc: Heiko Stuebner

Re: [PATCH v3 1/4] iio: adc: rockchip_saradc: reset saradc controller before programming it

On 2016年07月27日 22:47, Peter Meerwald-Stadler wrote: SARADC controller needs to be reset before programming it, otherwise it will not function properly. nitpicking on wording below Signed-off-by: Caesar Wang Cc: Jonathan Cameron Cc: Heiko Stuebner Cc: Rob Herring Cc:

Re: [PATCH 1/1] irqdomain: Export __irq_domain_alloc_irqs() and irq_domain_free_irqs()

On 27.07.2016 14:22, Christoph Hellwig wrote: > Hi Alex, > > just submit your PV irq chip for the kernel. It's so small that there > propbably is not need to even make it modular. Hello, Christoph, Thanks a lot for your reply! I'll try to do that and come up with a patch. Best regards,

Re: [PATCH 1/1] irqdomain: Export __irq_domain_alloc_irqs() and irq_domain_free_irqs()

On 27.07.2016 14:22, Christoph Hellwig wrote: > Hi Alex, > > just submit your PV irq chip for the kernel. It's so small that there > propbably is not need to even make it modular. Hello, Christoph, Thanks a lot for your reply! I'll try to do that and come up with a patch. Best regards,

Re: [PATCH v3 1/4] iio: adc: rockchip_saradc: reset saradc controller before programming it

On 2016年07月30日 05:28, Rob Herring wrote: On Wed, Jul 27, 2016 at 10:24:04PM +0800, Caesar Wang wrote: SARADC controller needs to be reset before programming it, otherwise it will not function properly. Signed-off-by: Caesar Wang Cc: Jonathan Cameron

Re: [PATCH v3 1/4] iio: adc: rockchip_saradc: reset saradc controller before programming it

On 2016年07月30日 05:28, Rob Herring wrote: On Wed, Jul 27, 2016 at 10:24:04PM +0800, Caesar Wang wrote: SARADC controller needs to be reset before programming it, otherwise it will not function properly. Signed-off-by: Caesar Wang Cc: Jonathan Cameron Cc: Heiko Stuebner Cc: Rob Herring Cc:

Re: [PATCH v3 1/4] iio: adc: rockchip_saradc: reset saradc controller before programming it

On 2016年07月30日 05:28, Rob Herring wrote: On Wed, Jul 27, 2016 at 10:24:04PM +0800, Caesar Wang wrote: SARADC controller needs to be reset before programming it, otherwise it will not function properly. Signed-off-by: Caesar Wang Cc: Jonathan Cameron

Re: [PATCH v3 1/4] iio: adc: rockchip_saradc: reset saradc controller before programming it

On 2016年07月30日 05:28, Rob Herring wrote: On Wed, Jul 27, 2016 at 10:24:04PM +0800, Caesar Wang wrote: SARADC controller needs to be reset before programming it, otherwise it will not function properly. Signed-off-by: Caesar Wang Cc: Jonathan Cameron Cc: Heiko Stuebner Cc: Rob Herring Cc:

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

On Fri, 2016-07-29 at 18:27 -0400, Allen Hubbe wrote: > Perl warns: > > Unescaped left brace in regex is deprecated, passed through in regex > > This is explained under "Quantifiers" in perl doc: > http://perldoc.perl.org/perlre.html#Quantifiers Hey Allen. I'm at 5.22 and don't see a warning.

Re: [PATCH] checkpatch: fix perl warning about unescaped brace

On Fri, 2016-07-29 at 18:27 -0400, Allen Hubbe wrote: > Perl warns: > > Unescaped left brace in regex is deprecated, passed through in regex > > This is explained under "Quantifiers" in perl doc: > http://perldoc.perl.org/perlre.html#Quantifiers Hey Allen. I'm at 5.22 and don't see a warning.

Re: [PATCH] fs: wipe off the compiler warn

On Fri, 29 Jul 2016 22:46:39 +0800 zhongjiang wrote: > From: zhong jiang > > when compile the kenrel code, I happens to the following warn. > fs/reiserfs/ibalance.c:1156:2: warning: ___new_insert_key___ may be used > uninitialized in this function.

Re: [PATCH] fs: wipe off the compiler warn

On Fri, 29 Jul 2016 22:46:39 +0800 zhongjiang wrote: > From: zhong jiang > > when compile the kenrel code, I happens to the following warn. > fs/reiserfs/ibalance.c:1156:2: warning: ___new_insert_key___ may be used > uninitialized in this function. > memcpy(new_insert_key_addr, _insert_key,

really and truly

Hello, I wanted to share with you something important , I guess I really and truly am in love this time! Take a look at some pics of us Warmest, sleepylight

really and truly

Hello, I wanted to share with you something important , I guess I really and truly am in love this time! Take a look at some pics of us Warmest, sleepylight

Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues

On Thu, 21 Jul 2016 16:21:42 -0500 Josh Poimboeuf wrote: > When function graph tracing is enabled for a function, its return > address on the stack is replaced with the address of an ftrace handler > (return_to_handler). When dumping the stack of a task with graph > tracing

Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues

On Thu, 21 Jul 2016 16:21:42 -0500 Josh Poimboeuf wrote: > When function graph tracing is enabled for a function, its return > address on the stack is replaced with the address of an ftrace handler > (return_to_handler). When dumping the stack of a task with graph > tracing enabled, there are

Re: Build failure in linux mainline when building arcv2 images

On 07/29/2016 02:48 PM, Guenter Roeck wrote: Yeah there's a 4.8.5 based one (referred to as GNU 2016.03) - will prebuilt toolchain suffice or would you prefer building on your own. Prebuilt could be found below.

Re: Build failure in linux mainline when building arcv2 images

On 07/29/2016 02:48 PM, Guenter Roeck wrote: Yeah there's a 4.8.5 based one (referred to as GNU 2016.03) - will prebuilt toolchain suffice or would you prefer building on your own. Prebuilt could be found below.

[PATCH V2] clk: bcm: Add driver for Northstar ILP clock

From: Rafał Miłecki This clock is present on cheaper Northstar devices like BCM53573 or BCM47189 using Corex-A7. This driver uses PMU (Power Management Unit) to calculate clock rate and allows using it in a generic (clk_*) way. Signed-off-by: Rafał Miłecki

[PATCH V2] clk: bcm: Add driver for Northstar ILP clock

From: Rafał Miłecki This clock is present on cheaper Northstar devices like BCM53573 or BCM47189 using Corex-A7. This driver uses PMU (Power Management Unit) to calculate clock rate and allows using it in a generic (clk_*) way. Signed-off-by: Rafał Miłecki --- V2: Rebase on top of clk-next

Re: [PATCH v3 2/2] pci/aer: interrupt fixup in the quirk

On Tue, Jun 14, 2016 at 04:24:05PM +0800, Po Liu wrote: > On some platforms, root port doesn't support MSI/MSI-X/INTx in RC mode. > When chip support the aer interrupt with none MSI/MSI-X/INTx mode, > maybe there is interrupt line for aer pme etc. Search the interrupt > number in the fdt file.

Re: [PATCH v3 2/2] pci/aer: interrupt fixup in the quirk

On Tue, Jun 14, 2016 at 04:24:05PM +0800, Po Liu wrote: > On some platforms, root port doesn't support MSI/MSI-X/INTx in RC mode. > When chip support the aer interrupt with none MSI/MSI-X/INTx mode, > maybe there is interrupt line for aer pme etc. Search the interrupt > number in the fdt file.

  1   2   3   4   5   6   7   8   9   >