Re: [PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

On 03/02/2017 10:45 PM, Arnd Bergmann wrote: > On Thu, Mar 2, 2017 at 8:00 PM, Christian Borntraeger > wrote: >> On 03/02/2017 06:55 PM, Arnd Bergmann wrote: >>> On Thu, Mar 2, 2017 at 5:51 PM, Christian Borntraeger >>> wrote: On 03/02/2017

Re: [PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

On 03/02/2017 10:45 PM, Arnd Bergmann wrote: > On Thu, Mar 2, 2017 at 8:00 PM, Christian Borntraeger > wrote: >> On 03/02/2017 06:55 PM, Arnd Bergmann wrote: >>> On Thu, Mar 2, 2017 at 5:51 PM, Christian Borntraeger >>> wrote: On 03/02/2017 05:38 PM, Arnd Bergmann wrote: > > This

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On Thu 02-03-17 13:44:32, Laura Abbott wrote: > Hi, > > There's been some recent discussions[1] about Ion-like frameworks. There's > apparently interest in just keeping Ion since it works reasonablly well. > This series does what should be the final clean ups for it to possibly be > moved out of

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On Thu 02-03-17 13:44:32, Laura Abbott wrote: > Hi, > > There's been some recent discussions[1] about Ion-like frameworks. There's > apparently interest in just keeping Ion since it works reasonablly well. > This series does what should be the final clean ups for it to possibly be > moved out of

Re: [PATCH v2 6/9] kasan: improve slab object description

On 03/02/2017 04:48 PM, Andrey Konovalov wrote: > Changes slab object description from: > > Object at 880068388540, in cache kmalloc-128 size: 128 > > to: > > The buggy address belongs to the object at 880068388540 > which belongs to the cache kmalloc-128 of size 128 > The buggy

Re: [PATCH v2 6/9] kasan: improve slab object description

On 03/02/2017 04:48 PM, Andrey Konovalov wrote: > Changes slab object description from: > > Object at 880068388540, in cache kmalloc-128 size: 128 > > to: > > The buggy address belongs to the object at 880068388540 > which belongs to the cache kmalloc-128 of size 128 > The buggy

Re: [PATCH v4 08/19] scsi: be2iscsi: Replace PCI pool old API

On 3/1/2017 6:55 PM, Romain Perier wrote: The PCI pool API is deprecated. This commits replaces the PCI pool old Commit. API by the appropriated function with the DMA pool API. Appropriate perhaps? Signed-off-by: Romain Perier Acked-by: Peter Senna

Re: [PATCH v4 08/19] scsi: be2iscsi: Replace PCI pool old API

On 3/1/2017 6:55 PM, Romain Perier wrote: The PCI pool API is deprecated. This commits replaces the PCI pool old Commit. API by the appropriated function with the DMA pool API. Appropriate perhaps? Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter

Re: [PATCH] drm/arcpgu: use .mode_fixup instead of .atomic_check

Hi Daniel, On Thu, 2017-03-02 at 20:54 +0100, Daniel Vetter wrote: > On Thu, Mar 02, 2017 at 08:27:54PM +0300, Alexey Brodkin wrote: > > > > Since we cannot always generate exactly requested pixel clock > > there's not much sense in checking requested_clock == clk_round_rate(). > > In that case

Re: [PATCH] drm/arcpgu: use .mode_fixup instead of .atomic_check

Hi Daniel, On Thu, 2017-03-02 at 20:54 +0100, Daniel Vetter wrote: > On Thu, Mar 02, 2017 at 08:27:54PM +0300, Alexey Brodkin wrote: > > > > Since we cannot always generate exactly requested pixel clock > > there's not much sense in checking requested_clock == clk_round_rate(). > > In that case

[PATCH v3 3/3] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support by adding hvclock_page VVAR. Signed-off-by: Vitaly Kuznetsov --- arch/x86/entry/vdso/vclock_gettime.c | 24

Re: net/kcm: use-after-free in kcm_wq

On Fri, Mar 3, 2017 at 11:09 AM, Dmitry Vyukov wrote: > Hello, > > I am getting the following use-after-free reports while running > syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. Seems > that work items are not properly cancelled. > >

[PATCH v3 3/3] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support by adding hvclock_page VVAR. Signed-off-by: Vitaly Kuznetsov --- arch/x86/entry/vdso/vclock_gettime.c | 24

Re: net/kcm: use-after-free in kcm_wq

On Fri, Mar 3, 2017 at 11:09 AM, Dmitry Vyukov wrote: > Hello, > > I am getting the following use-after-free reports while running > syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. Seems > that work items are not properly cancelled. > >

[PATCH v3 0/3] x86/vdso: Add Hyper-V TSC page clocksource support

Hi, merge window is about to close so I hope it's OK to make another try here. Changes since v2: - Add explicit READ_ONCE() to not rely on 'volatile' [Andy Lutomirski] - rdtsc() -> rdtsc_ordered() [Andy Lutomirski] - virt_rmb() -> smp_rmb() [Thomas Gleixner, Andy Lutomirski] Thomas, Andy, it

[PATCH v3 0/3] x86/vdso: Add Hyper-V TSC page clocksource support

Hi, merge window is about to close so I hope it's OK to make another try here. Changes since v2: - Add explicit READ_ONCE() to not rely on 'volatile' [Andy Lutomirski] - rdtsc() -> rdtsc_ordered() [Andy Lutomirski] - virt_rmb() -> smp_rmb() [Thomas Gleixner, Andy Lutomirski] Thomas, Andy, it

Re: [PATCH v4 1/3] x86: Introduce a new constant KERNEL_MAPPING_SIZE

On 03/03/17 at 08:52pm, Baoquan He wrote: > On 03/03/17 at 01:16pm, Borislav Petkov wrote: > > On Fri, Mar 03, 2017 at 08:06:16PM +0800, Baoquan He wrote: > > > OK, I am trying to make things clearer, seems I failed. I thought kernel > > > iamge size is only allowed to be 512M at most, but can be

Re: [PATCH v4 1/3] x86: Introduce a new constant KERNEL_MAPPING_SIZE

On 03/03/17 at 08:52pm, Baoquan He wrote: > On 03/03/17 at 01:16pm, Borislav Petkov wrote: > > On Fri, Mar 03, 2017 at 08:06:16PM +0800, Baoquan He wrote: > > > OK, I am trying to make things clearer, seems I failed. I thought kernel > > > iamge size is only allowed to be 512M at most, but can be

[PATCH] HID: hid-multitouch: change for touch height/width

From: HungNien Chen This change is from Jonathan Clarke and have been discussed in previous thread(2017/01/24). Just doing a slight change in quirk name from Benjamin's comment. Signed-off-by: HungNien Chen --- drivers/hid/hid-multitouch.c |

[PATCH v3 1/3] x86/hyperv: implement hv_get_tsc_page()

To use Hyper-V TSC page clocksource from vDSO we need to make tsc_pg available. Implement hv_get_tsc_page() and add CONFIG_HYPERV_TSCPAGE to make #ifdef-s simple. Signed-off-by: Vitaly Kuznetsov --- arch/x86/hyperv/hv_init.c | 9 +++--

[PATCH] HID: hid-multitouch: change for touch height/width

From: HungNien Chen This change is from Jonathan Clarke and have been discussed in previous thread(2017/01/24). Just doing a slight change in quirk name from Benjamin's comment. Signed-off-by: HungNien Chen --- drivers/hid/hid-multitouch.c | 18 ++ 1 file changed, 14

[PATCH v3 1/3] x86/hyperv: implement hv_get_tsc_page()

To use Hyper-V TSC page clocksource from vDSO we need to make tsc_pg available. Implement hv_get_tsc_page() and add CONFIG_HYPERV_TSCPAGE to make #ifdef-s simple. Signed-off-by: Vitaly Kuznetsov --- arch/x86/hyperv/hv_init.c | 9 +++-- arch/x86/include/asm/mshyperv.h | 8

[PATCH v3 0/5] Fixed compilation error

Fixed compilation warning in lustre/lustre/llite/range_lock.c simran singhal (5): staging: nvec: Remove unnecessary cast on void pointer staging: lustre: Remove unnecessary cast on void pointer staging: lustre: lustre: Remove unnecessary cast on void pointer staging: rts5208: Remove

[PATCH] s390: scsi, use setup_timer instead of init_timer

From: Lukáš Korenčik Use inicialization with setup_timer function instead of using init_timer function and data fields. It improves readability. Signed-off-by: Lukáš Korenčik Signed-off-by: Jiri Slaby Cc: Steffen Maier

[PATCH] s390: scsi, use setup_timer instead of init_timer

From: Lukáš Korenčik Use inicialization with setup_timer function instead of using init_timer function and data fields. It improves readability. Signed-off-by: Lukáš Korenčik Signed-off-by: Jiri Slaby Cc: Steffen Maier Cc: Martin Schwidefsky Cc: Heiko Carstens Cc: ---

[PATCH v3 0/5] Fixed compilation error

Fixed compilation warning in lustre/lustre/llite/range_lock.c simran singhal (5): staging: nvec: Remove unnecessary cast on void pointer staging: lustre: Remove unnecessary cast on void pointer staging: lustre: lustre: Remove unnecessary cast on void pointer staging: rts5208: Remove

[PATCH v3 2/3] x86/hyperv: move TSC reading method to asm/mshyperv.h

As a preparation to making Hyper-V TSC page suitable for vDSO move the TSC page reading logic to asm/mshyperv.h. While on it, do the following - Document the reading algorithm. - Simplify the code a bit. - Add explicit READ_ONCE() to not rely on 'volatile'. - Add explicit barriers to prevent

[PATCH v3 2/3] x86/hyperv: move TSC reading method to asm/mshyperv.h

As a preparation to making Hyper-V TSC page suitable for vDSO move the TSC page reading logic to asm/mshyperv.h. While on it, do the following - Document the reading algorithm. - Simplify the code a bit. - Add explicit READ_ONCE() to not rely on 'volatile'. - Add explicit barriers to prevent

Re: [PATCH v2] clk/axs10x: introduce AXS10X pll driver

Hi Michael, Stephen, On Tue, 2017-02-21 at 16:11 +0300, Vlad Zakharov wrote: > AXS10X boards manages it's clocks using various PLLs. These PLL has same > dividers and corresponding control registers mapped to different addresses. > So we add one common driver for such PLLs. > > Each PLL on

Re: [PATCH v2] clk/axs10x: introduce AXS10X pll driver

Hi Michael, Stephen, On Tue, 2017-02-21 at 16:11 +0300, Vlad Zakharov wrote: > AXS10X boards manages it's clocks using various PLLs. These PLL has same > dividers and corresponding control registers mapped to different addresses. > So we add one common driver for such PLLs. > > Each PLL on

Re: [PATCH 2/2] mm: use is_migrate_isolate_page() to simplify the code

On Fri 03-03-17 19:12:49, Xishi Qiu wrote: > Use is_migrate_isolate_page() to simplify the code, no functional changes. > > Signed-off-by: Xishi Qiu Acked-by: Michal Hocko > --- > mm/page_isolation.c | 6 +++--- > 1 file changed, 3 insertions(+), 3

Re: [PATCH 2/2] mm: use is_migrate_isolate_page() to simplify the code

On Fri 03-03-17 19:12:49, Xishi Qiu wrote: > Use is_migrate_isolate_page() to simplify the code, no functional changes. > > Signed-off-by: Xishi Qiu Acked-by: Michal Hocko > --- > mm/page_isolation.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git

Re: [PATCH 2/6] cpufreq: schedutil: ignore the sugov kthread for frequencies selections

On 03-Mar 10:49, Viresh Kumar wrote: > On 02-03-17, 15:45, Patrick Bellasi wrote: > > In system where multiple CPUs shares the same frequency domain a small > > workload on a CPU can still be subject frequency spikes, generated by > > the activation of the sugov's kthread. > > > > Since the sugov

Re: [PATCH 2/6] cpufreq: schedutil: ignore the sugov kthread for frequencies selections

On 03-Mar 10:49, Viresh Kumar wrote: > On 02-03-17, 15:45, Patrick Bellasi wrote: > > In system where multiple CPUs shares the same frequency domain a small > > workload on a CPU can still be subject frequency spikes, generated by > > the activation of the sugov's kthread. > > > > Since the sugov

Re: [PATCH v2 1/9] kasan: introduce helper functions for determining bug type

On 03/02/2017 04:48 PM, Andrey Konovalov wrote: > Introduce get_shadow_bug_type() function, which determines bug type > based on the shadow value for a particular kernel address. > Introduce get_wild_bug_type() function, which determines bug type > for addresses which don't have a corresponding

Re: [PATCH v2 1/9] kasan: introduce helper functions for determining bug type

On 03/02/2017 04:48 PM, Andrey Konovalov wrote: > Introduce get_shadow_bug_type() function, which determines bug type > based on the shadow value for a particular kernel address. > Introduce get_wild_bug_type() function, which determines bug type > for addresses which don't have a corresponding

Re: [PATCH 0/3] powerpc/mm: page fault handler cleaning

Laurent Dufour writes: > Kindly ping... On my list for 4.12, but still dealing with the mess that is 4.11. Will review it in the next few weeks, unless someone else beats me to it ... ;) cheers

Re: [PATCH 0/3] powerpc/mm: page fault handler cleaning

Laurent Dufour writes: > Kindly ping... On my list for 4.12, but still dealing with the mess that is 4.11. Will review it in the next few weeks, unless someone else beats me to it ... ;) cheers

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 13:37:44 +0100 Boris Brezillon wrote: > On Fri, 3 Mar 2017 13:17:05 +0100 > Alban wrote: > > > On Thu, 2 Mar 2017 21:22:20 +0100 > > Boris Brezillon wrote: > > > > > On Thu, 2 Mar

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 13:37:44 +0100 Boris Brezillon wrote: > On Fri, 3 Mar 2017 13:17:05 +0100 > Alban wrote: > > > On Thu, 2 Mar 2017 21:22:20 +0100 > > Boris Brezillon wrote: > > > > > On Thu, 2 Mar 2017 20:50:21 +0100 > > > Alban wrote: > > > > > > > Add the binding to expose MTD

