[GIT PULL] kbuild fix for v4.10-rc3

Hi Linus, The asm-prototypes.h file added in the last merge window results in invalid code with CONFIG_KMEMCHECK=y. The net result is that genksyms segfaults. This pull request fixes the header, the genksyms fix is in my kbuild branch for 4.11. Thanks, Michal The following changes since commit

[GIT PULL] kbuild fix for v4.10-rc3

Hi Linus, The asm-prototypes.h file added in the last merge window results in invalid code with CONFIG_KMEMCHECK=y. The net result is that genksyms segfaults. This pull request fixes the header, the genksyms fix is in my kbuild branch for 4.11. Thanks, Michal The following changes since commit

Re: [PATCH v4 07/15] mtd: nand: move Samsung specific init/detection logic in nand_samsung.c

On Sat, 7 Jan 2017 00:53:24 +0100 Marek Vasut wrote: > On 01/04/2017 06:08 PM, Boris Brezillon wrote: > > On Wed, 4 Jan 2017 16:14:07 +0100 > > Marek Vasut wrote: > > > >> On 01/03/2017 02:01 PM, Boris Brezillon wrote: > >>> Move Samsung

Re: [PATCH v4 07/15] mtd: nand: move Samsung specific init/detection logic in nand_samsung.c

On Sat, 7 Jan 2017 00:53:24 +0100 Marek Vasut wrote: > On 01/04/2017 06:08 PM, Boris Brezillon wrote: > > On Wed, 4 Jan 2017 16:14:07 +0100 > > Marek Vasut wrote: > > > >> On 01/03/2017 02:01 PM, Boris Brezillon wrote: > >>> Move Samsung specific initialization and detection logic into >

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

* Andy Lutomirski wrote: > > When I looked at the fixmap, you had to define the space you need ahead of > > time and I am not sure there was enough space as you said. > > Can you try it and see if anything goes wrong? Even if something does go > wrong, > I think we should

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

* Andy Lutomirski wrote: > > When I looked at the fixmap, you had to define the space you need ahead of > > time and I am not sure there was enough space as you said. > > Can you try it and see if anything goes wrong? Even if something does go > wrong, > I think we should fix *that* rather

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

* Andy Lutomirski wrote: > > I looked back at the fixmap, and I can see a way it could be done (using > > NR_CPUS) like the other fixmap ranges. It would limit the number of cpus to > > 512 (there is 2M memory left on fixmap on the default configuration). > > That's > > if

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

* Andy Lutomirski wrote: > > I looked back at the fixmap, and I can see a way it could be done (using > > NR_CPUS) like the other fixmap ranges. It would limit the number of cpus to > > 512 (there is 2M memory left on fixmap on the default configuration). > > That's > > if we never add any

