[PATCH v3] qrtr: add MODULE_ALIAS macro to smd

Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load when IPCRTR channel is detected. Signed-off-by: Ramon Fried --- V2: Corrected subject line, this is not a part of a patchset. V3: Placed the changelog under the ---. net/qrtr/smd.c | 1 + 1 file

[PATCH v3] qrtr: add MODULE_ALIAS macro to smd

Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load when IPCRTR channel is detected. Signed-off-by: Ramon Fried --- V2: Corrected subject line, this is not a part of a patchset. V3: Placed the changelog under the ---. net/qrtr/smd.c | 1 + 1 file changed, 1 insertion(+)

Re: [BUG] lock_parent() breakage when used from shrink_dentry_list() (was Re: [PATCH v2 6/6] fs/dcache: Avoid remaining try_lock loop in shrink_dentry_list())

On Sat, Feb 24, 2018 at 12:22:48AM +, Al Viro wrote: > On Fri, Feb 23, 2018 at 01:35:52PM -0800, Linus Torvalds wrote: > > > This is too subtle, and your fix to check d_lockref.count < 0 sounds > > wrong to me. If it's really gone, maybe it has been reused and the > > refcount is positive

Re: [BUG] lock_parent() breakage when used from shrink_dentry_list() (was Re: [PATCH v2 6/6] fs/dcache: Avoid remaining try_lock loop in shrink_dentry_list())

On Sat, Feb 24, 2018 at 12:22:48AM +, Al Viro wrote: > On Fri, Feb 23, 2018 at 01:35:52PM -0800, Linus Torvalds wrote: > > > This is too subtle, and your fix to check d_lockref.count < 0 sounds > > wrong to me. If it's really gone, maybe it has been reused and the > > refcount is positive

[PATCH] MAINTAINERS: Add list, tree, and maintainer

MAINTAINERS is out of date for leaking_addresses.pl. There is now a tree on kernel.org for development of this script. We have a second maintainer now, thanks Tycho. Development of this scripts was started on kernel-hardening mailing list so let's keep it there. Update maintainer details; Add

[PATCH] MAINTAINERS: Add list, tree, and maintainer

MAINTAINERS is out of date for leaking_addresses.pl. There is now a tree on kernel.org for development of this script. We have a second maintainer now, thanks Tycho. Development of this scripts was started on kernel-hardening mailing list so let's keep it there. Update maintainer details; Add

Re: [PATCH v2] qrtr: add MODULE_ALIAS macro to smd

Ramon Fried writes: > Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load > when IPCRTR channel is detected. > > Signed-off-by: Ramon Fried > > V2: Corrected subject line, this is not a part of a patchset. > --- >

Re: [PATCH v2] qrtr: add MODULE_ALIAS macro to smd

Ramon Fried writes: > Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load > when IPCRTR channel is detected. > > Signed-off-by: Ramon Fried > > V2: Corrected subject line, this is not a part of a patchset. > --- > net/qrtr/smd.c | 1 + > 1 file changed, 1 insertion(+) The

Consent Proposal

Important details to share with you, kindly email me for info: "zhang...@asia.com" Mr.zhang

Consent Proposal

Important details to share with you, kindly email me for info: "zhang...@asia.com" Mr.zhang

RE: [PATCH v6 11/12] arm64: topology: enable ACPI/PPTT based CPU topology

Hi, > -Original Message- > From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org] > On Behalf Of Xiongfeng Wang > Sent: Saturday, February 24, 2018 8:36 AM > To: Lorenzo Pieralisi ; Jeremy Linton > > Cc:

RE: [PATCH v6 11/12] arm64: topology: enable ACPI/PPTT based CPU topology

Hi, > -Original Message- > From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org] > On Behalf Of Xiongfeng Wang > Sent: Saturday, February 24, 2018 8:36 AM > To: Lorenzo Pieralisi ; Jeremy Linton > > Cc: mark.rutl...@arm.com; jonathan.zh...@cavium.com; >