Re: [RFC PATCH 2/2] mtd: devices: m25p80: Enable spi-nor bounce buffer support

On Thu, Mar 02, 2017 at 08:49:00PM +0100, Boris Brezillon wrote: > 1/ for big transfers, dynamically allocating a bounce buffer on demand >(and freeing it after the DMA operation) might fail, or might induce >some latency, especially when the system is under high mem pressure. >

Re: [RFC PATCH 2/2] mtd: devices: m25p80: Enable spi-nor bounce buffer support

On Thu, Mar 02, 2017 at 08:49:00PM +0100, Boris Brezillon wrote: > 1/ for big transfers, dynamically allocating a bounce buffer on demand >(and freeing it after the DMA operation) might fail, or might induce >some latency, especially when the system is under high mem pressure. >

[PATCH v3 5/5] staging: rtl8712: Remove unnecessary cast on void pointer

The following Coccinelle script was used to detect this: @r@ expression x; void* e; type T; identifier f; @@ ( *((T *)e) | ((T *)x)[...] | ((T*)x)->f | - (T*) e ) Signed-off-by: simran singhal --- drivers/staging/rtl8712/rtl8712_recv.c | 11 +-- 1 file

[PATCH v3 5/5] staging: rtl8712: Remove unnecessary cast on void pointer