Re: [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions

On Sat, Jan 07, 2017 at 04:48:01PM +1300, Derek Robson wrote: > Two files change in style fix, changes are octal file permissions. > > Derek Robson (2): > Staging: unisys: visorbus: style fix, using octal file permissions > Staging: unisys: visorbus: style fix, using octal file permissions

Re: [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions

On Sat, Jan 07, 2017 at 04:48:01PM +1300, Derek Robson wrote: > Two files change in style fix, changes are octal file permissions. > > Derek Robson (2): > Staging: unisys: visorbus: style fix, using octal file permissions > Staging: unisys: visorbus: style fix, using octal file permissions

Re: [PATCH v2] hv: retry infinitely on hypercall transient failures

On Sat, Jan 07, 2017 at 07:23:14AM +, Long Li wrote: > > -Original Message- > > From: Greg KH [mailto:g...@kroah.com] > > Sent: Wednesday, January 04, 2017 11:48 PM > > To: Long Li > > Cc: KY Srinivasan ; Haiyang Zhang > >

Re: [PATCH v2] hv: retry infinitely on hypercall transient failures

On Sat, Jan 07, 2017 at 07:23:14AM +, Long Li wrote: > > -Original Message- > > From: Greg KH [mailto:g...@kroah.com] > > Sent: Wednesday, January 04, 2017 11:48 PM > > To: Long Li > > Cc: KY Srinivasan ; Haiyang Zhang > > ; de...@linuxdriverproject.org; linux- > >

Re: [PATCH] Staging: speakup: styel fix, octal file permissions

On Sat, Jan 07, 2017 at 05:11:16PM +1300, Derek Robson wrote: > Changed file permission to octal style, > Found using checkpatch Typo in your subject line :( > > Signed-off-by: Derek Robson > --- > drivers/staging/speakup/kobjects.c | 54 >

Re: [PATCH] Staging: speakup: styel fix, octal file permissions

On Sat, Jan 07, 2017 at 05:11:16PM +1300, Derek Robson wrote: > Changed file permission to octal style, > Found using checkpatch Typo in your subject line :( > > Signed-off-by: Derek Robson > --- > drivers/staging/speakup/kobjects.c | 54 > +++--- > 1 file

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

* Thomas Garnier wrote: > > No, and I had the way this worked on 64-bit wrong. LTR requires an > > available TSS and changes it to busy. So here are my thoughts on how > > this should work: > > > > Let's get rid of any connection between this code and KASLR. Every > >

Re: [RFC] x86/mm/KASLR: Remap GDTs at fixed location

* Thomas Garnier wrote: > > No, and I had the way this worked on 64-bit wrong. LTR requires an > > available TSS and changes it to busy. So here are my thoughts on how > > this should work: > > > > Let's get rid of any connection between this code and KASLR. Every > > time KASLR makes

Re: [PATCH v1] mtd: spi nor: modify the boot and flash type of FMC

Hi Cyrille, Thanks for your relay, I will update this patch soon. On 2017/1/6 21:44, Cyrille Pitchen wrote: > Hi, > > Le 06/01/2017 à 10:12, linshunquan 00354166 a écrit : >> (1) The HiSilicon Flash Memory Controller(FMC) is a multi-functions >> device which supports SPI Nor flash controller,

Re: [PATCH v1] mtd: spi nor: modify the boot and flash type of FMC

Hi Cyrille, Thanks for your relay, I will update this patch soon. On 2017/1/6 21:44, Cyrille Pitchen wrote: > Hi, > > Le 06/01/2017 à 10:12, linshunquan 00354166 a écrit : >> (1) The HiSilicon Flash Memory Controller(FMC) is a multi-functions >> device which supports SPI Nor flash controller,

Re: [PATCH 1/5] ARM: dts: qcom: apq8064: Add missing scm clock

On Fri 06 Jan 19:01 PST 2017, Andy Gross wrote: > On Fri, Jan 06, 2017 at 05:10:44PM -0800, John Stultz wrote: > > On Wed, Dec 21, 2016 at 3:49 AM, Bjorn Andersson > > wrote: > > > As per the device tree binding the apq8064 scm node requires the core > > > clock to be

Re: [PATCH 1/5] ARM: dts: qcom: apq8064: Add missing scm clock

On Fri 06 Jan 19:01 PST 2017, Andy Gross wrote: > On Fri, Jan 06, 2017 at 05:10:44PM -0800, John Stultz wrote: > > On Wed, Dec 21, 2016 at 3:49 AM, Bjorn Andersson > > wrote: > > > As per the device tree binding the apq8064 scm node requires the core > > > clock to be specified, so add this. > >

RE: [PATCH v2] hv: retry infinitely on hypercall transient failures

> -Original Message- > From: Greg KH [mailto:g...@kroah.com] > Sent: Wednesday, January 04, 2017 11:48 PM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; de...@linuxdriverproject.org; linux- > ker...@vger.kernel.org >

RE: [PATCH v2] hv: retry infinitely on hypercall transient failures

> -Original Message- > From: Greg KH [mailto:g...@kroah.com] > Sent: Wednesday, January 04, 2017 11:48 PM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; de...@linuxdriverproject.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v2] hv: retry infinitely on hypercall

RE: [PATCH] hv: use substraction to update ring buffer index

> -Original Message- > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > Sent: Thursday, January 05, 2017 3:40 AM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; de...@linuxdriverproject.org; linux- >

RE: [PATCH] hv: use substraction to update ring buffer index

> -Original Message- > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > Sent: Thursday, January 05, 2017 3:40 AM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; de...@linuxdriverproject.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH] hv: use substraction to

[PATCH v5 1/3] dmaengine: xilinx_dma: Check for channel idle state before submitting dma descriptor

Add channel idle state to ensure that dma descriptor is not submitted when VDMA engine is in progress. Reviewed-by: Jose Abreu Signed-off-by: Kedareswara rao Appana --- Changes for v5: ---> None. Changes for v4: ---> None. Changes for v3: ---> None.

[PATCH v5 1/3] dmaengine: xilinx_dma: Check for channel idle state before submitting dma descriptor

Add channel idle state to ensure that dma descriptor is not submitted when VDMA engine is in progress. Reviewed-by: Jose Abreu Signed-off-by: Kedareswara rao Appana --- Changes for v5: ---> None. Changes for v4: ---> None. Changes for v3: ---> None. Changes for v2: ---> Add idle check in the

[PATCH v5 0/3] dmaengine: xilinx_dma: Bug fixes

This patch series fixes below bugs in DMA and VDMA IP's ---> Do not start VDMA until frame buffer is processed by the h/w Fix ---> bug in Multi frame sotres handling in VDMA Fix issues w.r.to multi ---> frame descriptors submit with AXI DMA S2MM(recv) Side. Kedareswara rao Appana (3):

[PATCH v5 0/3] dmaengine: xilinx_dma: Bug fixes

This patch series fixes below bugs in DMA and VDMA IP's ---> Do not start VDMA until frame buffer is processed by the h/w Fix ---> bug in Multi frame sotres handling in VDMA Fix issues w.r.to multi ---> frame descriptors submit with AXI DMA S2MM(recv) Side. Kedareswara rao Appana (3):

[PATCH v5 3/3] dmaengine: xilinx_dma: Fix race condition in the driver for multiple descriptor scenario

When driver is handling AXI DMA SoftIP When user submits multiple descriptors back to back on the S2MM(recv) side with the current driver flow the last buffer descriptor next bd points to a invalid location resulting the invalid data or errors in the DMA engine. This patch fixes this issue by

[PATCH v5 2/3] dmaeninge: xilinx_dma: Fix bug in multiple frame stores scenario in vdma

When VDMA is configured for more than one frame in the h/w for example h/w is configured for n number of frames and user Submits n number of frames and triggered the DMA using issue_pending API. In the current driver flow we are submitting one frame at a time but we should submit all the n number

[PATCH v5 3/3] dmaengine: xilinx_dma: Fix race condition in the driver for multiple descriptor scenario

When driver is handling AXI DMA SoftIP When user submits multiple descriptors back to back on the S2MM(recv) side with the current driver flow the last buffer descriptor next bd points to a invalid location resulting the invalid data or errors in the DMA engine. This patch fixes this issue by

[PATCH v5 2/3] dmaeninge: xilinx_dma: Fix bug in multiple frame stores scenario in vdma

When VDMA is configured for more than one frame in the h/w for example h/w is configured for n number of frames and user Submits n number of frames and triggered the DMA using issue_pending API. In the current driver flow we are submitting one frame at a time but we should submit all the n number

Re: [GIT PULL] namespace related fixes for 4.10-rc3

On Sat, Jan 07, 2017 at 06:29:52AM +, Al Viro wrote: > On Sat, Jan 07, 2017 at 06:30:05PM +1300, Eric W. Biederman wrote: > > > Eric W. Biederman (3): > > mnt: Protect the mountpoint hashtable with mount_lock > ACK > > > mnt: Tuck mounts under others instead of creating

Re: [GIT PULL] namespace related fixes for 4.10-rc3

On Sat, Jan 07, 2017 at 06:29:52AM +, Al Viro wrote: > On Sat, Jan 07, 2017 at 06:30:05PM +1300, Eric W. Biederman wrote: > > > Eric W. Biederman (3): > > mnt: Protect the mountpoint hashtable with mount_lock > ACK > > > mnt: Tuck mounts under others instead of creating

Re: [GIT PULL] namespace related fixes for 4.10-rc3

On Sat, Jan 07, 2017 at 06:30:05PM +1300, Eric W. Biederman wrote: > Eric W. Biederman (3): > mnt: Protect the mountpoint hashtable with mount_lock ACK > mnt: Tuck mounts under others instead of creating shadow/side mounts. NAK; you have reintroduced put_mountpoint() outside of

Re: [GIT PULL] namespace related fixes for 4.10-rc3

On Sat, Jan 07, 2017 at 06:30:05PM +1300, Eric W. Biederman wrote: > Eric W. Biederman (3): > mnt: Protect the mountpoint hashtable with mount_lock ACK > mnt: Tuck mounts under others instead of creating shadow/side mounts. NAK; you have reintroduced put_mountpoint() outside of

Re: [V9fs-developer] 9pfs hangs since 4.7

On Fri, Jan 06, 2017 at 02:52:35PM +0100, Greg Kurz wrote: > Looking at the tag numbers, I think we're hitting the hardcoded limit of 128 > simultaneous requests in QEMU (which doesn't produce any error, new requests > are silently dropped). > > Tuomas, can you change MAX_REQ to some higher

Re: [V9fs-developer] 9pfs hangs since 4.7

On Fri, Jan 06, 2017 at 02:52:35PM +0100, Greg Kurz wrote: > Looking at the tag numbers, I think we're hitting the hardcoded limit of 128 > simultaneous requests in QEMU (which doesn't produce any error, new requests > are silently dropped). > > Tuomas, can you change MAX_REQ to some higher

