Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On (08/23/17 13:35), Boqun Feng wrote: > > KERN_CONT and "\n" should not be together. "\n" flushes the cont > > buffer immediately. > > > > Hmm.. Not quite familiar with printk() stuffs, but I could see several > usages of printk(KERN_CONT "...\n") in kernel. > > Did a bit research myself, and

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On (08/23/17 13:35), Boqun Feng wrote: > > KERN_CONT and "\n" should not be together. "\n" flushes the cont > > buffer immediately. > > > > Hmm.. Not quite familiar with printk() stuffs, but I could see several > usages of printk(KERN_CONT "...\n") in kernel. > > Did a bit research myself, and

Re: [PATCH 3/3] ARM: dts: sun8i: Add board dts file for Banana Pi M2 Berry

于 2017年8月23日 GMT+08:00 上午4:12:15, Maxime Ripard 写到: >On Tue, Aug 22, 2017 at 02:17:42PM +0800, Icenowy Zheng wrote: >> +_vcc5v0 { >> +gpio = < 7 23 GPIO_ACTIVE_HIGH>; /* PH23 */ >> +enable-active-high; >> +}; > >Same thing here, you're not using that

Re: [PATCH 3/3] ARM: dts: sun8i: Add board dts file for Banana Pi M2 Berry

于 2017年8月23日 GMT+08:00 上午4:12:15, Maxime Ripard 写到: >On Tue, Aug 22, 2017 at 02:17:42PM +0800, Icenowy Zheng wrote: >> +_vcc5v0 { >> +gpio = < 7 23 GPIO_ACTIVE_HIGH>; /* PH23 */ >> +enable-active-high; >> +}; > >Same thing here, you're not using that regulator anywhere. You don't >even

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On (08/23/17 13:35), Boqun Feng wrote: [..] > > > printk(KERN_CONT ");\n"); > > > > KERN_CONT and "\n" should not be together. "\n" flushes the cont > > buffer immediately. > > > > Hmm.. Not quite familiar with printk() stuffs, but I could see several > usages of printk(KERN_CONT

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On (08/23/17 13:35), Boqun Feng wrote: [..] > > > printk(KERN_CONT ");\n"); > > > > KERN_CONT and "\n" should not be together. "\n" flushes the cont > > buffer immediately. > > > > Hmm.. Not quite familiar with printk() stuffs, but I could see several > usages of printk(KERN_CONT

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On Wed, Aug 23, 2017 at 12:38:13PM +0800, Boqun Feng wrote: > From: Boqun Feng > Date: Wed, 23 Aug 2017 12:12:16 +0800 > Subject: [PATCH] lockdep: Print proper scenario if cross deadlock detected at > acquisition time > > For a potential deadlock about CROSSRELEASE as

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On Wed, Aug 23, 2017 at 12:38:13PM +0800, Boqun Feng wrote: > From: Boqun Feng > Date: Wed, 23 Aug 2017 12:12:16 +0800 > Subject: [PATCH] lockdep: Print proper scenario if cross deadlock detected at > acquisition time > > For a potential deadlock about CROSSRELEASE as follow: > > P1

[PATCH v3 3/5] dt-bindings: sdhci-omap: Add bindings for the sdhci-omap controller

Add binding for the TI's sdhci-omap controller. This now includes only a subset of properties documented in ti-omap-hsmmc.txt but will eventually include all the properties. Signed-off-by: Kishon Vijay Abraham I --- Changes from v2: *) Fixed example to use the updated compatible

[PATCH v3 3/5] dt-bindings: sdhci-omap: Add bindings for the sdhci-omap controller

Add binding for the TI's sdhci-omap controller. This now includes only a subset of properties documented in ti-omap-hsmmc.txt but will eventually include all the properties. Signed-off-by: Kishon Vijay Abraham I --- Changes from v2: *) Fixed example to use the updated compatible Changes from

Re: linux-next: manual merge of the net-next tree with the net tree

On Wed, Aug 23, 2017 at 11:31:05AM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > net/ipv6/ip6_fib.c > > between commit: > > c5cff8561d2d ("ipv6: add rcu grace period before freeing fib6_node") > > from the net tree and

Re: linux-next: manual merge of the net-next tree with the net tree

On Wed, Aug 23, 2017 at 11:31:05AM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > net/ipv6/ip6_fib.c > > between commit: > > c5cff8561d2d ("ipv6: add rcu grace period before freeing fib6_node") > > from the net tree and

Re: [PATCH 1/2] staging: android: ion: Remove extra line (checkpatch)

On Tue, Aug 22, 2017 at 10:55:36PM -0400, Nick Fox wrote: > Remove extra blank line (reported by checkpatch.pl) > > Signed-off-by: Nick Fox > --- > drivers/staging/android/ion/ion_cma_heap.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git

Re: [PATCH 1/2] staging: android: ion: Remove extra line (checkpatch)

On Tue, Aug 22, 2017 at 10:55:36PM -0400, Nick Fox wrote: > Remove extra blank line (reported by checkpatch.pl) > > Signed-off-by: Nick Fox > --- > drivers/staging/android/ion/ion_cma_heap.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/staging/android/ion/ion_cma_heap.c >

Re: [PATCH] staging: fsl-mc: be consistent when checking strcmp() returns

On Tue, Aug 22, 2017 at 07:33:45PM -0700, Joe Perches wrote: > On Tue, 2017-08-22 at 18:40 -0700, Greg KH wrote: > > On Thu, Aug 17, 2017 at 02:55:04PM +0300, laurentiu.tu...@nxp.com wrote: > > > From: Laurentiu Tudor > > > > > > Throughout the driver we use == 0 / != 0

[PATCH] rtc: ds1307: add basic support for ds1341 chip

This adds support for reading and writing date/time from/to ds1314 chip. Other functionality (alarms, inout clock, output clock) is not added yet, because availability of that depends on chip connections. Signed-off-by: Nikita Yushchenko --- drivers/rtc/Kconfig

Re: [PATCH] staging: fsl-mc: be consistent when checking strcmp() returns

On Tue, Aug 22, 2017 at 07:33:45PM -0700, Joe Perches wrote: > On Tue, 2017-08-22 at 18:40 -0700, Greg KH wrote: > > On Thu, Aug 17, 2017 at 02:55:04PM +0300, laurentiu.tu...@nxp.com wrote: > > > From: Laurentiu Tudor > > > > > > Throughout the driver we use == 0 / != 0 to check strcmp() returns

[PATCH] rtc: ds1307: add basic support for ds1341 chip

This adds support for reading and writing date/time from/to ds1314 chip. Other functionality (alarms, inout clock, output clock) is not added yet, because availability of that depends on chip connections. Signed-off-by: Nikita Yushchenko --- drivers/rtc/Kconfig | 10 +-

Re: [PATCH 2/2] staging: android: ion: Change argument to kmalloc (checkpatch)

On Tue, Aug 22, 2017 at 10:55:37PM -0400, Nick Fox wrote: > Change argument to kmalloc() to fix style issue, reported by checkpatch > > Signed-off-by: Nick Fox > --- > drivers/staging/android/ion/ion_cma_heap.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >

Re: [PATCH 2/2] staging: android: ion: Change argument to kmalloc (checkpatch)

On Tue, Aug 22, 2017 at 10:55:37PM -0400, Nick Fox wrote: > Change argument to kmalloc() to fix style issue, reported by checkpatch > > Signed-off-by: Nick Fox > --- > drivers/staging/android/ion/ion_cma_heap.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH] binder: let ANDROID_BINDER_IPC_32BIT be selectable on 32bit ARM

On Tue, Aug 22, 2017 at 08:14:10PM -0700, John Stultz wrote: > On Tue, Aug 22, 2017 at 8:01 PM, Jisheng Zhang wrote: > > On Tue, 22 Aug 2017 19:57:04 -0700 John Stultz wrote: > > > >> On Tue, Aug 22, 2017 at 7:56 PM, John Stultz > >> wrote: > >> > On

Re: [PATCH] binder: let ANDROID_BINDER_IPC_32BIT be selectable on 32bit ARM

On Tue, Aug 22, 2017 at 08:14:10PM -0700, John Stultz wrote: > On Tue, Aug 22, 2017 at 8:01 PM, Jisheng Zhang wrote: > > On Tue, 22 Aug 2017 19:57:04 -0700 John Stultz wrote: > > > >> On Tue, Aug 22, 2017 at 7:56 PM, John Stultz > >> wrote: > >> > On Tue, Aug 22, 2017 at 7:34 PM, Jisheng Zhang

Re: [PATCH] binder: let ANDROID_BINDER_IPC_32BIT be selectable on 32bit ARM

On Wed, Aug 23, 2017 at 10:34:20AM +0800, Jisheng Zhang wrote: > On Tue, 22 Aug 2017 18:51:08 -0700 Greg KH wrote: > > > On Tue, Aug 08, 2017 at 07:03:05PM +0800, Jisheng Zhang wrote: > > > As noted in commit d0bdff0db809 ("staging: Fix build issues with new > > > binder API"), we can add back

Re: [PATCH] binder: let ANDROID_BINDER_IPC_32BIT be selectable on 32bit ARM

On Wed, Aug 23, 2017 at 10:34:20AM +0800, Jisheng Zhang wrote: > On Tue, 22 Aug 2017 18:51:08 -0700 Greg KH wrote: > > > On Tue, Aug 08, 2017 at 07:03:05PM +0800, Jisheng Zhang wrote: > > > As noted in commit d0bdff0db809 ("staging: Fix build issues with new > > > binder API"), we can add back

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On Wed, Aug 23, 2017 at 01:46:48PM +0900, Sergey Senozhatsky wrote: > On (08/23/17 12:38), Boqun Feng wrote: > [..] > > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c > > index 642fb5362507..a3709e15f609 100644 > > --- a/kernel/locking/lockdep.c > > +++ b/kernel/locking/lockdep.c

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On Wed, Aug 23, 2017 at 01:46:48PM +0900, Sergey Senozhatsky wrote: > On (08/23/17 12:38), Boqun Feng wrote: > [..] > > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c > > index 642fb5362507..a3709e15f609 100644 > > --- a/kernel/locking/lockdep.c > > +++ b/kernel/locking/lockdep.c

Re: [PATCH] staging: olpc_dcon: Change fixed function names with "%s: ", __func__

On Wed, Aug 23, 2017 at 01:06:52PM +0800, Shurong Zhang wrote: > Replace hard-coded function names in strings with "%s", __func__ > in the olpc_dcon.c file. Issue found by checkpatch.pl. What is up with the odd indentation? And why did you send this twice? Which patch should I use? I'll

Re: [PATCH] staging: olpc_dcon: Change fixed function names with "%s: ", __func__

On Wed, Aug 23, 2017 at 01:06:52PM +0800, Shurong Zhang wrote: > Replace hard-coded function names in strings with "%s", __func__ > in the olpc_dcon.c file. Issue found by checkpatch.pl. What is up with the odd indentation? And why did you send this twice? Which patch should I use? I'll

RE: [PATCH v2 1/6] fsl/fman: enable FMan Keygen

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Wednesday, August 23, 2017 7:47 AM > To: Madalin-cristian Bucur > Cc: net...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v2 1/6]

