Re: [PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

Hi! On 01/17/2017 03:39 PM, Joseph Qi wrote: On 17/1/17 14:30, Eric Ren wrote: We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code

Re: [PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

Hi! On 01/17/2017 03:39 PM, Joseph Qi wrote: On 17/1/17 14:30, Eric Ren wrote: We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code

Re: [PATCH 7/8] Revert "ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp"

On Mon 16-01-17 22:01:18, Theodore Ts'o wrote: > On Fri, Jan 06, 2017 at 03:11:06PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > This reverts commit c45653c341f5c8a0ce19c8f0ad4678640849cb86 because > > sb_getblk_gfp is not really needed as > > sb_getblk > >

Re: [PATCH v3 2/2] tpm: enhance TPM 2.0 PCR extend to support multiple banks

On 01/12/2017 11:50 PM, Jarkko Sakkinen wrote: On Thu, Jan 12, 2017 at 11:58:10AM -0500, Nayna Jain wrote: The current TPM 2.0 device driver extends only the SHA1 PCR bank but the TCG Specification[1] recommends extending all active PCR banks, to prevent malicious users from setting unused

Re: [PATCH 7/8] Revert "ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp"

On Mon 16-01-17 22:01:18, Theodore Ts'o wrote: > On Fri, Jan 06, 2017 at 03:11:06PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > This reverts commit c45653c341f5c8a0ce19c8f0ad4678640849cb86 because > > sb_getblk_gfp is not really needed as > > sb_getblk > > __getblk_gfp > >

Re: [PATCH v3 2/2] tpm: enhance TPM 2.0 PCR extend to support multiple banks

On 01/12/2017 11:50 PM, Jarkko Sakkinen wrote: On Thu, Jan 12, 2017 at 11:58:10AM -0500, Nayna Jain wrote: The current TPM 2.0 device driver extends only the SHA1 PCR bank but the TCG Specification[1] recommends extending all active PCR banks, to prevent malicious users from setting unused

Re: [PATCH RESEND] coredump: Ensure proper size of sparse core files

On Mon, Jan 16, 2017 at 10:42:43PM -0500, David Miller wrote: > The lseek() done by dump_skip() should extend the file properly. lseek never extends a file. It just moves the current file position. So if you do not have a write after the lseek it does nothing.

Re: [PATCH RESEND] coredump: Ensure proper size of sparse core files

On Mon, Jan 16, 2017 at 10:42:43PM -0500, David Miller wrote: > The lseek() done by dump_skip() should extend the file properly. lseek never extends a file. It just moves the current file position. So if you do not have a write after the lseek it does nothing.

Re: [PATCH v2 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts

Jan Kiszka writes: > When using the a device with edge-triggered interrupts, such as MSIs, > the interrupt handler has to ensure that there is a point in time during > its execution where all interrupts sources are silent so that a new > event can trigger a new interrupt

Re: [PATCH v2 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts

Jan Kiszka writes: > When using the a device with edge-triggered interrupts, such as MSIs, > the interrupt handler has to ensure that there is a point in time during > its execution where all interrupts sources are silent so that a new > event can trigger a new interrupt again. > > This is

Re: [PATCH v1 00/54] block: support multipage bvec

On Tue, Jan 17, 2017 at 10:40:36AM +0800, Ming Lei wrote: > IMO, the only one left is raid(1/5/10) which can be dealt with by the > "NO_MP" flag. No, they can't in the long run. They need to handle the bvecs just like everyone else.

Re: [PATCH v1 00/54] block: support multipage bvec

On Tue, Jan 17, 2017 at 10:40:36AM +0800, Ming Lei wrote: > IMO, the only one left is raid(1/5/10) which can be dealt with by the > "NO_MP" flag. No, they can't in the long run. They need to handle the bvecs just like everyone else.

Re: [PATCH 1/6] mm: introduce kv[mz]alloc helpers

On Mon 16-01-17 13:57:43, John Hubbard wrote: > > > On 01/16/2017 01:48 PM, Michal Hocko wrote: > > On Mon 16-01-17 13:15:08, John Hubbard wrote: > > > > > > > > > On 01/16/2017 11:40 AM, Michal Hocko wrote: > > > > On Mon 16-01-17 11:09:37, John Hubbard wrote: > > > > > > > > > > > > > > >

Re: [PATCH 1/6] mm: introduce kv[mz]alloc helpers

On Mon 16-01-17 13:57:43, John Hubbard wrote: > > > On 01/16/2017 01:48 PM, Michal Hocko wrote: > > On Mon 16-01-17 13:15:08, John Hubbard wrote: > > > > > > > > > On 01/16/2017 11:40 AM, Michal Hocko wrote: > > > > On Mon 16-01-17 11:09:37, John Hubbard wrote: > > > > > > > > > > > > > > >

Re: [PATCH v3 2/4] dt-bindings: Add TI SCI PM Domains

On 17/01/17 00:12, Dave Gerlach wrote: On 01/13/2017 08:40 PM, Rob Herring wrote: On Fri, Jan 13, 2017 at 2:28 PM, Dave Gerlach wrote: On 01/13/2017 01:25 PM, Rob Herring wrote: On Thu, Jan 12, 2017 at 9:27 AM, Dave Gerlach wrote: Rob, On 01/11/2017

Re: [PATCH v3 2/4] dt-bindings: Add TI SCI PM Domains

On 17/01/17 00:12, Dave Gerlach wrote: On 01/13/2017 08:40 PM, Rob Herring wrote: On Fri, Jan 13, 2017 at 2:28 PM, Dave Gerlach wrote: On 01/13/2017 01:25 PM, Rob Herring wrote: On Thu, Jan 12, 2017 at 9:27 AM, Dave Gerlach wrote: Rob, On 01/11/2017 03:34 PM, Rob Herring wrote: On

Re: [PATCH v3 3/3] reset: zx2967: add reset controller driver for ZTE's zx2967 family

On Tue, Jan 17, 2017 at 11:22:57AM +0800, Baoyou Xie wrote: > This patch adds reset controller driver for ZTE's zx2967 family. > > Signed-off-by: Baoyou Xie Reviewed-by: Shawn Guo

Re: [PATCH v3 3/3] reset: zx2967: add reset controller driver for ZTE's zx2967 family

On Tue, Jan 17, 2017 at 11:22:57AM +0800, Baoyou Xie wrote: > This patch adds reset controller driver for ZTE's zx2967 family. > > Signed-off-by: Baoyou Xie Reviewed-by: Shawn Guo

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 08:14:56AM +0100, Peter Zijlstra wrote: > On Tue, Jan 17, 2017 at 11:05:42AM +0900, Byungchul Park wrote: > > On Mon, Jan 16, 2017 at 04:10:01PM +0100, Peter Zijlstra wrote: > > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > > > @@ -155,6 +164,9 @@

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 08:14:56AM +0100, Peter Zijlstra wrote: > On Tue, Jan 17, 2017 at 11:05:42AM +0900, Byungchul Park wrote: > > On Mon, Jan 16, 2017 at 04:10:01PM +0100, Peter Zijlstra wrote: > > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > > > @@ -155,6 +164,9 @@

Re: [PATCH v3 2/2] ocfs2: fix deadlock issue when taking inode lock at vfs entry points

On 17/1/17 14:30, Eric Ren wrote: Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") results in a deadlock, as the author "Tariq Saeed" realized shortly after the patch was merged. The discussion happened here

Re: [PATCH] fbdev: ssd1307fb: allow reset-gpios is missing

On Mon, Jan 16, 2017 at 05:50:21PM +0800, Icenowy Zheng wrote: > > 2017年1月16日 16:02于 Maxime Ripard 写道： > > > > On Sun, Jan 15, 2017 at 07:21:46PM +0800, Icenowy Zheng wrote: > > > Currently some SSD1306 OLED modules are sold without a reset pin (only > > > VCC,

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 02:24:08PM +0800, Boqun Feng wrote: > On Tue, Jan 17, 2017 at 11:33:41AM +0900, Byungchul Park wrote: > > On Mon, Jan 16, 2017 at 04:13:19PM +0100, Peter Zijlstra wrote: > > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > > + /* > > > > +

Re: [PATCH v3 2/2] ocfs2: fix deadlock issue when taking inode lock at vfs entry points

On 17/1/17 14:30, Eric Ren wrote: Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") results in a deadlock, as the author "Tariq Saeed" realized shortly after the patch was merged. The discussion happened here

Re: [PATCH] fbdev: ssd1307fb: allow reset-gpios is missing

On Mon, Jan 16, 2017 at 05:50:21PM +0800, Icenowy Zheng wrote: > > 2017年1月16日 16:02于 Maxime Ripard 写道： > > > > On Sun, Jan 15, 2017 at 07:21:46PM +0800, Icenowy Zheng wrote: > > > Currently some SSD1306 OLED modules are sold without a reset pin (only > > > VCC, GND, SCK, SDA four pins). > > >

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 02:24:08PM +0800, Boqun Feng wrote: > On Tue, Jan 17, 2017 at 11:33:41AM +0900, Byungchul Park wrote: > > On Mon, Jan 16, 2017 at 04:13:19PM +0100, Peter Zijlstra wrote: > > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > > + /* > > > > +

Re: [PATCH] staging: lustre: headers: potential UAPI headers

On Mon, Jan 16, 2017 at 09:28:30PM +, James Simmons wrote: > > > On Mon, Dec 19, 2016 at 12:06:47PM -0500, James Simmons wrote: > > > Not for landing. This is the purposed UAPI headers > > > with the removal of unlikely and debugging macros. > > > This is just for feedback to see if this is

Re: [PATCH] staging: lustre: headers: potential UAPI headers

On Mon, Jan 16, 2017 at 09:28:30PM +, James Simmons wrote: > > > On Mon, Dec 19, 2016 at 12:06:47PM -0500, James Simmons wrote: > > > Not for landing. This is the purposed UAPI headers > > > with the removal of unlikely and debugging macros. > > > This is just for feedback to see if this is

Re: [PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

On 17/1/17 14:30, Eric Ren wrote: We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code carefully. However, we found that it's very hard

Re: [PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

On 17/1/17 14:30, Eric Ren wrote: We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code carefully. However, we found that it's very hard

[PATCH v2] usb: host: xhci: plat: check hcc_params after add hcd

From: William wu The commit 4ac53087d6d4 ("usb: xhci: plat: Create both HCDs before adding them") move add hcd to the end of probe, this cause hcc_params uninitiated, because xHCI driver sets hcc_params in xhci_gen_setup() called from usb_add_hcd(). This patch checks

[PATCH v2] usb: host: xhci: plat: check hcc_params after add hcd

From: William wu The commit 4ac53087d6d4 ("usb: xhci: plat: Create both HCDs before adding them") move add hcd to the end of probe, this cause hcc_params uninitiated, because xHCI driver sets hcc_params in xhci_gen_setup() called from usb_add_hcd(). This patch checks the Maximum Primary Stream

Re: [PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

On 01/17/2017 02:30 PM, Eric Ren wrote: > We are in the situation that we have to avoid recursive cluster locking, > but there is no way to check if a cluster lock has been taken by a > precess already. > > Mostly, we can avoid recursive locking by writing code carefully. > However, we found that

Re: [PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

On 01/17/2017 02:30 PM, Eric Ren wrote: > We are in the situation that we have to avoid recursive cluster locking, > but there is no way to check if a cluster lock has been taken by a > precess already. > > Mostly, we can avoid recursive locking by writing code carefully. > However, we found that

Re: [PATCH v3 2/2] ocfs2: fix deadlock issue when taking inode lock at vfs entry points

On 01/17/2017 02:30 PM, Eric Ren wrote: > Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") > results in a deadlock, as the author "Tariq Saeed" realized shortly > after the patch was merged. The discussion happened here >

Re: [PATCH v3 2/2] ocfs2: fix deadlock issue when taking inode lock at vfs entry points

On 01/17/2017 02:30 PM, Eric Ren wrote: > Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") > results in a deadlock, as the author "Tariq Saeed" realized shortly > after the patch was merged. The discussion happened here >

Re: [PATCH] tpm: add session handles to the save and restore of the tpm2 space manager

On Mon, Jan 16, 2017 at 03:18:45PM -0800, James Bottomley wrote: > On Mon, 2017-01-16 at 12:04 +0200, Jarkko Sakkinen wrote: > > On Fri, Jan 13, 2017 at 11:24:13AM -0800, James Bottomley wrote: > > > Session handles are slightly more difficult to manage because any > > > TPM > > > only has a

Re: [PATCH] tpm: add session handles to the save and restore of the tpm2 space manager

On Mon, Jan 16, 2017 at 03:18:45PM -0800, James Bottomley wrote: > On Mon, 2017-01-16 at 12:04 +0200, Jarkko Sakkinen wrote: > > On Fri, Jan 13, 2017 at 11:24:13AM -0800, James Bottomley wrote: > > > Session handles are slightly more difficult to manage because any > > > TPM > > > only has a

Re: [PATCH 1/1] x86: sanitize argument of clearcpuid command-line option

* Odzioba, Lukasz wrote: > > pr_warn("x86/cpu: Ignoring invalid "clearcpuid=%s' option!\n", arg) > > > > Which would save quite a bit of head scratching and frustration when > > someone has a > > bad enough day to add silly typos to the kernel cmdline. > > Is

[PATCH v2 6+/6] platform/x86: dell-wmi-led: fix coding style issues

Fix coding style issues in dell-wmi-led which checkpatch complains about to make sure the module gets a clean start in the x86 platform driver subsystem. Signed-off-by: Michał Kępień --- This is an extra patch that Jacek asked for [1]. [1] https://lkml.org/lkml/2017/1/16/631

Re: [PATCH 1/1] x86: sanitize argument of clearcpuid command-line option

* Odzioba, Lukasz wrote: > > pr_warn("x86/cpu: Ignoring invalid "clearcpuid=%s' option!\n", arg) > > > > Which would save quite a bit of head scratching and frustration when > > someone has a > > bad enough day to add silly typos to the kernel cmdline. > > Is there any particular reason

[PATCH v2 6+/6] platform/x86: dell-wmi-led: fix coding style issues

Fix coding style issues in dell-wmi-led which checkpatch complains about to make sure the module gets a clean start in the x86 platform driver subsystem. Signed-off-by: Michał Kępień --- This is an extra patch that Jacek asked for [1]. [1] https://lkml.org/lkml/2017/1/16/631

Re: [tpmdd-devel] [PATCH RFC v3 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Mon, Jan 16, 2017 at 09:28:17AM -0800, James Bottomley wrote: > On Mon, 2017-01-16 at 19:24 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 16, 2017 at 09:14:13AM -0700, Jason Gunthorpe wrote: > > > On Mon, Jan 16, 2017 at 03:12:11PM +0200, Jarkko Sakkinen wrote: > > > > > > > @@ -199,7 +227,9

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 11:05:42AM +0900, Byungchul Park wrote: > On Mon, Jan 16, 2017 at 04:10:01PM +0100, Peter Zijlstra wrote: > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > @@ -155,6 +164,9 @@ struct lockdep_map { > > > int cpu; > > >

Re: [tpmdd-devel] [PATCH RFC v3 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Mon, Jan 16, 2017 at 09:28:17AM -0800, James Bottomley wrote: > On Mon, 2017-01-16 at 19:24 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 16, 2017 at 09:14:13AM -0700, Jason Gunthorpe wrote: > > > On Mon, Jan 16, 2017 at 03:12:11PM +0200, Jarkko Sakkinen wrote: > > > > > > > @@ -199,7 +227,9

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 11:05:42AM +0900, Byungchul Park wrote: > On Mon, Jan 16, 2017 at 04:10:01PM +0100, Peter Zijlstra wrote: > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > @@ -155,6 +164,9 @@ struct lockdep_map { > > > int cpu; > > >

Re: [GIT PULL 4/4] ARM: defconfig: exynos: Defconfig for v4.11

On Fri, Jan 13, 2017 at 05:20:30PM +0200, Krzysztof Kozlowski wrote: > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are available in the git repository at: > >

Re: [GIT PULL 4/4] ARM: defconfig: exynos: Defconfig for v4.11

On Fri, Jan 13, 2017 at 05:20:30PM +0200, Krzysztof Kozlowski wrote: > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are available in the git repository at: > >

Re: [GIT PULL 2/4] ARM: dts: exynos: DT for v4.11

On Fri, Jan 13, 2017 at 05:20:28PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Few improvements and Exynos4412 DTSI removal. > > This pulls external dependecy from clock tree (one clock commit). > > Best regards, > Krzysztof > > > The following changes since commit

Re: [GIT PULL 2/4] ARM: dts: exynos: DT for v4.11

On Fri, Jan 13, 2017 at 05:20:28PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Few improvements and Exynos4412 DTSI removal. > > This pulls external dependecy from clock tree (one clock commit). > > Best regards, > Krzysztof > > > The following changes since commit

Re: [PATCH 2/3] Make static usermode helper binaries constant

On Mon, Jan 16, 2017 at 04:25:55PM -0500, J. Bruce Fields wrote: > On Mon, Jan 16, 2017 at 05:50:31PM +0100, Greg KH wrote: > > From: Greg Kroah-Hartman > > > > There are a number of usermode helper binaries that are "hard coded" in > > the kernel today, so mark them

Re: [PATCH 2/3] Make static usermode helper binaries constant

On Mon, Jan 16, 2017 at 04:25:55PM -0500, J. Bruce Fields wrote: > On Mon, Jan 16, 2017 at 05:50:31PM +0100, Greg KH wrote: > > From: Greg Kroah-Hartman > > > > There are a number of usermode helper binaries that are "hard coded" in > > the kernel today, so mark them as "const" to make it harder

Re: [GIT PULL] STi DT update for v4.11 round 1

On Thu, Jan 12, 2017 at 05:59:43PM +0100, Patrice Chotard wrote: > Hi Arnd, Kevin, Olof > > PLease consider this first round of STi dts update for v4.11 : > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are

Re: [GIT PULL 1/4] ARM: exynos: Mach/soc for v4.11

On Fri, Jan 13, 2017 at 05:20:27PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Mostly cleanups for v4.11. > > Best regards, > Krzysztof > > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are available in the

Re: [GIT PULL] STi DT update for v4.11 round 1

On Thu, Jan 12, 2017 at 05:59:43PM +0100, Patrice Chotard wrote: > Hi Arnd, Kevin, Olof > > PLease consider this first round of STi dts update for v4.11 : > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are

Re: [GIT PULL 1/4] ARM: exynos: Mach/soc for v4.11

On Fri, Jan 13, 2017 at 05:20:27PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Mostly cleanups for v4.11. > > Best regards, > Krzysztof > > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are available in the

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 11:05:42AM +0900, Byungchul Park wrote: > On Mon, Jan 16, 2017 at 04:10:01PM +0100, Peter Zijlstra wrote: > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > + > > > + /* > > > + * Whenever irq happens, these are updated so that we can > > > + *

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 11:05:42AM +0900, Byungchul Park wrote: > On Mon, Jan 16, 2017 at 04:10:01PM +0100, Peter Zijlstra wrote: > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > + > > > + /* > > > + * Whenever irq happens, these are updated so that we can > > > + *

Re: [GIT PULL 3/4] arm64: dts: exynos: DT for v4.11

On Fri, Jan 13, 2017 at 05:20:29PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Important: > 1. Unlike others, this is rebased on v4.10-rc2 because v4.10-rc1 was not >building on arm64. > 2. This contains pinctrl change (in header), acked by Linus Walleij. >Although I kept it on separate

Re: [GIT PULL 3/4] arm64: dts: exynos: DT for v4.11

On Fri, Jan 13, 2017 at 05:20:29PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Important: > 1. Unlike others, this is rebased on v4.10-rc2 because v4.10-rc1 was not >building on arm64. > 2. This contains pinctrl change (in header), acked by Linus Walleij. >Although I kept it on separate

Re: [PATCH] usb: dwc3: ep0: Fix the possible missed request for handling delay STATUS phase

Hi, On 16 January 2017 at 20:06, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >> Hi, >> >> On 16 January 2017 at 19:29, Felipe Balbi wrote: >>> >>> Hi, >>> >>> Baolin Wang writes: Hi, On

Re: [PATCH] usb: dwc3: ep0: Fix the possible missed request for handling delay STATUS phase

Hi, On 16 January 2017 at 20:06, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >> Hi, >> >> On 16 January 2017 at 19:29, Felipe Balbi wrote: >>> >>> Hi, >>> >>> Baolin Wang writes: Hi, On 16 January 2017 at 18:56, Felipe Balbi wrote: > > Hi, > > Baolin

Re: [PATCH 3/3] Reverted "mm: bail out in shrink_inactive_list()"

On Mon, Jan 16, 2017 at 08:33:17PM +0100, Michal Hocko wrote: > From: Michal Hocko > > This reverts 91dcade47a3d0e7c31464ef05f56c08e92a0e9c2. > inactive_reclaimable_pages shouldn't be needed anymore since that > get_scan_count is aware of the eligble zones ("mm, vmscan: consider

Re: [PATCH 3/3] Reverted "mm: bail out in shrink_inactive_list()"

On Mon, Jan 16, 2017 at 08:33:17PM +0100, Michal Hocko wrote: > From: Michal Hocko > > This reverts 91dcade47a3d0e7c31464ef05f56c08e92a0e9c2. > inactive_reclaimable_pages shouldn't be needed anymore since that > get_scan_count is aware of the eligble zones ("mm, vmscan: consider > eligible zones

Re: [PATCH 1/3] mm, vmscan: cleanup lru size claculations

On Mon, Jan 16, 2017 at 08:33:15PM +0100, Michal Hocko wrote: > From: Michal Hocko > > lruvec_lru_size returns the full size of the LRU list while we sometimes > need a value reduced only to eligible zones (e.g. for lowmem requests). > inactive_list_is_low is one such user.

Re: [PATCH 1/3] mm, vmscan: cleanup lru size claculations

On Mon, Jan 16, 2017 at 08:33:15PM +0100, Michal Hocko wrote: > From: Michal Hocko > > lruvec_lru_size returns the full size of the LRU list while we sometimes > need a value reduced only to eligible zones (e.g. for lowmem requests). > inactive_list_is_low is one such user. Later patches will

[PATCH v3 2/2] ocfs2: fix deadlock issue when taking inode lock at vfs entry points

Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") results in a deadlock, as the author "Tariq Saeed" realized shortly after the patch was merged. The discussion happened here (https://oss.oracle.com/pipermail/ocfs2-devel/2015-September/011085.html). The reason why taking

[PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code carefully. However, we found that it's very hard to handle the routines that are

[PATCH v3 0/2] fix deadlock caused by recursive cluster locking

This is a formal patch set v2 to solve the deadlock issue on which I previously started a RFC (draft patch), and the discussion happened here: [https://oss.oracle.com/pipermail/ocfs2-devel/2016-October/012455.html] Compared to the previous draft patch, this one is much simple and neat. It neither

[PATCH v3 2/2] ocfs2: fix deadlock issue when taking inode lock at vfs entry points

Commit 743b5f1434f5 ("ocfs2: take inode lock in ocfs2_iop_set/get_acl()") results in a deadlock, as the author "Tariq Saeed" realized shortly after the patch was merged. The discussion happened here (https://oss.oracle.com/pipermail/ocfs2-devel/2015-September/011085.html). The reason why taking

[PATCH v3 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code carefully. However, we found that it's very hard to handle the routines that are

[PATCH v3 0/2] fix deadlock caused by recursive cluster locking

This is a formal patch set v2 to solve the deadlock issue on which I previously started a RFC (draft patch), and the discussion happened here: [https://oss.oracle.com/pipermail/ocfs2-devel/2016-October/012455.html] Compared to the previous draft patch, this one is much simple and neat. It neither

Re: + mm-vmscan-add-mm_vmscan_inactive_list_is_low-tracepoint.patch added to -mm tree

Hello, On Fri, Jan 13, 2017 at 10:10:09AM +0100, Michal Hocko wrote: > On Fri 13-01-17 17:57:34, Minchan Kim wrote: > > On Fri, Jan 13, 2017 at 08:47:07AM +0100, Michal Hocko wrote: > > > On Fri 13-01-17 10:37:24, Minchan Kim wrote: > > > > Hello, > > > > > > > > On Thu, Jan 12, 2017 at

Re: + mm-vmscan-add-mm_vmscan_inactive_list_is_low-tracepoint.patch added to -mm tree

Hello, On Fri, Jan 13, 2017 at 10:10:09AM +0100, Michal Hocko wrote: > On Fri 13-01-17 17:57:34, Minchan Kim wrote: > > On Fri, Jan 13, 2017 at 08:47:07AM +0100, Michal Hocko wrote: > > > On Fri 13-01-17 10:37:24, Minchan Kim wrote: > > > > Hello, > > > > > > > > On Thu, Jan 12, 2017 at

Re: [PATCH v4 1/3] dt: bindings: add documentation for zx2967 family thermal sensor

On Tue, Jan 17, 2017 at 01:38:48PM +0800, Baoyou Xie wrote: > On 17 January 2017 at 13:27, Eduardo Valentin wrote: > > It's a good idea:) In fact, we defined some thermal zones and used IPA > on products. > Cool! Any feedback on using IPA?

Re: [PATCH v4 1/3] dt: bindings: add documentation for zx2967 family thermal sensor

On Tue, Jan 17, 2017 at 01:38:48PM +0800, Baoyou Xie wrote: > On 17 January 2017 at 13:27, Eduardo Valentin wrote: > > It's a good idea:) In fact, we defined some thermal zones and used IPA > on products. > Cool! Any feedback on using IPA?

[PATCH] ahci: qoriq: added ls2088a platforms support

From: Tang Yuantian Ls2088a is new introduced arm-based soc with sata support with following features: 1. Complies with the serial ATA 3.0 specification and the AHCI 1.3.1 specification 2. Contains a high-speed descriptor-based DMA controller 3. Supports the following:

[PATCH] ahci: qoriq: added ls2088a platforms support

From: Tang Yuantian Ls2088a is new introduced arm-based soc with sata support with following features: 1. Complies with the serial ATA 3.0 specification and the AHCI 1.3.1 specification 2. Contains a high-speed descriptor-based DMA controller 3. Supports the following: a. Speeds of 1.5

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 11:33:41AM +0900, Byungchul Park wrote: > On Mon, Jan 16, 2017 at 04:13:19PM +0100, Peter Zijlstra wrote: > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > + /* > > > + * We assign class_idx here redundantly even though following > > > + * memcpy

Re: [PATCH v4 07/15] lockdep: Implement crossrelease feature

On Tue, Jan 17, 2017 at 11:33:41AM +0900, Byungchul Park wrote: > On Mon, Jan 16, 2017 at 04:13:19PM +0100, Peter Zijlstra wrote: > > On Fri, Dec 09, 2016 at 02:12:03PM +0900, Byungchul Park wrote: > > > + /* > > > + * We assign class_idx here redundantly even though following > > > + * memcpy

Re: [GIT PULL] ARM: exynos: Fixes for v4.10

On Fri, Jan 13, 2017 at 04:32:25PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Just a couple of minor fixes for this release cycle. > > Best regards, > Krzysztof > > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)

Re: [GIT PULL] ARM: exynos: Fixes for v4.10

On Fri, Jan 13, 2017 at 04:32:25PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Just a couple of minor fixes for this release cycle. > > Best regards, > Krzysztof > > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)

[PATCH v2] thermal/intel_powerclamp: Fix sched_setscheduler fail

From: "Liu, Xinwu" The schedule policy of thread "kidle_inject" is SCHED_NORMAL: [ 772.796284] intel_powerclamp: Start idle injection to reduce power [ 772.825757] [ cut here ] [ 772.825877] WARNING: CPU: 0 PID: 2140 at

[PATCH v2] thermal/intel_powerclamp: Fix sched_setscheduler fail

From: "Liu, Xinwu" The schedule policy of thread "kidle_inject" is SCHED_NORMAL: [ 772.796284] intel_powerclamp: Start idle injection to reduce power [ 772.825757] [ cut here ] [ 772.825877] WARNING: CPU: 0 PID: 2140 at

Re: [PATCH v7 3/3] arm64: dts: exynos: Add tm2 touchkey node

Hi, I tested this patch on v6[1] and replied it. But, this version is missing the my tested-by and reviewed-by tag. [1] https://patchwork.kernel.org/patch/9504139/ So, I add my reviewed-by and tested-by tag again. Reviewed-by: Chanwoo Choi Tested-by: Chanwoo Choi

Re: [PATCH v7 3/3] arm64: dts: exynos: Add tm2 touchkey node

Hi, I tested this patch on v6[1] and replied it. But, this version is missing the my tested-by and reviewed-by tag. [1] https://patchwork.kernel.org/patch/9504139/ So, I add my reviewed-by and tested-by tag again. Reviewed-by: Chanwoo Choi Tested-by: Chanwoo Choi On 2017년 01월 17일 14:54,

Re: [PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

On Mon, Jan 16, 2017 at 2:39 AM, Neil Armstrong wrote: > On 01/15/2017 03:43 PM, Andreas Färber wrote: >> Am 13.01.2017 um 21:03 schrieb Kevin Hilman: >>> Neil Armstrong writes: >>> The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of

Re: [PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

On Mon, Jan 16, 2017 at 2:39 AM, Neil Armstrong wrote: > On 01/15/2017 03:43 PM, Andreas Färber wrote: >> Am 13.01.2017 um 21:03 schrieb Kevin Hilman: >>> Neil Armstrong writes: >>> The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, this patch adds this

Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support

On Friday 13 January 2017 11:50 PM, Tony Lindgren wrote: > * Vignesh R [170113 00:03]: >> This patch series re enables DMA support for UART 8250_omap driver. >> >> Tested on AM335x, AM437x that use EDMA and OMAP5 and DRA74 EVM with >> SDMA. > > Is 8250_omap serial console

Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support

On Friday 13 January 2017 11:50 PM, Tony Lindgren wrote: > * Vignesh R [170113 00:03]: >> This patch series re enables DMA support for UART 8250_omap driver. >> >> Tested on AM335x, AM437x that use EDMA and OMAP5 and DRA74 EVM with >> SDMA. > > Is 8250_omap serial console working for you on

[PATCH v7 0/3] Add touch key driver support for TM2

Hi, This patch is last three patch from https://lkml.org/lkml/2017/1/6/277. because 1 and 2 patches have already been merged by Krzysztof. This patchset adds support for the tm2 touchkey device. The driver has been ported from Tizen Kernel, originally written by Beomho. I ported it to the

[PATCH v7 2/3] input: tm2-touchkey: Add touchkey driver support for TM2

This patch adds support for the TM2 touch key and led functionality. The driver interfaces with userspace through an input device and reports KEY_PHONE and KEY_BACK event types. LED brightness can be controlled by "/sys/class/leds/tm2-touchkey/brightness". Signed-off-by: Beomho Seo

[PATCH v7 0/3] Add touch key driver support for TM2

Hi, This patch is last three patch from https://lkml.org/lkml/2017/1/6/277. because 1 and 2 patches have already been merged by Krzysztof. This patchset adds support for the tm2 touchkey device. The driver has been ported from Tizen Kernel, originally written by Beomho. I ported it to the

[PATCH v7 2/3] input: tm2-touchkey: Add touchkey driver support for TM2

This patch adds support for the TM2 touch key and led functionality. The driver interfaces with userspace through an input device and reports KEY_PHONE and KEY_BACK event types. LED brightness can be controlled by "/sys/class/leds/tm2-touchkey/brightness". Signed-off-by: Beomho Seo

[PATCH v7 3/3] arm64: dts: exynos: Add tm2 touchkey node

Add DT node support for TM2 touchkey device. Signed-off-by: Beomho Seo Signed-off-by: Jaechul Lee Signed-off-by: Andi Shyti Reviewed-by: Javier Martinez Canillas ---

[PATCH v7 1/3] input: Add support for the tm2 touchkey device driver

This patch adds the binding description of the tm2 touchkey device driver. Signed-off-by: Jaechul Lee Reviewed-by: Javier Martinez Canillas Reviewed-by: Andi Shyti Reviewed-by: Chanwoo Choi

[PATCH v7 3/3] arm64: dts: exynos: Add tm2 touchkey node

Add DT node support for TM2 touchkey device. Signed-off-by: Beomho Seo Signed-off-by: Jaechul Lee Signed-off-by: Andi Shyti Reviewed-by: Javier Martinez Canillas --- arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 13 + 1 file changed, 13 insertions(+) diff --git

[PATCH v7 1/3] input: Add support for the tm2 touchkey device driver

This patch adds the binding description of the tm2 touchkey device driver. Signed-off-by: Jaechul Lee Reviewed-by: Javier Martinez Canillas Reviewed-by: Andi Shyti Reviewed-by: Chanwoo Choi Acked-by: Rob Herring Acked-by: Krzysztof Kozlowski --- .../bindings/input/cypress,tm2-touchkey.txt

Re: [PATCH] pcie: ti: Provide patch to force GEN1 PCIe operation

Hi Joao, On Monday 16 January 2017 10:31 PM, Joao Pinto wrote: > > Hi, > > Às 10:13 AM de 1/16/2017, Kishon Vijay Abraham I escreveu: >> + Joao, Jingoo >> >> Hi, >> >> On Monday 16 January 2017 03:01 PM, Lukasz Majewski wrote: >>> Hi Kishon, >>> Hi Łukasz, On Monday 16 January

Re: [PATCH] pcie: ti: Provide patch to force GEN1 PCIe operation

Hi Joao, On Monday 16 January 2017 10:31 PM, Joao Pinto wrote: > > Hi, > > Às 10:13 AM de 1/16/2017, Kishon Vijay Abraham I escreveu: >> + Joao, Jingoo >> >> Hi, >> >> On Monday 16 January 2017 03:01 PM, Lukasz Majewski wrote: >>> Hi Kishon, >>> Hi Łukasz, On Monday 16 January

  1   2   3   4   5   6   7   8   9   10   >