[PATCH v1 3/3] thermal: zx2967: add thermal driver for ZTE's zx2967 family

This patch adds thermal driver for ZTE's zx2967 family. Signed-off-by: Baoyou Xie --- drivers/thermal/Kconfig | 6 + drivers/thermal/Makefile | 1 + drivers/thermal/zx2967_thermal.c | 241 +++ 3 files changed, 248

[PATCH v1 3/3] thermal: zx2967: add thermal driver for ZTE's zx2967 family

This patch adds thermal driver for ZTE's zx2967 family. Signed-off-by: Baoyou Xie --- drivers/thermal/Kconfig | 6 + drivers/thermal/Makefile | 1 + drivers/thermal/zx2967_thermal.c | 241 +++ 3 files changed, 248 insertions(+) create

[PATCH v1 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

Add the zx2967 thermal drivers as maintained by ARM ZTE architecture maintainers, as they're parts of the core IP. Signed-off-by: Baoyou Xie --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 64f04df..2593296 100644 ---

[PATCH v1 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

Add the zx2967 thermal drivers as maintained by ARM ZTE architecture maintainers, as they're parts of the core IP. Signed-off-by: Baoyou Xie --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 64f04df..2593296 100644 --- a/MAINTAINERS +++

[PATCH v1 1/3] dt: bindings: add thermal device driver for zx2967

This patch adds dt-binding documentation for zx2967 family thermal sensor. Signed-off-by: Baoyou Xie --- .../devicetree/bindings/thermal/zx2967-thermal.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644

[PATCH v1 1/3] dt: bindings: add thermal device driver for zx2967

This patch adds dt-binding documentation for zx2967 family thermal sensor. Signed-off-by: Baoyou Xie --- .../devicetree/bindings/thermal/zx2967-thermal.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644

[GIT PULL] namespace related fixes for 4.10-rc3

Linus, Please pull the for-linus branch from the git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus HEAD: cd293bfacd57928627ef7da6194e0cbe24db3291 sysctl: Drop reference added by grab_header in proc_sys_readdir This tree contains 5 fixes.

[GIT PULL] namespace related fixes for 4.10-rc3

Linus, Please pull the for-linus branch from the git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus HEAD: cd293bfacd57928627ef7da6194e0cbe24db3291 sysctl: Drop reference added by grab_header in proc_sys_readdir This tree contains 5 fixes.

[PATCH perf/core 4/4] perf-probe: Find probe events without target module

Find probe events without -m "module" option. If perf-probe failed to find given function in kernel image, it tries to find same symbol and module in kallsyms, and retry search in the found module. E.g. # perf probe -D i915_capabilities p:probe/i915_capabilities i915:i915_capabilities+0

[PATCH perf/core 4/4] perf-probe: Find probe events without target module

Find probe events without -m "module" option. If perf-probe failed to find given function in kernel image, it tries to find same symbol and module in kallsyms, and retry search in the found module. E.g. # perf probe -D i915_capabilities p:probe/i915_capabilities i915:i915_capabilities+0

[PATCH perf/core 3/4] perf-probe: Fix to probe on gcc generated functions in modules

Fix to probe on gcc generated functions on modules. Since probing on a module is based on its symbol name, it should be adjusted on actual symbols. E.g. without this fix, perf probe shows probe definition on non-exist symbol as below. $ perf probe -m build-x86_64/net/netfilter/nf_nat.ko -F

[PATCH perf/core 3/4] perf-probe: Fix to probe on gcc generated functions in modules

Fix to probe on gcc generated functions on modules. Since probing on a module is based on its symbol name, it should be adjusted on actual symbols. E.g. without this fix, perf probe shows probe definition on non-exist symbol as below. $ perf probe -m build-x86_64/net/netfilter/nf_nat.ko -F

[PATCH perf/core 2/4] perf-probe: Add error checks to offline probe post-processing

Add error check codes to post process and improve it for offline probe events as; - post process fails if no matched symbol found in map(-ENOENT) or strdup() failed(-ENOMEM). - Even if the symbol name is same, it updates symbol address and offset. Signed-off-by: Masami Hiramatsu

[PATCH perf/core 2/4] perf-probe: Add error checks to offline probe post-processing

Add error check codes to post process and improve it for offline probe events as; - post process fails if no matched symbol found in map(-ENOENT) or strdup() failed(-ENOMEM). - Even if the symbol name is same, it updates symbol address and offset. Signed-off-by: Masami Hiramatsu ---

[PATCH perf/core 1/4] perf-probe: Fix to show correct locations for events on modules

Fix to show correct locations for events on modules by relocating given address. Currently the relocation is done when we failed to find the address in debuginfo, but for modules it always makes a mistakes. E.g. without this fix, events on module seems wrong, but other cases (kernel and user

[PATCH perf/core 1/4] perf-probe: Fix to show correct locations for events on modules

Fix to show correct locations for events on modules by relocating given address. Currently the relocation is done when we failed to find the address in debuginfo, but for modules it always makes a mistakes. E.g. without this fix, events on module seems wrong, but other cases (kernel and user

[PATCH perf/core 0/4] perf-probe: Fix and improve module probe events

Hello, This series fixes some issues on offline/online module probe support and improve perf-probe to probe module without -m option (Thanks Arnaldo!). This includes below patches. - [1/4] Fix perf-probe --list to show correct probe location in module. - [2/4] Improve error checking

[PATCH perf/core 0/4] perf-probe: Fix and improve module probe events

Hello, This series fixes some issues on offline/online module probe support and improve perf-probe to probe module without -m option (Thanks Arnaldo!). This includes below patches. - [1/4] Fix perf-probe --list to show correct probe location in module. - [2/4] Improve error checking

RE: [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions

> -Original Message- > From: Derek Robson [mailto:robso...@gmail.com] > Sent: Friday, January 6, 2017 10:48 PM > To: Kershner, David A ; > gre...@linuxfoundation.org; Sell, Timothy C > Cc: *S-Par-Maintainer ; >

RE: [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions

> -Original Message- > From: Derek Robson [mailto:robso...@gmail.com] > Sent: Friday, January 6, 2017 10:48 PM > To: Kershner, David A ; > gre...@linuxfoundation.org; Sell, Timothy C > Cc: *S-Par-Maintainer ; > de...@driverdev.osuosl.org; linux-kernel@vger.kernel.org; Derek Robson > >

Re: [PATCH] ipc/sem.c: fix semop()/semop() locking failure

On Sun, 2016-12-18 at 19:45 -0800, Davidlohr Bueso wrote: > Nit: the title is a bit unclear. How about: > > ipc/sem.: fix semop() locking imbalance > > Otherwise, Ack. (notices patchlet _not_ flying upstream... s/failure/imbalance?)

Re: [PATCH] ipc/sem.c: fix semop()/semop() locking failure

On Sun, 2016-12-18 at 19:45 -0800, Davidlohr Bueso wrote: > Nit: the title is a bit unclear. How about: > > ipc/sem.: fix semop() locking imbalance > > Otherwise, Ack. (notices patchlet _not_ flying upstream... s/failure/imbalance?)

[PATCH] Staging: speakup: styel fix, octal file permissions

Changed file permission to octal style, Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/speakup/kobjects.c | 54 +++--- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/drivers/staging/speakup/kobjects.c

[PATCH] Staging: speakup: styel fix, octal file permissions

Changed file permission to octal style, Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/speakup/kobjects.c | 54 +++--- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/drivers/staging/speakup/kobjects.c

Re: [PATCH v2] ARM: dts: qcom: apq8064: Add missing scm clock

On Thu, Dec 29, 2016 at 4:06 AM, Bjorn Andersson wrote: > As per the device tree binding the apq8064 scm node requires the core > clock to be specified, so add this. > > Signed-off-by: Bjorn Andersson > --- > > Changes since v1: > - Changed

Re: [PATCH v2] ARM: dts: qcom: apq8064: Add missing scm clock

On Thu, Dec 29, 2016 at 4:06 AM, Bjorn Andersson wrote: > As per the device tree binding the apq8064 scm node requires the core > clock to be specified, so add this. > > Signed-off-by: Bjorn Andersson > --- > > Changes since v1: > - Changed clock to Daytona Fabric > >

Re: [PATCH net-next 1/4] siphash: add cryptographically secure PRF

Hi Jason, just a few comments: On Fri, Jan 06, 2017 at 09:10:52PM +0100, Jason A. Donenfeld wrote: > +#define SIPHASH_ALIGNMENT __alignof__(u64) > +typedef u64 siphash_key_t[2]; I was confused by all the functions passing siphash_key_t "by value" until I saw that it's actually typedefed to

Re: [PATCH net-next 1/4] siphash: add cryptographically secure PRF

Hi Jason, just a few comments: On Fri, Jan 06, 2017 at 09:10:52PM +0100, Jason A. Donenfeld wrote: > +#define SIPHASH_ALIGNMENT __alignof__(u64) > +typedef u64 siphash_key_t[2]; I was confused by all the functions passing siphash_key_t "by value" until I saw that it's actually typedefed to

Re: [PATCH v3 1/3] timekeeping: Add a fast and NMI safe boot clock

On Fri, Jan 6, 2017 at 6:39 PM, Joel Fernandes wrote: > Hi John, > > On Fri, Jan 6, 2017 at 4:48 PM, John Stultz wrote: >> On Thu, Nov 24, 2016 at 12:20 PM, Joel Fernandes wrote: >>> This boot clock can be used as a tracing clock and

Re: [PATCH v3 1/3] timekeeping: Add a fast and NMI safe boot clock

On Fri, Jan 6, 2017 at 6:39 PM, Joel Fernandes wrote: > Hi John, > > On Fri, Jan 6, 2017 at 4:48 PM, John Stultz wrote: >> On Thu, Nov 24, 2016 at 12:20 PM, Joel Fernandes wrote: >>> This boot clock can be used as a tracing clock and will account for >>> suspend time. >>> >>> To keep it NMI

Re: [PATCH 2/3] Input: pwm-beeper - switch to using managed resources

On 01/06/2017 12:20 PM, Dmitry Torokhov wrote: e of managed resources (devm) simplifies error handling and teardown ^ Looks like the commit message got cut off. of the driver.

Re: [PATCH 2/3] Input: pwm-beeper - switch to using managed resources

On 01/06/2017 12:20 PM, Dmitry Torokhov wrote: e of managed resources (devm) simplifies error handling and teardown ^ Looks like the commit message got cut off. of the driver.

[PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions

Two files change in style fix, changes are octal file permissions. Derek Robson (2): Staging: unisys: visorbus: style fix, using octal file permissions Staging: unisys: visorbus: style fix, using octal file permissions drivers/staging/unisys/visorbus/visorbus_main.c | 6 +++---

[PATCH 2/2] Staging: unisys: visorbus: style fix, using octal file permissions

Changed file permissions to octal sytle. Found using checkpatch. Signed-off-by: Derek Robson --- drivers/staging/unisys/visorbus/visorchipset.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/unisys/visorbus/visorchipset.c

[PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions

Two files change in style fix, changes are octal file permissions. Derek Robson (2): Staging: unisys: visorbus: style fix, using octal file permissions Staging: unisys: visorbus: style fix, using octal file permissions drivers/staging/unisys/visorbus/visorbus_main.c | 6 +++---

[PATCH 2/2] Staging: unisys: visorbus: style fix, using octal file permissions

Changed file permissions to octal sytle. Found using checkpatch. Signed-off-by: Derek Robson --- drivers/staging/unisys/visorbus/visorchipset.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/unisys/visorbus/visorchipset.c

[PATCH 1/2] Staging: unisys: visorbus: style fix, using octal file permissions

Changed file permissions to octal style. Found with checkpatch Signed-off-by: Derek Robson --- drivers/staging/unisys/visorbus/visorbus_main.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorbus_main.c

[PATCH 1/2] Staging: unisys: visorbus: style fix, using octal file permissions

Changed file permissions to octal style. Found with checkpatch Signed-off-by: Derek Robson --- drivers/staging/unisys/visorbus/visorbus_main.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorbus_main.c

Re: [PATCH] net: use kvmalloc rather than open coded variant

Hi Michal, [auto build test ERROR on net-next/master] [also build test ERROR on v4.10-rc2 next-20170106] [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/Michal-Hocko/net-use-kvmalloc-rather-than

Re: [PATCH] net: use kvmalloc rather than open coded variant

Hi Michal, [auto build test ERROR on net-next/master] [also build test ERROR on v4.10-rc2 next-20170106] [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/Michal-Hocko/net-use-kvmalloc-rather-than

Re: [PATCH] net: use kvmalloc rather than open coded variant

Hi Michal, [auto build test ERROR on net-next/master] [also build test ERROR on v4.10-rc2 next-20170106] [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/Michal-Hocko/net-use-kvmalloc-rather-than

Re: [PATCH] net: use kvmalloc rather than open coded variant

Hi Michal, [auto build test ERROR on net-next/master] [also build test ERROR on v4.10-rc2 next-20170106] [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/Michal-Hocko/net-use-kvmalloc-rather-than

Re: [PATCH] usb: dwc2: use u32 for DT binding parameters

On 1/6/2017 1:52 PM, John Stultz wrote: > On Fri, Jan 6, 2017 at 4:45 AM, Leo Yan wrote: >> Commit 05ee799f2021 ("usb: dwc2: Move gadget settings into core_params") >> changes to type u16 for DT binding "g-rx-fifo-size" and >> "g-np-tx-fifo-size" but use type u32 for

Re: [PATCH] usb: dwc2: use u32 for DT binding parameters

On 1/6/2017 1:52 PM, John Stultz wrote: > On Fri, Jan 6, 2017 at 4:45 AM, Leo Yan wrote: >> Commit 05ee799f2021 ("usb: dwc2: Move gadget settings into core_params") >> changes to type u16 for DT binding "g-rx-fifo-size" and >> "g-np-tx-fifo-size" but use type u32 for "g-tx-fifo-size". Finally the

[PATCH] usb: dwc2: use u32 for DT binding parameters

From: Leo Yan Commit 05ee799f2021 ("usb: dwc2: Move gadget settings into core_params") changes to type u16 for DT binding "g-rx-fifo-size" and "g-np-tx-fifo-size" but use type u32 for "g-tx-fifo-size". Finally the the first two parameters cannot be passed successfully with

[PATCH] usb: dwc2: use u32 for DT binding parameters

From: Leo Yan Commit 05ee799f2021 ("usb: dwc2: Move gadget settings into core_params") changes to type u16 for DT binding "g-rx-fifo-size" and "g-np-tx-fifo-size" but use type u32 for "g-tx-fifo-size". Finally the the first two parameters cannot be passed successfully with wrong data format.

[PATCH] treewide: fix semicolon.cocci warnings

net/netfilter/x_tables.c:716:59-60: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Signed-off-by: Fengguang Wu --- x_tables.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---

[PATCH] treewide: fix semicolon.cocci warnings

net/netfilter/x_tables.c:716:59-60: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Signed-off-by: Fengguang Wu --- x_tables.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/net/netfilter/x_tables.c +++

[PATCH v3] ext4: increase the protection of nlink dec and ext4 inode destroy

Because of the disk and hardware issue, the ext4 filesystem have many errors, the inode->i_nlink of ext4 becomes zero abnormally but the dentry is still positive, it will cause memory corruption after the following process: 1) Due to the inode->i_nlink is 0, this inode will be added into the

[PATCH v3] ext4: increase the protection of nlink dec and ext4 inode destroy

Because of the disk and hardware issue, the ext4 filesystem have many errors, the inode->i_nlink of ext4 becomes zero abnormally but the dentry is still positive, it will cause memory corruption after the following process: 1) Due to the inode->i_nlink is 0, this inode will be added into the

Re: [net-next][PATCH] RDS: validate the requested traces user input against max supported

From: Santosh Shilimkar Date: Fri, 6 Jan 2017 10:44:15 -0800 > Larger than supported value can lead to array read/write overflow. > > Reported-by: Colin Ian King > Signed-off-by: Santosh Shilimkar Applied,

Re: [net-next][PATCH] RDS: validate the requested traces user input against max supported

From: Santosh Shilimkar Date: Fri, 6 Jan 2017 10:44:15 -0800 > Larger than supported value can lead to array read/write overflow. > > Reported-by: Colin Ian King > Signed-off-by: Santosh Shilimkar Applied, thanks.

Re: [PATCH net-next] bridge: multicast to unicast

On Mon, 2 Jan 2017 20:32:14 +0100 Linus Lüssing wrote: > This feature is intended for interface types which have a more reliable > and/or efficient way to deliver unicast packets than broadcast ones > (e.g. wifi). Why is this not done in MAC80211 rather than bridge?

Re: [PATCH net-next] bridge: multicast to unicast

On Mon, 2 Jan 2017 20:32:14 +0100 Linus Lüssing wrote: > This feature is intended for interface types which have a more reliable > and/or efficient way to deliver unicast packets than broadcast ones > (e.g. wifi). Why is this not done in MAC80211 rather than bridge?

[PATCH] Staging: media: lirc: style fix, using octal file permissions

Change file permissions to octal style. Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/media/lirc/lirc_imon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/media/lirc/lirc_imon.c

[PATCH] Staging: media: lirc: style fix, using octal file permissions

Change file permissions to octal style. Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/media/lirc/lirc_imon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/media/lirc/lirc_imon.c b/drivers/staging/media/lirc/lirc_imon.c index

Re: [PATCH 1/5] ARM: dts: qcom: apq8064: Add missing scm clock

On Fri, Jan 06, 2017 at 05:10:44PM -0800, John Stultz wrote: > On Wed, Dec 21, 2016 at 3:49 AM, Bjorn Andersson > wrote: > > As per the device tree binding the apq8064 scm node requires the core > > clock to be specified, so add this. > > > > Cc: John Stultz

Re: [PATCH 1/5] ARM: dts: qcom: apq8064: Add missing scm clock

On Fri, Jan 06, 2017 at 05:10:44PM -0800, John Stultz wrote: > On Wed, Dec 21, 2016 at 3:49 AM, Bjorn Andersson > wrote: > > As per the device tree binding the apq8064 scm node requires the core > > clock to be specified, so add this. > > > > Cc: John Stultz > > Signed-off-by: Bjorn Andersson >

Re: [PATCH net-next 0/2] afs: Implement bulk read

git/log/?h=rxrpc-rewrite > > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20170106 Pulled, thanks David.

Re: [PATCH net-next 0/2] afs: Implement bulk read

> > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20170106 Pulled, thanks David.

Re: [PATCH v3 1/3] timekeeping: Add a fast and NMI safe boot clock

Hi John, On Fri, Jan 6, 2017 at 4:48 PM, John Stultz wrote: > On Thu, Nov 24, 2016 at 12:20 PM, Joel Fernandes wrote: >> This boot clock can be used as a tracing clock and will account for >> suspend time. >> >> To keep it NMI safe since we're

Re: [PATCH v3 1/3] timekeeping: Add a fast and NMI safe boot clock

Hi John, On Fri, Jan 6, 2017 at 4:48 PM, John Stultz wrote: > On Thu, Nov 24, 2016 at 12:20 PM, Joel Fernandes wrote: >> This boot clock can be used as a tracing clock and will account for >> suspend time. >> >> To keep it NMI safe since we're accessing from tracing, we're not using a >>

  1   2   3   4   5   6   7   8   9   10   >