RE: [PATCH v2 1/6] fsl/fman: enable FMan Keygen

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Wednesday, August 23, 2017 7:47 AM > To: Madalin-cristian Bucur > Cc: net...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v2 1/6] fsl/fman: enable FMan

Re: [PATCH] ALSA: core: Use common error handling code in two functions

On Tue, 22 Aug 2017 21:12:02 +0200, SF Markus Elfring wrote: > > From: Markus Elfring > Date: Tue, 22 Aug 2017 21:01:01 +0200 > > Add jump targets so that a bit of exception handling can be better reused > at the end of these functions. > > This issue was

Re: [PATCH] ALSA: core: Use common error handling code in two functions

On Tue, 22 Aug 2017 21:12:02 +0200, SF Markus Elfring wrote: > > From: Markus Elfring > Date: Tue, 22 Aug 2017 21:01:01 +0200 > > Add jump targets so that a bit of exception handling can be better reused > at the end of these functions. > > This issue was detected by using the Coccinelle

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

M +, Bart Van Assche wrote: > > > > On Tue, 2017-08-22 at 19:47 +0900, Sergey Senozhatsky wrote: > > > > > == > > > > > WARNING: possible circular locking dependency detected > > > > &

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

M +, Bart Van Assche wrote: > > > > On Tue, 2017-08-22 at 19:47 +0900, Sergey Senozhatsky wrote: > > > > > == > > > > > WARNING: possible circular locking dependency detected > > > > &