The following Coccinelle script was used to detect this: @r@ expression x; void* e; type T; identifier f; @@ ( *((T *)e) | ((T *)x)[...] | ((T*)x)->f | - (T*) e ) Signed-off-by: simran singhal --- drivers/staging/rtl8712/rtl8712_recv.c | 11 +-- 1 file changed, 5 insertions(+),

[PATCH] clk: imx: correct uart4_serial clock name in driver for i.MX6UL

Signed-off-by: Robin van der Gracht --- drivers/clk/imx/clk-imx6ul.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/imx/clk-imx6ul.c b/drivers/clk/imx/clk-imx6ul.c index 0f1f17a..4dcd107 100644 --- a/drivers/clk/imx/clk-imx6ul.c +++

[PATCH] clk: imx: correct uart4_serial clock name in driver for i.MX6UL

Signed-off-by: Robin van der Gracht --- drivers/clk/imx/clk-imx6ul.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/imx/clk-imx6ul.c b/drivers/clk/imx/clk-imx6ul.c index 0f1f17a..4dcd107 100644 --- a/drivers/clk/imx/clk-imx6ul.c +++ b/drivers/clk/imx/clk-imx6ul.c

Re: [PATCH] netfilter: nf_conntrack_sip: fix wrong memory initialisation

On Wed, Mar 01, 2017 at 03:33:26PM +0100, Christophe Leroy wrote: > In commit 82de0be6862cd ("netfilter: Add helper array > register/unregister functions"), > struct nf_conntrack_helper sip[MAX_PORTS][4] was changed to > sip[MAX_PORTS * 4], so the memory init should have been changed to >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