[PATCH v2] qrtr: add MODULE_ALIAS macro to smd

Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load when IPCRTR channel is detected. Signed-off-by: Ramon Fried V2: Corrected subject line, this is not a part of a patchset. --- net/qrtr/smd.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2] qrtr: add MODULE_ALIAS macro to smd

Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load when IPCRTR channel is detected. Signed-off-by: Ramon Fried V2: Corrected subject line, this is not a part of a patchset. --- net/qrtr/smd.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/qrtr/smd.c

[PATCH 1/6] qrtr: add MODULE_ALIAS macro to smd

Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load when IPCRTR channel is detected. Signed-off-by: Ramon Fried --- net/qrtr/smd.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/qrtr/smd.c b/net/qrtr/smd.c index 50615d5efac1..9cf089b9754e

[PATCH 1/6] qrtr: add MODULE_ALIAS macro to smd

Added MODULE_ALIAS("rpmsg:IPCRTR") to ensure qrtr-smd and qrtr will load when IPCRTR channel is detected. Signed-off-by: Ramon Fried --- net/qrtr/smd.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/qrtr/smd.c b/net/qrtr/smd.c index 50615d5efac1..9cf089b9754e 100644 ---

[PATCH] headers: linux/mutex.h: drop linkage.h

From: Randy Dunlap does not use nor need , so drop that one header file from mutex.h. is currently #included in around 1250 C source files (oops, I didn't count other header files that #include it), making it the 27th most-used header file. Build tested on i386 and

[PATCH] headers: linux/irq.h: drop 5 #included header files

From: Randy Dunlap does not use nor need several of its #included files, so drop those header files from irq.h. is currently #included in around 1135 C source files (oops, I didn't count other header files that #include it), making it the 29th most-used header file.

[PATCH] headers: linux/mutex.h: drop linkage.h

From: Randy Dunlap does not use nor need , so drop that one header file from mutex.h. is currently #included in around 1250 C source files (oops, I didn't count other header files that #include it), making it the 27th most-used header file. Build tested on i386 and x86_64 * (allnoconfig,

[PATCH] headers: linux/irq.h: drop 5 #included header files

From: Randy Dunlap does not use nor need several of its #included files, so drop those header files from irq.h. is currently #included in around 1135 C source files (oops, I didn't count other header files that #include it), making it the 29th most-used header file. Build tested on i386 and

Re: [BUG] arm64: Build error with gcc 6

Hi Masami Hiramatsu, On Sun, Feb 25, 2018 at 11:50:37AM +0900, Masami Hiramatsu wrote: > commit e1a50de37860 ("arm64: cputype: Silence Sparse warnings") > introduces "UL" suffix to a hex number, but it causes a build error with > gcc-6 series. > I've hit below error with 6.2.1 and 6.4.1. Of

Re: [BUG] arm64: Build error with gcc 6

Hi Masami Hiramatsu, On Sun, Feb 25, 2018 at 11:50:37AM +0900, Masami Hiramatsu wrote: > commit e1a50de37860 ("arm64: cputype: Silence Sparse warnings") > introduces "UL" suffix to a hex number, but it causes a build error with > gcc-6 series. > I've hit below error with 6.2.1 and 6.4.1. Of

Re: [PATCH 6/7] lkdtm: crash on overwriting protected pmalloc var

Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2] [cannot apply to next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 6/7] lkdtm: crash on overwriting protected pmalloc var

Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2] [cannot apply to next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 3/7] struct page: add field for vm_struct

On Fri, Feb 23, 2018 at 04:48:03PM +0200, Igor Stoppa wrote: > @@ -1769,6 +1771,9 @@ void *__vmalloc_node_range(unsigned long size, unsigned > long align, > > kmemleak_vmalloc(area, size, gfp_mask); > > + for (i = 0; i < area->nr_pages; i++) > + area->pages[i]->area =

Re: [PATCH 3/7] struct page: add field for vm_struct

On Fri, Feb 23, 2018 at 04:48:03PM +0200, Igor Stoppa wrote: > @@ -1769,6 +1771,9 @@ void *__vmalloc_node_range(unsigned long size, unsigned > long align, > > kmemleak_vmalloc(area, size, gfp_mask); > > + for (i = 0; i < area->nr_pages; i++) > + area->pages[i]->area =

Re: [PATCH 4.15 00/45] 4.15.6-stable review

On Fri, Feb 23, 2018 at 07:28:39PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.6 release. > There are 45 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 1/7] genalloc: track beginning of allocations

Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 4.15 00/45] 4.15.6-stable review