Re: Fwd: struct pt_regs missing in /usr/include/ tree for eBPF program compile

On Mon, Aug 14, 2017 at 02:08:07PM +0200, Heiko Carstens wrote: > > Now, I would like to avoid going down that road to pull > > in kernel internal headers into test_verifier.c, could > > we instead add a bpf_ptregs.h helper in tools/testing/selftests/bpf/, > > where s390 and arm64 would put a

Re: Fwd: struct pt_regs missing in /usr/include/ tree for eBPF program compile

On Mon, Aug 14, 2017 at 02:08:07PM +0200, Heiko Carstens wrote: > > Now, I would like to avoid going down that road to pull > > in kernel internal headers into test_verifier.c, could > > we instead add a bpf_ptregs.h helper in tools/testing/selftests/bpf/, > > where s390 and arm64 would put a

[PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response

We need a wrapper function to determine when a particular device is returning Configuration Request Retry Status (CRS) response. This will only happen if the root port supports CRS visibility. Signed-off-by: Sinan Kaya --- drivers/pci/pci.h | 4 1 file changed, 4

[PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response

We need a wrapper function to determine when a particular device is returning Configuration Request Retry Status (CRS) response. This will only happen if the root port supports CRS visibility. Signed-off-by: Sinan Kaya --- drivers/pci/pci.h | 4 1 file changed, 4 insertions(+) diff --git

[PATCH V12 4/5] PCI: Handle CRS ("device not ready") returned by device after FLR

Sporadic reset issues have been observed with Intel 750 NVMe drive while assigning the physical function to the guest machine. The sequence of events observed is as follows: - perform a Function Level Reset (FLR) - sleep up to 1000ms total - read ~0 from PCI_COMMAND - warn that the

[PATCH V12 4/5] PCI: Handle CRS ("device not ready") returned by device after FLR

Sporadic reset issues have been observed with Intel 750 NVMe drive while assigning the physical function to the guest machine. The sequence of events observed is as follows: - perform a Function Level Reset (FLR) - sleep up to 1000ms total - read ~0 from PCI_COMMAND - warn that the

[PATCH V12 5/5] PCI: Warn periodically while waiting for device to become ready

Add a print statement in pci_bus_wait_crs() so that user observes the progress of device polling instead of silently waiting for timeout to be reached. Signed-off-by: Sinan Kaya [bhelgaas: check for timeout first so we don't print "waiting, giving up", always print time

[PATCH V12 1/5] PCI: Don't ignore valid response before CRS timeout

From: Bjorn Helgaas While waiting for a device to become ready (i.e., to return a non-CRS completion to a read of its Vendor ID), if we got a valid response to the very last read before timing out, we printed a warning and gave up on the device even though it was actually

[PATCH V12 1/5] PCI: Don't ignore valid response before CRS timeout

From: Bjorn Helgaas While waiting for a device to become ready (i.e., to return a non-CRS completion to a read of its Vendor ID), if we got a valid response to the very last read before timing out, we printed a warning and gave up on the device even though it was actually ready. For a typical

[PATCH V12 5/5] PCI: Warn periodically while waiting for device to become ready

Add a print statement in pci_bus_wait_crs() so that user observes the progress of device polling instead of silently waiting for timeout to be reached. Signed-off-by: Sinan Kaya [bhelgaas: check for timeout first so we don't print "waiting, giving up", always print time we've slept (not the

[PATCH V12 3/5] PCI: Factor out pci_bus_wait_crs()

Configuration Request Retry Status (CRS) was previously hidden inside pci_bus_read_dev_vendor_id(). We want to add support for CRS in other situations, such as waiting for a device to become ready after a Function Level Reset. Move CRS handling into pci_bus_wait_crs() so it can be called from

[PATCH V12 3/5] PCI: Factor out pci_bus_wait_crs()

Configuration Request Retry Status (CRS) was previously hidden inside pci_bus_read_dev_vendor_id(). We want to add support for CRS in other situations, such as waiting for a device to become ready after a Function Level Reset. Move CRS handling into pci_bus_wait_crs() so it can be called from

Re: [PATCH 0/2] Separate NUMA statistics from zone statistics

On 08/22/2017 06:14 PM, kemi wrote: > when performance is not important and when you want all tooling to work, you > set: > > sysctl vm.strict_stats=1 > > but if you can tolerate some possible tool breakage and some decreased > counter precision, you can do: > > sysctl

Re: [PATCH 0/2] Separate NUMA statistics from zone statistics

On 08/22/2017 06:14 PM, kemi wrote: > when performance is not important and when you want all tooling to work, you > set: > > sysctl vm.strict_stats=1 > > but if you can tolerate some possible tool breakage and some decreased > counter precision, you can do: > > sysctl

[PATCH v2 net-next 1/1] hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

Hyper-V Sockets (hv_sock) supplies a byte-stream based communication mechanism between the host and the guest. It uses VMBus ringbuffer as the transportation layer. With hv_sock, applications between the host (Windows 10, Windows Server 2016 or newer) and the guest can talk with each other using

[PATCH v2 net-next 1/1] hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

Hyper-V Sockets (hv_sock) supplies a byte-stream based communication mechanism between the host and the guest. It uses VMBus ringbuffer as the transportation layer. With hv_sock, applications between the host (Windows 10, Windows Server 2016 or newer) and the guest can talk with each other using

Re: [PATCH v4] iio: accel: mma8452: improvements to handle multiple events

Am 23.08.2017 02:29 schrieb Harinath Nampally: If rising: use transient OR ff_mt device-dependent like before. But now save it in a simple flag, whether transient registers are available. Ok, is it good idea to add the flag to struct mma_chip_info like below? * @mma_scales:

Re: [PATCH v4] iio: accel: mma8452: improvements to handle multiple events

Am 23.08.2017 02:29 schrieb Harinath Nampally: If rising: use transient OR ff_mt device-dependent like before. But now save it in a simple flag, whether transient registers are available. Ok, is it good idea to add the flag to struct mma_chip_info like below? * @mma_scales:

Re: ext4 bug fixes for 4.13

On Tue, Aug 22, 2017 at 9:16 PM, Theodore Ts'o wrote: > > Theodore Ts'o (1): > ext4: fix clang build regression Tssk. The authorship attribution here looks wrong, and the authorship (Arnd) ended up being in the commit log rather than the author field. Please be more careful

Re: ext4 bug fixes for 4.13

On Tue, Aug 22, 2017 at 9:16 PM, Theodore Ts'o wrote: > > Theodore Ts'o (1): > ext4: fix clang build regression Tssk. The authorship attribution here looks wrong, and the authorship (Arnd) ended up being in the commit log rather than the author field. Please be more careful when applying

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On (08/23/17 12:38), Boqun Feng wrote: [..] > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c > index 642fb5362507..a3709e15f609 100644 > --- a/kernel/locking/lockdep.c > +++ b/kernel/locking/lockdep.c > @@ -1156,6 +1156,23 @@ print_circular_lock_scenario(struct held_lock *src, >

Re: [PATCH v2 1/6] fsl/fman: enable FMan Keygen

From: Madalin-cristian Bucur Date: Wed, 23 Aug 2017 04:36:56 + > The struct fman is only visible in the fman file, the fman port > module uses struct fman as an opaque pointer, thus this export. Don't use that programming model. Export the datastructure properly to

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

On (08/23/17 12:38), Boqun Feng wrote: [..] > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c > index 642fb5362507..a3709e15f609 100644 > --- a/kernel/locking/lockdep.c > +++ b/kernel/locking/lockdep.c > @@ -1156,6 +1156,23 @@ print_circular_lock_scenario(struct held_lock *src, >

Re: [PATCH v2 1/6] fsl/fman: enable FMan Keygen

From: Madalin-cristian Bucur Date: Wed, 23 Aug 2017 04:36:56 + > The struct fman is only visible in the fman file, the fman port > module uses struct fman as an opaque pointer, thus this export. Don't use that programming model. Export the datastructure properly to it's users. This

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

Sergey Senozhatsky wrote: > > > > == > > > > WARNING: possible circular locking dependency detected > > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted > > > > --

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

Sergey Senozhatsky wrote: > > > > == > > > > WARNING: possible circular locking dependency detected > > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted > > > > --

Re: [PATCH 13/18] rpmsg: glink: Add rx done command

On 8/22/2017 7:46 PM, Sricharan R wrote: Hi, +    /* Take it off the tree of receive intents */ +    if (!intent->reuse) { +    spin_lock(>intent_lock); +    idr_remove(>liids, intent->id); +    spin_unlock(>intent_lock); +    } + +    /* Schedule the sending of a rx_done

Re: [PATCH 13/18] rpmsg: glink: Add rx done command

On 8/22/2017 7:46 PM, Sricharan R wrote: Hi, +    /* Take it off the tree of receive intents */ +    if (!intent->reuse) { +    spin_lock(>intent_lock); +    idr_remove(>liids, intent->id); +    spin_unlock(>intent_lock); +    } + +    /* Schedule the sending of a rx_done

Re: [PATCH v11 2/4] PCI: Factor out pci_bus_wait_crs()

On 8/21/2017 3:37 PM, Sinan Kaya wrote: > bool pci_bus_crs_pending(struct pci_dev *dev, u32 l) > { > if !pci_bus_crs_vis_supported(dev->parent) > return false; Apparently, I can't do this. By the time, we come to here from vendor id read function, the topology has not been set

Re: [PATCH v11 2/4] PCI: Factor out pci_bus_wait_crs()

On 8/21/2017 3:37 PM, Sinan Kaya wrote: > bool pci_bus_crs_pending(struct pci_dev *dev, u32 l) > { > if !pci_bus_crs_vis_supported(dev->parent) > return false; Apparently, I can't do this. By the time, we come to here from vendor id read function, the topology has not been set

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

Sergey Senozhatsky wrote: > > > > == > > > > WARNING: possible circular locking dependency detected > > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted > > > > --

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

Sergey Senozhatsky wrote: > > > > == > > > > WARNING: possible circular locking dependency detected > > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted > > > > --

RE: [PATCH v2 1/6] fsl/fman: enable FMan Keygen

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] > On Behalf Of David Miller > Sent: Wednesday, August 23, 2017 12:35 AM > Subject: Re: [PATCH v2 1/6] fsl/fman: enable FMan Keygen > > From: Madalin Bucur > Date: Tue,

RE: [PATCH v2 1/6] fsl/fman: enable FMan Keygen

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] > On Behalf Of David Miller > Sent: Wednesday, August 23, 2017 12:35 AM > Subject: Re: [PATCH v2 1/6] fsl/fman: enable FMan Keygen > > From: Madalin Bucur > Date: Tue, 22 Aug 2017 20:31:01

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

From: Vallish Vaidyeshwara Date: Wed, 23 Aug 2017 00:10:25 + > I am submitting 2 patch series to enable hires timer to timeout > datagram sockets (AF_UNIX & AF_INET domain) and test code to test > timeout accuracy on these sockets. This is not reasonable. If you want

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

From: Vallish Vaidyeshwara Date: Wed, 23 Aug 2017 00:10:25 + > I am submitting 2 patch series to enable hires timer to timeout > datagram sockets (AF_UNIX & AF_INET domain) and test code to test > timeout accuracy on these sockets. This is not reasonable. If you want high resolution events

[PATCH v4 3/4] mmc: sdhci: enable/disable the clock in sdhci_pltfm_suspend/resume

This commit provides similar cleanups as commit 83eacdfa2529 ("mmc: sdhci: disable the clock in sdhci_pltfm_unregister()") did for unregister hooks. sdhci-brcmstb.c and sdhci-sirf.c implement their own suspend/resume hooks to handle pltfm_host->clk. Move clock handling to sdhci_pltfm.c so that

[PATCH v4 3/4] mmc: sdhci: enable/disable the clock in sdhci_pltfm_suspend/resume

This commit provides similar cleanups as commit 83eacdfa2529 ("mmc: sdhci: disable the clock in sdhci_pltfm_unregister()") did for unregister hooks. sdhci-brcmstb.c and sdhci-sirf.c implement their own suspend/resume hooks to handle pltfm_host->clk. Move clock handling to sdhci_pltfm.c so that

RE: [PATCH] vsock: only load vmci transport on VMware hypervisor by default

> From: Jorgen S. Hansen [mailto:jhan...@vmware.com] > > On Aug 22, 2017, at 11:54 AM, Stefan Hajnoczi > wrote: > > ... > > We *can* by looking at the destination CID. Please take a look at > > drivers/misc/vmw_vmci/vmci_route.c:vmci_route() to see how VMCI > handles > >

RE: [PATCH] vsock: only load vmci transport on VMware hypervisor by default

> From: Jorgen S. Hansen [mailto:jhan...@vmware.com] > > On Aug 22, 2017, at 11:54 AM, Stefan Hajnoczi > wrote: > > ... > > We *can* by looking at the destination CID. Please take a look at > > drivers/misc/vmw_vmci/vmci_route.c:vmci_route() to see how VMCI > handles > > nested virt. > > > > It

RE: [PATCH v3 1/4] ACPI / EC: Cleanup EC GPE mask flag

Hi, > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Subject: Re: [PATCH v3 1/4] ACPI / EC: Cleanup EC GPE mask flag > > On Friday, August 11, 2017 8:36:28 AM CEST Lv Zheng wrote: > > EC_FLAGS_COMMAND_STORM is actually used to mask GPE during IRQ processing. > > This patch cleans it up

RE: [PATCH v3 1/4] ACPI / EC: Cleanup EC GPE mask flag

Hi, > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Subject: Re: [PATCH v3 1/4] ACPI / EC: Cleanup EC GPE mask flag > > On Friday, August 11, 2017 8:36:28 AM CEST Lv Zheng wrote: > > EC_FLAGS_COMMAND_STORM is actually used to mask GPE during IRQ processing. > > This patch cleans it up

[PATCH v4 2/4] mmc: sdhci-pxav2: switch to managed clk and sdhci_pltfm_unregister()

The difference between sdhci_pxav2_remove() and sdhci_pltfm_unregister() is clk_put(). It will go away by using the managed resource clk, then sdhci_pltfm_unregister() can be reused. Also, rename the jump labels to say what the goto does. (Coding style suggested by

[PATCH v4 2/4] mmc: sdhci-pxav2: switch to managed clk and sdhci_pltfm_unregister()

The difference between sdhci_pxav2_remove() and sdhci_pltfm_unregister() is clk_put(). It will go away by using the managed resource clk, then sdhci_pltfm_unregister() can be reused. Also, rename the jump labels to say what the goto does. (Coding style suggested by

[PATCH v4 1/4] mmc: sdhci-cadence: add suspend / resume support

Currently, the probe function initializes the PHY, but PHY settings are lost during the sleep state. Restore the PHY registers when resuming. To facilitate this, split sdhci_cdns_phy_init() into the DT parse part and PHY update part so that the latter can be invoked from the resume hook.

[PATCH v4 1/4] mmc: sdhci-cadence: add suspend / resume support

Currently, the probe function initializes the PHY, but PHY settings are lost during the sleep state. Restore the PHY registers when resuming. To facilitate this, split sdhci_cdns_phy_init() into the DT parse part and PHY update part so that the latter can be invoked from the resume hook.

[PATCH v4 0/4] mmc: sdhci: refactor PM in sdhci-pltfm add support PM for cadence port

[1] implements suspend / resume for sdhci-cadence.c [2] refactor sdhci-pxav2 [3] add clk handling for suspend/resume hooks of sdhci-pltfm. This also cleans up sdhci-brcmstb.c and sdhci-sirf.c [4] export sdhci_pltfm_suspend/resume to reduce code duplication Masahiro Yamada (4): mmc:

[PATCH v4 0/4] mmc: sdhci: refactor PM in sdhci-pltfm add support PM for cadence port

[1] implements suspend / resume for sdhci-cadence.c [2] refactor sdhci-pxav2 [3] add clk handling for suspend/resume hooks of sdhci-pltfm. This also cleans up sdhci-brcmstb.c and sdhci-sirf.c [4] export sdhci_pltfm_suspend/resume to reduce code duplication Masahiro Yamada (4): mmc:

[PATCH v4 4/4] mmc: sdhci-pltfm: export sdhci_pltfm_suspend/resume

This will be useful when drivers want to reuse either suspend or resume callback instead of whole of sdhci_pltfm_pmops. Signed-off-by: Masahiro Yamada --- Changes in v4: None Changes in v3: None Changes in v2: None drivers/mmc/host/sdhci-cadence.c | 20

[PATCH v4 4/4] mmc: sdhci-pltfm: export sdhci_pltfm_suspend/resume

This will be useful when drivers want to reuse either suspend or resume callback instead of whole of sdhci_pltfm_pmops. Signed-off-by: Masahiro Yamada --- Changes in v4: None Changes in v3: None Changes in v2: None drivers/mmc/host/sdhci-cadence.c | 20 +---

ext4 bug fixes for 4.13

The following changes since commit aae4e7a8bc44722fe70d58920a36916b1043195e: Linux 4.13-rc4 (2017-08-06 18:44:49 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable for you to fetch changes up to

ext4 bug fixes for 4.13

The following changes since commit aae4e7a8bc44722fe70d58920a36916b1043195e: Linux 4.13-rc4 (2017-08-06 18:44:49 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable for you to fetch changes up to

Re: [PATCH] drivers: net: wireless: atmel: check memory allocation failure

Himanshu Jha writes: > Check memory allocation failure and return -ENOMEM if failure > occurs. > > Signed-off-by: Himanshu Jha The title prefix is wrong:

Re: [PATCH] drivers: net: wireless: atmel: check memory allocation failure

Himanshu Jha writes: > Check memory allocation failure and return -ENOMEM if failure > occurs. > > Signed-off-by: Himanshu Jha The title prefix is wrong: https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#commit_title_is_wrong -- Kalle Valo

Re: [PATCH v12 7/8] wireless: ipw2200: Replace PCI pool old API

+ linux-wireless Stanislav Yakovlev writes: > On 22 August 2017 at 07:47, Romain Perier wrote: >> The PCI pool API is deprecated. This commit replaces the PCI pool old >> API by the appropriate function with the DMA pool API. >> >>

Re: [PATCH v12 7/8] wireless: ipw2200: Replace PCI pool old API

+ linux-wireless Stanislav Yakovlev writes: > On 22 August 2017 at 07:47, Romain Perier wrote: >> The PCI pool API is deprecated. This commit replaces the PCI pool old >> API by the appropriate function with the DMA pool API. >> >> Signed-off-by: Romain Perier >> Reviewed-by: Peter Senna

Re: [PATCH] actbl1.h: use tab instead of seven spaces as the indentation

On Wed, Aug 23, 2017 at 03:43:33AM +, Zheng, Lv wrote: >Hi, > >> From: linux-acpi-ow...@vger.kernel.org >> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Chao Fan >> Subject: [PATCH] actbl1.h: use tab instead of seven spaces as the indentation >> >> The indentation of these two lines

Re: [PATCH] actbl1.h: use tab instead of seven spaces as the indentation

On Wed, Aug 23, 2017 at 03:43:33AM +, Zheng, Lv wrote: >Hi, > >> From: linux-acpi-ow...@vger.kernel.org >> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Chao Fan >> Subject: [PATCH] actbl1.h: use tab instead of seven spaces as the indentation >> >> The indentation of these two lines

Re: [1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2

2017-08-21 22:17 GMT+09:00 Simon Horman : > On Wed, Aug 16, 2017 at 11:07:27AM +0530, Viresh Kumar wrote: >> The initial idea of creating the cpufreq-dt-platdev.c file was to keep a >> list of platforms that use the "operating-points" (V1) bindings and >> create cpufreq device

Re: [1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2

2017-08-21 22:17 GMT+09:00 Simon Horman : > On Wed, Aug 16, 2017 at 11:07:27AM +0530, Viresh Kumar wrote: >> The initial idea of creating the cpufreq-dt-platdev.c file was to keep a >> list of platforms that use the "operating-points" (V1) bindings and >> create cpufreq device for them only, as we

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

> > WARNING: possible circular locking dependency detected > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted > > > -- > > > fsck.ext4/148 is trying to acquire lock: > > > (>bd_

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

> > WARNING: possible circular locking dependency detected > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted > > > -- > > > fsck.ext4/148 is trying to acquire lock: > > > (>bd_

[PATCH][v3] PM / Hibernate: Feed the wathdog when creating snapshot

There is a problem that when counting the pages for creating the hibernation snapshot will take significant amount of time, especially on system with large memory. Since the counting job is performed with irq disabled, this might lead to NMI lockup. The following warning were found on a system

[PATCH][v3] PM / Hibernate: Feed the wathdog when creating snapshot

There is a problem that when counting the pages for creating the hibernation snapshot will take significant amount of time, especially on system with large memory. Since the counting job is performed with irq disabled, this might lead to NMI lockup. The following warning were found on a system

Re: [PATCH][v2] PM / Hibernate: Feed the wathdog when creating snapshot

On Tue, Aug 22, 2017 at 02:55:39PM +0200, Rafael J. Wysocki wrote: > On Tuesday, August 22, 2017 5:20:02 AM CEST Chen Yu wrote: > > There is a problem that when counting the pages for creating > > the hibernation snapshot will take significant amount of > > time, especially on system with large

Re: [PATCH][v2] PM / Hibernate: Feed the wathdog when creating snapshot

On Tue, Aug 22, 2017 at 02:55:39PM +0200, Rafael J. Wysocki wrote: > On Tuesday, August 22, 2017 5:20:02 AM CEST Chen Yu wrote: > > There is a problem that when counting the pages for creating > > the hibernation snapshot will take significant amount of > > time, especially on system with large

  1   2   3   4   5   6   7   8   9   10   >