On Thu, 2 Mar 2017, Thomas Gleixner wrote: > On Wed, 1 Mar 2017, Thomas Gleixner wrote: > > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > >

Re: [PATCH] netfilter: nf_conntrack_sip: fix wrong memory initialisation

On Wed, Mar 01, 2017 at 03:33:26PM +0100, Christophe Leroy wrote: > In commit 82de0be6862cd ("netfilter: Add helper array > register/unregister functions"), > struct nf_conntrack_helper sip[MAX_PORTS][4] was changed to > sip[MAX_PORTS * 4], so the memory init should have been changed to >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

On Thu, 2 Mar 2017, Thomas Gleixner wrote: > On Wed, 1 Mar 2017, Thomas Gleixner wrote: > > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > >

Re: [PATCH v2 2/2] drm: bridge: Move HPD handling to PHY operations

Hi Jose, On Friday 03 Mar 2017 10:05:36 Jose Abreu wrote: > On 03-03-2017 09:07, Neil Armstrong wrote: > > The problem is that the HPD/RxSense is tied to this phy_mask and glued > > into the dw-hdmi driver. > > > > The *real* solution would be to completely separate the HPD/RxSense irq > >

Re: [PATCH v2 2/2] drm: bridge: Move HPD handling to PHY operations

Hi Jose, On Friday 03 Mar 2017 10:05:36 Jose Abreu wrote: > On 03-03-2017 09:07, Neil Armstrong wrote: > > The problem is that the HPD/RxSense is tied to this phy_mask and glued > > into the dw-hdmi driver. > > > > The *real* solution would be to completely separate the HPD/RxSense irq > >