On Fri, Feb 23, 2018 at 07:28:39PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.6 release. > There are 45 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 1/7] genalloc: track beginning of allocations

Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 4.9 000/145] 4.9.84-stable review

On Fri, Feb 23, 2018 at 07:25:06PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.84 release. > There are 145 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.9 000/145] 4.9.84-stable review

On Fri, Feb 23, 2018 at 07:25:06PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.84 release. > There are 145 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

[BUG] arm64: Build error with gcc 6

Hello, commit e1a50de37860 ("arm64: cputype: Silence Sparse warnings") introduces "UL" suffix to a hex number, but it causes a build error with gcc-6 series. I've hit below error with 6.2.1 and 6.4.1. Of course this is resolved by the latest stable gcc-7.2.1. But from the compatibility point of

[BUG] arm64: Build error with gcc 6

Hello, commit e1a50de37860 ("arm64: cputype: Silence Sparse warnings") introduces "UL" suffix to a hex number, but it causes a build error with gcc-6 series. I've hit below error with 6.2.1 and 6.4.1. Of course this is resolved by the latest stable gcc-7.2.1. But from the compatibility point of

Re: [PATCH 4/7] Protectable Memory

Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2] [cannot apply to next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 4/7] Protectable Memory

Hi Igor, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2] [cannot apply to next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

DMA map SG ignores DMA mask or don't report error

Hello, tl;dr: Custom PCIe FPGA board, custom driver: dma_map_sg() and dma_set_mask() do not report any error, the dma addresses are bigger than the useable address space (30 bit). I'm trying to write a direct I/O driver for a custom PCIe FPGA board (for my MSc thesis). I would like to use

DMA map SG ignores DMA mask or don't report error

Hello, tl;dr: Custom PCIe FPGA board, custom driver: dma_map_sg() and dma_set_mask() do not report any error, the dma addresses are bigger than the useable address space (30 bit). I'm trying to write a direct I/O driver for a custom PCIe FPGA board (for my MSc thesis). I would like to use

[PATCH] pwm: sun4i: properly check current state

Correctly extract the prescaler value from CTRL_REG before comparing it to PWM_PRESCAL_MASK. Also, check that both PWM_CLK_GATING and PWM_EN to ensure the PWM is enabled instead of relying on only one of those. Fixes: 93e0dfb2c52f ("pwm: sun4i: Improve hardware read out") Signed-off-by:

[PATCH] pwm: sun4i: properly check current state

Correctly extract the prescaler value from CTRL_REG before comparing it to PWM_PRESCAL_MASK. Also, check that both PWM_CLK_GATING and PWM_EN to ensure the PWM is enabled instead of relying on only one of those. Fixes: 93e0dfb2c52f ("pwm: sun4i: Improve hardware read out") Signed-off-by:

Logitech webcam USB audio breakage during the 4.10 merge window

I have a problem that was previously reported here: https://www.spinics.net/lists/linux-usb/msg156999.html It seems that with the 4.10-rc1 kernel a regression was introduced that makes my Logitech C310 microphone record a distorted ( chipmunk ) sound. With the 4.9.1 kernel it works perfectly.

Logitech webcam USB audio breakage during the 4.10 merge window

I have a problem that was previously reported here: https://www.spinics.net/lists/linux-usb/msg156999.html It seems that with the 4.10-rc1 kernel a regression was introduced that makes my Logitech C310 microphone record a distorted ( chipmunk ) sound. With the 4.9.1 kernel it works perfectly.

Re: [PATCH v0 1/3] livepatch: add sample cumulative patch

Joe, On Fri, Feb 23, 2018 at 1:33 PM, Joe Lawrence wrote: > Add a simple atomic replace / cumulative livepatch example. > > Signed-off-by: Joe Lawrence > --- > samples/livepatch/Makefile | 1 + >

Re: [PATCH v0 1/3] livepatch: add sample cumulative patch

Joe, On Fri, Feb 23, 2018 at 1:33 PM, Joe Lawrence wrote: > Add a simple atomic replace / cumulative livepatch example. > > Signed-off-by: Joe Lawrence > --- > samples/livepatch/Makefile | 1 + > samples/livepatch/livepatch-cumulative.c | 216 > +++

Re: mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML)