Re: [RFC 11/11] mm: remove SWAP_[SUCCESS|AGAIN|FAIL]

On 03/02/2017 12:09 PM, Minchan Kim wrote: > There is no user for it. Remove it. Last patches in the series prepared ground for this removal. The entire series looks pretty straight forward. As it does not change any functionality, wondering what kind of tests this should go through to look for

Re: [RFC 11/11] mm: remove SWAP_[SUCCESS|AGAIN|FAIL]

On 03/02/2017 12:09 PM, Minchan Kim wrote: > There is no user for it. Remove it. Last patches in the series prepared ground for this removal. The entire series looks pretty straight forward. As it does not change any functionality, wondering what kind of tests this should go through to look for

Re: [PATCH 00/26] bring back stack frame warning with KASAN

On Fri, Mar 3, 2017 at 1:25 PM, Alexander Potapenko wrote: > On Thu, Mar 2, 2017 at 5:38 PM, Arnd Bergmann wrote: >> It took a long while to get this done, but I'm finally ready >> to send the first half of the KASAN stack size patches that >> I did in response

Re: XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1.

On Fri, Mar 03, 2017 at 04:36:18AM -0600, Nathan Royce wrote: > I do have ECB selected as well: > DM_CRYPT=y > CRYPTO_ECB=y > CRYPTO_XTS=y > > name : ecb(aes) > driver : ecb-aes-s5p > module : kernel > priority : 100 > refcnt : 1 > selftest : passed > internal

Re: [PATCH 00/26] bring back stack frame warning with KASAN

On Fri, Mar 3, 2017 at 1:25 PM, Alexander Potapenko wrote: > On Thu, Mar 2, 2017 at 5:38 PM, Arnd Bergmann wrote: >> It took a long while to get this done, but I'm finally ready >> to send the first half of the KASAN stack size patches that >> I did in response to the kernelci.org warnings. >>

Re: XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1.

On Fri, Mar 03, 2017 at 04:36:18AM -0600, Nathan Royce wrote: > I do have ECB selected as well: > DM_CRYPT=y > CRYPTO_ECB=y > CRYPTO_XTS=y > > name : ecb(aes) > driver : ecb-aes-s5p > module : kernel > priority : 100 > refcnt : 1 > selftest : passed > internal

[PATCH 12/17] fs, btrfs: convert scrub_recover.refs from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 12/17] fs, btrfs: convert scrub_recover.refs from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by: Hans Liljestrand

Re: [PATCH 3/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks

On 03-Mar 14:01, Viresh Kumar wrote: > On 02-03-17, 15:45, Patrick Bellasi wrote: > > diff --git a/kernel/sched/cpufreq_schedutil.c > > b/kernel/sched/cpufreq_schedutil.c > > @@ -293,15 +305,29 @@ static void sugov_update_shared(struct > > update_util_data *hook, u64 time, > > if (curr ==

Re: [PATCH 3/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks

On 03-Mar 14:01, Viresh Kumar wrote: > On 02-03-17, 15:45, Patrick Bellasi wrote: > > diff --git a/kernel/sched/cpufreq_schedutil.c > > b/kernel/sched/cpufreq_schedutil.c > > @@ -293,15 +305,29 @@ static void sugov_update_shared(struct > > update_util_data *hook, u64 time, > > if (curr ==

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 13:17:05 +0100 Alban wrote: > On Thu, 2 Mar 2017 21:22:20 +0100 > Boris Brezillon wrote: > > > On Thu, 2 Mar 2017 20:50:21 +0100 > > Alban wrote: > > > > > Add the binding to expose MTD partitions as

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 13:17:05 +0100 Alban wrote: > On Thu, 2 Mar 2017 21:22:20 +0100 > Boris Brezillon wrote: > > > On Thu, 2 Mar 2017 20:50:21 +0100 > > Alban wrote: > > > > > Add the binding to expose MTD partitions as nvmem providers. > > > > Looks good. Maybe you should take the

Re: [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger

On 02/28/2017 05:51 PM, Fabrice Gasnier wrote: > EXTi (external interrupt) signal can be routed internally as trigger > source for ADC conversions: STM32F4 ADC can use EXTI11. > > Retrieve interrupt trigger from DT, so it can be muxed into ADC IP, > via extsel. Hi, Sorry, I have some trouble

Re: [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger

On 02/28/2017 05:51 PM, Fabrice Gasnier wrote: > EXTi (external interrupt) signal can be routed internally as trigger > source for ADC conversions: STM32F4 ADC can use EXTI11. > > Retrieve interrupt trigger from DT, so it can be muxed into ADC IP, > via extsel. Hi, Sorry, I have some trouble

[PATCH] mac80211: Use setup_timer instead of init_timer

From: Ondřej Lysoněk Use setup_timer() and setup_deferrable_timer() to set the data and function timer fields. It makes the code cleaner and will allow for easier change of the timer struct internals. Signed-off-by: Ondřej Lysoněk

[PATCH] mac80211: Use setup_timer instead of init_timer

From: Ondřej Lysoněk Use setup_timer() and setup_deferrable_timer() to set the data and function timer fields. It makes the code cleaner and will allow for easier change of the timer struct internals. Signed-off-by: Ondřej Lysoněk Signed-off-by: Jiri Slaby Cc: Johannes Berg Cc: "David S.

[PATCH v3 2/5] staging: lustre: Remove unnecessary cast on void pointer

The following Coccinelle script was used to detect this: @r@ expression x; void* e; type T; identifier f; @@ ( *((T *)e) | ((T *)x)[...] | ((T*)x)->f | - (T*) e ) Signed-off-by: simran singhal --- drivers/staging/lustre/lustre/lmv/lmv_obd.c | 4 ++-- 1 file

[PATCH v3 2/5] staging: lustre: Remove unnecessary cast on void pointer

The following Coccinelle script was used to detect this: @r@ expression x; void* e; type T; identifier f; @@ ( *((T *)e) | ((T *)x)[...] | ((T*)x)->f | - (T*) e ) Signed-off-by: simran singhal --- drivers/staging/lustre/lustre/lmv/lmv_obd.c | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 11:27:34 + Srinivas Kandagatla wrote: > On 02/03/17 19:50, Alban wrote: > > Add the binding to expose MTD partitions as nvmem providers. > > It would be nice to see more description of this patch, explaining the > real use case. > > > >

[PATCH] scsi: lpfc: replace init_timer by setup_timer

From: Tomas Jasek This patch shortens every init_timer in lpfc module followed by function and data assignment using setup_timer. This is purely cleanup patch, it does not add new functionality nor remove any existing functionality. An init_timer call in this form:

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 11:27:34 + Srinivas Kandagatla wrote: > On 02/03/17 19:50, Alban wrote: > > Add the binding to expose MTD partitions as nvmem providers. > > It would be nice to see more description of this patch, explaining the > real use case. > > > > Signed-off-by: Alban > > --- >

[PATCH] scsi: lpfc: replace init_timer by setup_timer

From: Tomas Jasek This patch shortens every init_timer in lpfc module followed by function and data assignment using setup_timer. This is purely cleanup patch, it does not add new functionality nor remove any existing functionality. An init_timer call in this form: init_timer(>fc_disctmo);

Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API

On Fri, 3 Mar 2017 11:23:16 + Srinivas Kandagatla wrote: > > > + mutex_lock(_nvmem_list_lock); > > + list_for_each_entry(mtd_nvmem, _nvmem_list, list) { > > + if (mtd_nvmem->mtd == mtd) { > > + list_del(_nvmem->list); > > +

Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API

On Fri, 3 Mar 2017 11:23:16 + Srinivas Kandagatla wrote: > > > + mutex_lock(_nvmem_list_lock); > > + list_for_each_entry(mtd_nvmem, _nvmem_list, list) { > > + if (mtd_nvmem->mtd == mtd) { > > + list_del(_nvmem->list); > > + found = true; >

Re: [PATCH v2 0/4] fujitsu_init() cleanup

On Thu, Mar 02, 2017 at 08:19:38AM +0100, Micha?? K??pie?? wrote: > > On Wed, Mar 01, 2017 at 09:10:40AM +0100, Micha?? K??pie?? wrote: > > > These patches should make fujitsu_init() a bit more palatable. No > > > changes are made to platform device code yet, for clarity these will be > > >

Re: [PATCH v2 0/4] fujitsu_init() cleanup

On Thu, Mar 02, 2017 at 08:19:38AM +0100, Micha?? K??pie?? wrote: > > On Wed, Mar 01, 2017 at 09:10:40AM +0100, Micha?? K??pie?? wrote: > > > These patches should make fujitsu_init() a bit more palatable. No > > > changes are made to platform device code yet, for clarity these will be > > >

Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API

On Thu, 2 Mar 2017 22:18:03 +0100 Boris Brezillon wrote: > On Thu, 2 Mar 2017 20:50:22 +0100 > Alban wrote: > > [snip] > > > +static void mtd_nvmem_add(struct mtd_info *mtd) > > +{ > > + struct device *dev = >dev; > > + struct device_node

Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API

On Thu, 2 Mar 2017 22:18:03 +0100 Boris Brezillon wrote: > On Thu, 2 Mar 2017 20:50:22 +0100 > Alban wrote: > > [snip] > > > +static void mtd_nvmem_add(struct mtd_info *mtd) > > +{ > > + struct device *dev = >dev; > > + struct device_node *np = dev_of_node(dev); > > + struct

[PATCH 0/2] fs, ceph filesystem refcount conversions

Now when new refcount_t type and API are finally merged (see include/linux/refcount.h), the following patches convert various refcounters in the ceph filesystem from atomic_t to refcount_t. By doing this we prevent intentional or accidental underflows or overflows that can led to use-after-free

[PATCH 0/2] fs, ceph filesystem refcount conversions

Now when new refcount_t type and API are finally merged (see include/linux/refcount.h), the following patches convert various refcounters in the ceph filesystem from atomic_t to refcount_t. By doing this we prevent intentional or accidental underflows or overflows that can led to use-after-free

[PATCH 06/17] fs, btrfs: convert btrfs_delayed_ref_node.refs from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 06/17] fs, btrfs: convert btrfs_delayed_ref_node.refs from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by: Hans Liljestrand

[PATCH 1/3] futex: remove duplicated code

There is code duplicated over all architecture's headers for futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, and comparison of the result. Remove this duplication and leave up to the arches only the needed assembly which is now in arch_futex_atomic_op_inuser. Note that

[PATCH 1/3] futex: remove duplicated code

There is code duplicated over all architecture's headers for futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, and comparison of the result. Remove this duplication and leave up to the arches only the needed assembly which is now in arch_futex_atomic_op_inuser. Note that

[PATCH] drm/arcpgu: Opt in debugfs

This change adopts debugfs usage for outputting useful data. As of today we print: * Mode and real HW clock values * Standard FB info Code is heavily borrowed from ARM's HDLCD thus adding Liviu in Cc. Signed-off-by: Alexey Brodkin Cc: Liviu Dudau

[PATCH v3 3/5] coresight: add support for debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension" introduces several sampling registers, e.g.

[PATCH] drm/arcpgu: Opt in debugfs

This change adopts debugfs usage for outputting useful data. As of today we print: * Mode and real HW clock values * Standard FB info Code is heavily borrowed from ARM's HDLCD thus adding Liviu in Cc. Signed-off-by: Alexey Brodkin Cc: Liviu Dudau Cc: Daniel Vetter Cc: David Airlie Cc: Jose

[PATCH v3 3/5] coresight: add support for debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension" introduces several sampling registers, e.g.

[PATCH] Documentation/sphinx: fix primary_domain configuration

With Sphinx 1.5.3 I get the warning: WARNING: primary_domain 'C' not found, ignored. It seems that domain names in Sphinx are case-sensitive and for the C domain the name must be lower case. Signed-off-by: John Keeping --- Documentation/conf.py | 2 +- 1 file

[PATCH] Documentation/sphinx: fix primary_domain configuration

With Sphinx 1.5.3 I get the warning: WARNING: primary_domain 'C' not found, ignored. It seems that domain names in Sphinx are case-sensitive and for the C domain the name must be lower case. Signed-off-by: John Keeping --- Documentation/conf.py | 2 +- 1 file changed, 1 insertion(+),

Re: [PATCH 00/26] bring back stack frame warning with KASAN

On Thu, Mar 2, 2017 at 5:38 PM, Arnd Bergmann wrote: > It took a long while to get this done, but I'm finally ready > to send the first half of the KASAN stack size patches that > I did in response to the kernelci.org warnings. > > As before, it's worth mentioning that things are

Re: [PATCH 00/26] bring back stack frame warning with KASAN

On Thu, Mar 2, 2017 at 5:38 PM, Arnd Bergmann wrote: > It took a long while to get this done, but I'm finally ready > to send the first half of the KASAN stack size patches that > I did in response to the kernelci.org warnings. > > As before, it's worth mentioning that things are generally worse

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 11:27:34 + Srinivas Kandagatla wrote: > On 02/03/17 19:50, Alban wrote: > > Add the binding to expose MTD partitions as nvmem providers. > > It would be nice to see more description of this patch, explaining the > real use case. I'll

Re: [PATCH 1/3] doc: bindings: Add bindings documentation for mtd nvmem

On Fri, 3 Mar 2017 11:27:34 + Srinivas Kandagatla wrote: > On 02/03/17 19:50, Alban wrote: > > Add the binding to expose MTD partitions as nvmem providers. > > It would be nice to see more description of this patch, explaining the > real use case. I'll try, writing good documentation is

Re: [PATCH 1/3] dt-bindings: imx-ocotp: add compatible string for i.MX7D/S

On Wed, Mar 01, 2017 at 02:40:52PM +0800, Peng Fan wrote: > Add compatible string for i.MX7D/S > > Signed-off-by: Peng Fan > Cc: Shawn Guo > Cc: Srinivas Kandagatla > Cc: Maxime Ripard >

Re: [PATCH v11 2/9] mmc: cavium: Add core MMC driver for Cavium SOCs

On 6 February 2017 at 14:39, Jan Glauber wrote: > This core driver will be used by a MIPS platform driver > or by an ARM64 PCI driver. The core driver implements the > mmc_host_ops and slot probe & remove functions. > Callbacks are provided to allow platform specific

Re: [PATCH 1/3] dt-bindings: imx-ocotp: add compatible string for i.MX7D/S

On Wed, Mar 01, 2017 at 02:40:52PM +0800, Peng Fan wrote: > Add compatible string for i.MX7D/S > > Signed-off-by: Peng Fan > Cc: Shawn Guo > Cc: Srinivas Kandagatla > Cc: Maxime Ripard > Cc: Rob Herring > Cc: Mark Rutland > --- > Documentation/devicetree/bindings/nvmem/imx-ocotp.txt | 1 +

Re: [PATCH v11 2/9] mmc: cavium: Add core MMC driver for Cavium SOCs

On 6 February 2017 at 14:39, Jan Glauber wrote: > This core driver will be used by a MIPS platform driver > or by an ARM64 PCI driver. The core driver implements the > mmc_host_ops and slot probe & remove functions. > Callbacks are provided to allow platform specific interrupt > enable and bus

<    6   7   8   9   10   11   12   13   14   15   >