Hello Andrew, Michal, On Thu, Feb 22, 2018 at 02:26:30PM +0100, Michal Hocko wrote: > On Thu 22-02-18 14:08:14, Eugeniu Rosca wrote: > > On Thu, Feb 22, 2018 at 01:59:55PM +0100, Michal Hocko wrote: > > > On Thu 22-02-18 11:38:32, Eugeniu Rosca wrote: > > > > Hi Michal, > > > > > > > > Please,

Re: mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML)

Hello Andrew, Michal, On Thu, Feb 22, 2018 at 02:26:30PM +0100, Michal Hocko wrote: > On Thu 22-02-18 14:08:14, Eugeniu Rosca wrote: > > On Thu, Feb 22, 2018 at 01:59:55PM +0100, Michal Hocko wrote: > > > On Thu 22-02-18 11:38:32, Eugeniu Rosca wrote: > > > > Hi Michal, > > > > > > > > Please,

Re: 500 ms delay in time saved into RTC

Hi, On 19/02/2018 at 12:03:28 +0100, Karel Zak wrote: > On Mon, Feb 19, 2018 at 08:11:05AM +0100, Rasmus Villemoes wrote: > > It's because util-linux's hwclock still assumes the world is x86. See > > this comment in the util-linux source code: > > > > /* > > * The Hardware Clock

Re: 500 ms delay in time saved into RTC

Hi, On 19/02/2018 at 12:03:28 +0100, Karel Zak wrote: > On Mon, Feb 19, 2018 at 08:11:05AM +0100, Rasmus Villemoes wrote: > > It's because util-linux's hwclock still assumes the world is x86. See > > this comment in the util-linux source code: > > > > /* > > * The Hardware Clock

Re: [GIT PULL] KVM changes for 4.16-rc3

On Fri, Feb 23, 2018 at 5:46 PM, Paolo Bonzini wrote: > > git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus This has 28 fixes that were committed one hour before you sent this email. I pulled, but I think I'm going to unpull, just because I want an explanation

Re: [GIT PULL] KVM changes for 4.16-rc3

On Fri, Feb 23, 2018 at 5:46 PM, Paolo Bonzini wrote: > > git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus This has 28 fixes that were committed one hour before you sent this email. I pulled, but I think I'm going to unpull, just because I want an explanation of how that could

Re: [PATCH] lib/test_kmod: Fix an integer overflow test

On Sat, Feb 24, 2018 at 10:06:01PM +, Luis R. Rodriguez wrote: > On Sat, Feb 24, 2018 at 11:45:16AM +0300, Dan Carpenter wrote: > > On Sat, Feb 24, 2018 at 02:59:41AM +, Luis R. Rodriguez wrote: > > > On Mon, Jan 22, 2018 at 01:27:54PM +0300, Dan Carpenter wrote: > > > > The main problem

Re: [PATCH] lib/test_kmod: Fix an integer overflow test

On Sat, Feb 24, 2018 at 10:06:01PM +, Luis R. Rodriguez wrote: > On Sat, Feb 24, 2018 at 11:45:16AM +0300, Dan Carpenter wrote: > > On Sat, Feb 24, 2018 at 02:59:41AM +, Luis R. Rodriguez wrote: > > > On Mon, Jan 22, 2018 at 01:27:54PM +0300, Dan Carpenter wrote: > > > > The main problem

[PATCH net 3/4] net/sonic: Clean up and modernize log messages

Add missing printk severity levels by adopting pr_foo() calls for the platform_driver and dev_foo() calls for the nubus_driver. Avoid KERN_CONT usage as per advice from checkpatch. Avoid #ifdef around printk calls. Don't log driver probe messages after calling register_netdev(). Cc: Thomas

[PATCH net 4/4] net/sonic: Replace custom debug logging with netif_* calls

Eliminate duplicated debug code by moving it into the core driver. Don't log the only valid silicon revision number (it's in the source). Cc: Thomas Bogendoerfer Cc: Chris Zankel Tested-by: Stan Johnson Signed-off-by: Finn Thain

[PATCH net 3/4] net/sonic: Clean up and modernize log messages

Add missing printk severity levels by adopting pr_foo() calls for the platform_driver and dev_foo() calls for the nubus_driver. Avoid KERN_CONT usage as per advice from checkpatch. Avoid #ifdef around printk calls. Don't log driver probe messages after calling register_netdev(). Cc: Thomas

[PATCH net 4/4] net/sonic: Replace custom debug logging with netif_* calls

Eliminate duplicated debug code by moving it into the core driver. Don't log the only valid silicon revision number (it's in the source). Cc: Thomas Bogendoerfer Cc: Chris Zankel Tested-by: Stan Johnson Signed-off-by: Finn Thain --- Only the sonic.[ch] and macsonic.c changes have been tested.

[PATCH net 1/4] net/macsonic: Convert to nubus_driver

This resolves an old issue preventing any NuBus SONIC NICs from working in a Mac with an on-board SONIC device. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/net/ethernet/natsemi/macsonic.c | 173 ++-- 1

[PATCH net 0/4] Fixes, cleanup and modernization for SONIC ethernet drivers

Changes since v4 of combined patch series: - Removed redundant and non-portable MACH_IS_MAC tests. - Omitted patches unrelated to SONIC drivers. - Dropped changes to the 'version_printed' logic and debug message text. Finn Thain (4): net/macsonic: Convert to nubus_driver net/macsonic: Drop

[PATCH net 2/4] net/macsonic: Drop redundant MACH_IS_MAC test

The MACH_IS_MAC test is redundant here because the platform device won't get registered unless MACH_IS_MAC. Cc: Geert Uytterhoeven Signed-off-by: Finn Thain --- drivers/net/ethernet/natsemi/macsonic.c | 3 --- 1 file changed, 3 deletions(-)

[PATCH net 1/4] net/macsonic: Convert to nubus_driver

This resolves an old issue preventing any NuBus SONIC NICs from working in a Mac with an on-board SONIC device. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/net/ethernet/natsemi/macsonic.c | 173 ++-- 1 file changed, 119 insertions(+), 54

[PATCH net 0/4] Fixes, cleanup and modernization for SONIC ethernet drivers

Changes since v4 of combined patch series: - Removed redundant and non-portable MACH_IS_MAC tests. - Omitted patches unrelated to SONIC drivers. - Dropped changes to the 'version_printed' logic and debug message text. Finn Thain (4): net/macsonic: Convert to nubus_driver net/macsonic: Drop

[PATCH net 2/4] net/macsonic: Drop redundant MACH_IS_MAC test

The MACH_IS_MAC test is redundant here because the platform device won't get registered unless MACH_IS_MAC. Cc: Geert Uytterhoeven Signed-off-by: Finn Thain --- drivers/net/ethernet/natsemi/macsonic.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/net/ethernet/natsemi/macsonic.c

Re: [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver

On 23/02/2018 16:26, Vincent Guittot wrote: > Hi Daniel, > > On 21 February 2018 at 16:29, Daniel Lezcano > wrote: >> + >> +/** >> + * struct cpuidle_cooling_device - data for the idle cooling device >> + * @cdev: a pointer to a struct thermal_cooling_device >> + *

Re: [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver

On 23/02/2018 16:26, Vincent Guittot wrote: > Hi Daniel, > > On 21 February 2018 at 16:29, Daniel Lezcano > wrote: >> + >> +/** >> + * struct cpuidle_cooling_device - data for the idle cooling device >> + * @cdev: a pointer to a struct thermal_cooling_device >> + * @cpumask: a cpumask

Re: [PATCH V2 7/7] cpuidle/drivers/cpuidle-arm: Register the cooling device

On 24/02/2018 03:50, Wangtao (Kevin, Kirin) wrote: > > > On 2018/2/21 23:29, Daniel Lezcano wrote: >> Register the ARM generic cpuidle driver as a cooling device. >> >> Signed-off-by: Daniel Lezcano >> --- >>   drivers/cpuidle/cpuidle-arm.c | 5 + >>   1 file

Re: [PATCH V2 7/7] cpuidle/drivers/cpuidle-arm: Register the cooling device

On 24/02/2018 03:50, Wangtao (Kevin, Kirin) wrote: > > > On 2018/2/21 23:29, Daniel Lezcano wrote: >> Register the ARM generic cpuidle driver as a cooling device. >> >> Signed-off-by: Daniel Lezcano >> --- >>   drivers/cpuidle/cpuidle-arm.c | 5 + >>   1 file changed, 5 insertions(+) >> >>

Re: [RFC tip/locking/lockdep v5 16/17] lockdep: Documention for recursive read lock detection reasoning

On Thu, Feb 22, 2018 at 03:09:03PM +0800, Boqun Feng wrote: > As now we support recursive read lock deadlock detection, add related > explanation in the Documentation/lockdep/lockdep-desgin.txt: > > * Definition of recursive read locks, non-recursive locks, strong > dependency path and

Re: [RFC tip/locking/lockdep v5 16/17] lockdep: Documention for recursive read lock detection reasoning

On Thu, Feb 22, 2018 at 03:09:03PM +0800, Boqun Feng wrote: > As now we support recursive read lock deadlock detection, add related > explanation in the Documentation/lockdep/lockdep-desgin.txt: > > * Definition of recursive read locks, non-recursive locks, strong > dependency path and

Re: [PATCH] tools/memory-model: update: remove rb-dep, smp_read_barrier_depends, and lockless_dereference

On 2018/02/24 10:08:14 -0800, Paul E. McKenney wrote: > On Sat, Feb 24, 2018 at 11:49:20AM -0500, Alan Stern wrote: >> On Sat, 24 Feb 2018, Andrea Parri wrote: >> >>> On Fri, Feb 23, 2018 at 07:30:13PM -0800, Paul E. McKenney wrote: On Sat, Feb 24, 2018 at 12:22:24PM +0900, Akira Yokosawa

Re: [PATCH] tools/memory-model: update: remove rb-dep, smp_read_barrier_depends, and lockless_dereference

On 2018/02/24 10:08:14 -0800, Paul E. McKenney wrote: > On Sat, Feb 24, 2018 at 11:49:20AM -0500, Alan Stern wrote: >> On Sat, 24 Feb 2018, Andrea Parri wrote: >> >>> On Fri, Feb 23, 2018 at 07:30:13PM -0800, Paul E. McKenney wrote: On Sat, Feb 24, 2018 at 12:22:24PM +0900, Akira Yokosawa

[PATCH] i2c: xiic: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 36ecbcab84d0 ("i2c: xiic: Implement power management") Signed-off-by: Tobias Jordan --- This is one of a

[PATCH] i2c: xiic: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 36ecbcab84d0 ("i2c: xiic: Implement power management") Signed-off-by: Tobias Jordan --- This is one of a number of patches for problems

[PATCH] i2c: tegra: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the related error branches. Fixes: 1f50ad2c86cd ("i2c: tegra: Add runtime power-management support") Signed-off-by: Tobias Jordan ---

[PATCH] i2c: tegra: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the related error branches. Fixes: 1f50ad2c86cd ("i2c: tegra: Add runtime power-management support") Signed-off-by: Tobias Jordan --- This is one of a number of

[PATCH] i2c: sprd: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the related error branches. Fixes: 8b9ec0719834 ("i2c: Add Spreadtrum I2C controller driver") Signed-off-by: Tobias Jordan --- This is

[PATCH] i2c: sprd: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the related error branches. Fixes: 8b9ec0719834 ("i2c: Add Spreadtrum I2C controller driver") Signed-off-by: Tobias Jordan --- This is one of a number of patches for

[PATCH] i2c: imx-lpi2c: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 13d6eb20fc79 ("i2c: imx-lpi2c: add runtime pm support") Signed-off-by: Tobias Jordan --- This is one of a

[PATCH] i2c: imx-lpi2c: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 13d6eb20fc79 ("i2c: imx-lpi2c: add runtime pm support") Signed-off-by: Tobias Jordan --- This is one of a number of patches for problems

[PATCH] i2c: img-scb: fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 93222bd9b966 ("i2c: img-scb: Add runtime PM") Signed-off-by: Tobias Jordan --- This is one of a number of

[PATCH] i2c: imx: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the related error branches. Fixes: 588eb93ea49f ("i2c: imx: add runtime pm support to improve the performance") Signed-off-by: Tobias Jordan

[PATCH] i2c: img-scb: fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 93222bd9b966 ("i2c: img-scb: Add runtime PM") Signed-off-by: Tobias Jordan --- This is one of a number of patches for problems found using

[PATCH] i2c: imx: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the related error branches. Fixes: 588eb93ea49f ("i2c: imx: add runtime pm support to improve the performance") Signed-off-by: Tobias Jordan --- In i2c_imx_xfer(),

[PATCH] i2c: cadence: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 7fa32329ca03 ("i2c: cadence: Move to sensible power management") Signed-off-by: Tobias Jordan --- This is one

[PATCH] i2c: cadence: Fix PM device usage count

pm_runtime_get_sync() increases the device's usage count even when reporting an error, so add a call to pm_runtime_put_noidle() in the error branch. Fixes: 7fa32329ca03 ("i2c: cadence: Move to sensible power management") Signed-off-by: Tobias Jordan --- This is one of a number of patches for

Re: [PATCH] scsi: lpfc: use memcpy_toio instead of writeq

About to post a patch to fix. Rather than fidgeting with the copy routine, I want to go back to what we originally proposed - writeq() on 64bit, writel() on 32-bit. -- james On 2/23/2018 1:02 PM, Arnd Bergmann wrote: On Fri, Feb 23, 2018 at 4:36 PM, Arnd Bergmann wrote: @@

Re: [PATCH] scsi: lpfc: use memcpy_toio instead of writeq

About to post a patch to fix. Rather than fidgeting with the copy routine, I want to go back to what we originally proposed - writeq() on 64bit, writel() on 32-bit. -- james On 2/23/2018 1:02 PM, Arnd Bergmann wrote: On Fri, Feb 23, 2018 at 4:36 PM, Arnd Bergmann wrote: @@ -138,12 +137,10

[PATCH V1 1/3] x86/efi: Call efi_delete_dummy_variable() during efi subsystem initialization

From: Sai Praneeth Invoking efi_runtime_services() through efi_workqueue means all accesses to efi_runtime_services() should be done after efi_rts_wq has been created. efi_delete_dummy_variable() calls set_variable(), hence efi_delete_dummy_variable() should be

[PATCH V1 1/3] x86/efi: Call efi_delete_dummy_variable() during efi subsystem initialization

From: Sai Praneeth Invoking efi_runtime_services() through efi_workqueue means all accesses to efi_runtime_services() should be done after efi_rts_wq has been created. efi_delete_dummy_variable() calls set_variable(), hence efi_delete_dummy_variable() should be called after efi_rts_wq has been

[PATCH V1 3/3] efi: Use efi_rts_workqueue to invoke EFI Runtime Services

From: Sai Praneeth Presently, efi_runtime_services() are executed by firmware in process context. To execute efi_runtime_service(), kernel switches the page directory from swapper_pgd to efi_pgd. However, efi_pgd doesn't have any user space mappings. A potential

[PATCH V1 3/3] efi: Use efi_rts_workqueue to invoke EFI Runtime Services

From: Sai Praneeth Presently, efi_runtime_services() are executed by firmware in process context. To execute efi_runtime_service(), kernel switches the page directory from swapper_pgd to efi_pgd. However, efi_pgd doesn't have any user space mappings. A potential issue could be, for instance, an

[PATCH V1 2/3] efi: Introduce efi_rts_workqueue and necessary infrastructure to invoke all efi_runtime_services()

From: Sai Praneeth When a process requests the kernel to execute any efi_runtime_service(), the requested efi_runtime_service (represented as an identifier) and its arguments are packed into a struct named efi_runtime_work and queued onto work queue named

[PATCH V1 2/3] efi: Introduce efi_rts_workqueue and necessary infrastructure to invoke all efi_runtime_services()

From: Sai Praneeth When a process requests the kernel to execute any efi_runtime_service(), the requested efi_runtime_service (represented as an identifier) and its arguments are packed into a struct named efi_runtime_work and queued onto work queue named efi_rts_wq. The caller then waits until

[PATCH V1 0/3] Use efi_rts_workqueue to invoke EFI Runtime Services

From: Sai Praneeth This patch set is an outcome of the discussion at https://lkml.org/lkml/2017/8/21/607 Presently, efi_runtime_services() are executed by firmware in process context. To execute efi_runtime_service(), kernel switches the page directory from

[PATCH V1 0/3] Use efi_rts_workqueue to invoke EFI Runtime Services

From: Sai Praneeth This patch set is an outcome of the discussion at https://lkml.org/lkml/2017/8/21/607 Presently, efi_runtime_services() are executed by firmware in process context. To execute efi_runtime_service(), kernel switches the page directory from swapper_pgd to efi_pgd. However,

[PATCH 12/15] drm/sun4i: Allow building on arm64

64-bit ARM SoCs from Allwinner have DE2/TCON/HDMI periphery which is compatible to 32-bit SoCs, so allow building DRM driver for arm64 architecture. Signed-off-by: Jernej Skrabec --- drivers/gpu/drm/sun4i/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 12/15] drm/sun4i: Allow building on arm64

64-bit ARM SoCs from Allwinner have DE2/TCON/HDMI periphery which is compatible to 32-bit SoCs, so allow building DRM driver for arm64 architecture. Signed-off-by: Jernej Skrabec --- drivers/gpu/drm/sun4i/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 02/15] clk: sunxi-ng: h3: h5: Add minimal rate for video PLL

Although user manuals for H3 and H5 SoCs state that minimal rate supported by video PLL is around 30 MHz, it seems that in reality minimal rate is around 192 MHz. Experiments showed that any rate below 96 MHz doesn't produce any video output at all. Even at this frequency, stable output depends

[PATCH 02/15] clk: sunxi-ng: h3: h5: Add minimal rate for video PLL

Although user manuals for H3 and H5 SoCs state that minimal rate supported by video PLL is around 30 MHz, it seems that in reality minimal rate is around 192 MHz. Experiments showed that any rate below 96 MHz doesn't produce any video output at all. Even at this frequency, stable output depends

Re: [PATCH] lib/test_kmod: Fix an integer overflow test

On Sat, Feb 24, 2018 at 11:45:16AM +0300, Dan Carpenter wrote: > On Sat, Feb 24, 2018 at 02:59:41AM +, Luis R. Rodriguez wrote: > > On Mon, Jan 22, 2018 at 01:27:54PM +0300, Dan Carpenter wrote: > > > The main problem is that the parentheses are in the wrong place and the > > > unlikely() call

Re: [PATCH] lib/test_kmod: Fix an integer overflow test

On Sat, Feb 24, 2018 at 11:45:16AM +0300, Dan Carpenter wrote: > On Sat, Feb 24, 2018 at 02:59:41AM +, Luis R. Rodriguez wrote: > > On Mon, Jan 22, 2018 at 01:27:54PM +0300, Dan Carpenter wrote: > > > The main problem is that the parentheses are in the wrong place and the > > > unlikely() call

  1   2   3   4   >