Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Mon, Jan 30, 2017 at 1:05 PM, Marc Zyngier wrote: > On 30/01/17 17:58, Jintack Lim wrote: >> On Sun, Jan 29, 2017 at 6:54 AM, Marc Zyngier wrote: >>> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >>> wrote: Make

Re: [RFC V2 08/12] mm: Add new VMA flag VM_CDM

On Mon, Jan 30, 2017 at 09:05:49AM +0530, Anshuman Khandual wrote: > VMA which contains CDM memory pages should be marked with new VM_CDM flag. > These VMAs need to be identified in various core kernel paths for special > handling and this flag will help in their identification. > >

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Mon, Jan 30, 2017 at 1:05 PM, Marc Zyngier wrote: > On 30/01/17 17:58, Jintack Lim wrote: >> On Sun, Jan 29, 2017 at 6:54 AM, Marc Zyngier wrote: >>> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >>> wrote: Make cntvoff per each timer context. This is helpful to abstract kvm

Re: [RFC V2 08/12] mm: Add new VMA flag VM_CDM

On Mon, Jan 30, 2017 at 09:05:49AM +0530, Anshuman Khandual wrote: > VMA which contains CDM memory pages should be marked with new VM_CDM flag. > These VMAs need to be identified in various core kernel paths for special > handling and this flag will help in their identification. > >

Re: [PATCH] ARM64: meson-gxbb-p200: add ADC laddered keys

Neil Armstrong writes: > Add the 5 buttons connected to a resistor laddered matrix and sampled > by the SAR ADC channel 0. > > Only the p200 board has these buttons, the P201 doesn't. > > Signed-off-by: Neil Armstrong Applied to v4.11/dt64.

Re: [PATCH] ARM64: meson-gxbb-p200: add ADC laddered keys

Neil Armstrong writes: > Add the 5 buttons connected to a resistor laddered matrix and sampled > by the SAR ADC channel 0. > > Only the p200 board has these buttons, the P201 doesn't. > > Signed-off-by: Neil Armstrong Applied to v4.11/dt64. Note that I fixed up the subject prefix to be ARM64:

[PATCH 09/14] kdb: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- kernel/debug/kdb/kdb_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c index ca18391..095e6d8 100644 ---

[PATCH 08/14] ipmi: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/char/ipmi/ipmi_msghandler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c index

[PATCH 09/14] kdb: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- kernel/debug/kdb/kdb_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c index ca18391..095e6d8 100644 ---

[PATCH 08/14] ipmi: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/char/ipmi/ipmi_msghandler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c index 9f69995..961d677 100644 ---

[PATCH 11/14] PM: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- kernel/power/user.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/power/user.c b/kernel/power/user.c index 22df9f7..c478572 100644 --- a/kernel/power/user.c +++

[PATCH 11/14] PM: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- kernel/power/user.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/power/user.c b/kernel/power/user.c index 22df9f7..c478572 100644 --- a/kernel/power/user.c +++ b/kernel/power/user.c @@

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On 30/01/17 18:41, Christoffer Dall wrote: > On Mon, Jan 30, 2017 at 05:50:03PM +, Marc Zyngier wrote: >> On 30/01/17 15:02, Christoffer Dall wrote: >>> On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On 30/01/17 18:41, Christoffer Dall wrote: > On Mon, Jan 30, 2017 at 05:50:03PM +, Marc Zyngier wrote: >> On 30/01/17 15:02, Christoffer Dall wrote: >>> On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim wrote: > Now

[PATCH 10/14] PM / Hibernate: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- kernel/power/hibernate.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c index b26dbc4..cfa7930 100644 ---

[PATCH 10/14] PM / Hibernate: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- kernel/power/hibernate.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c index b26dbc4..cfa7930 100644 --- a/kernel/power/hibernate.c +++

Re: [PATCH] perf: fix topology test on systems with sparse CPUs

On Mon, Jan 30, 2017 at 05:53:34PM +0100, Jan Stancek wrote: SNIP > + ret = build_cpu_topo(tp, cpu); > if (ret < 0) > break; > } > + > +out_free: > + cpu_map__put(map); > if (ret) { > free_cpu_topo(tp); >

Re: [PATCH] perf: fix topology test on systems with sparse CPUs

On Mon, Jan 30, 2017 at 05:53:34PM +0100, Jan Stancek wrote: SNIP > + ret = build_cpu_topo(tp, cpu); > if (ret < 0) > break; > } > + > +out_free: > + cpu_map__put(map); > if (ret) { > free_cpu_topo(tp); >

Re: [PATCH] perf: fix topology test on systems with sparse CPUs

On Mon, Jan 30, 2017 at 05:53:34PM +0100, Jan Stancek wrote: > Topology test fails on systems with sparse CPUs, e.g. SNIP > > - for (i = 0; i < nr; i++) { > - ret = build_cpu_topo(tp, i); > + for (i = 0; i < tp->cpu_nr; i++) { > + cpu = map->map[i]; no need for

Re: [PATCH] perf: fix topology test on systems with sparse CPUs

On Mon, Jan 30, 2017 at 05:53:34PM +0100, Jan Stancek wrote: > Topology test fails on systems with sparse CPUs, e.g. SNIP > > - for (i = 0; i < nr; i++) { > - ret = build_cpu_topo(tp, i); > + for (i = 0; i < tp->cpu_nr; i++) { > + cpu = map->map[i]; no need for

Re: [PATCH] perf: fix topology test on systems with sparse CPUs

On Mon, Jan 30, 2017 at 05:53:34PM +0100, Jan Stancek wrote: SNIP > diff --git a/tools/perf/util/env.c b/tools/perf/util/env.c > index bb964e86b09d..0c2cae807a61 100644 > --- a/tools/perf/util/env.c > +++ b/tools/perf/util/env.c > @@ -60,29 +60,45 @@ int perf_env__set_cmdline(struct perf_env

Re: [PATCH] perf: fix topology test on systems with sparse CPUs

On Mon, Jan 30, 2017 at 05:53:34PM +0100, Jan Stancek wrote: SNIP > diff --git a/tools/perf/util/env.c b/tools/perf/util/env.c > index bb964e86b09d..0c2cae807a61 100644 > --- a/tools/perf/util/env.c > +++ b/tools/perf/util/env.c > @@ -60,29 +60,45 @@ int perf_env__set_cmdline(struct perf_env

[PATCH 07/14] PM / RUNTIME: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/base/power/runtime.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c index 872eac4..8ed435f 100644 ---

[PATCH 06/14] s390/qeth: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/s390/net/qeth_core_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/s390/net/qeth_core_main.c b/drivers/s390/net/qeth_core_main.c index 315d8a2..9595b90

[PATCH 06/14] s390/qeth: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/s390/net/qeth_core_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/s390/net/qeth_core_main.c b/drivers/s390/net/qeth_core_main.c index 315d8a2..9595b90 100644 ---

[PATCH 07/14] PM / RUNTIME: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/base/power/runtime.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c index 872eac4..8ed435f 100644 ---

[PATCH 14/14] xfs: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- fs/xfs/xfs_buf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c index ac3b4db..51b2167 100644 --- a/fs/xfs/xfs_buf.c +++ b/fs/xfs/xfs_buf.c @@

[PATCH 13/14] ext4: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- fs/ext4/ext4.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h index 164a2e0..3184c25 100644 --- a/fs/ext4/ext4.h +++ b/fs/ext4/ext4.h @@ -2916,7

[PATCH 14/14] xfs: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- fs/xfs/xfs_buf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c index ac3b4db..51b2167 100644 --- a/fs/xfs/xfs_buf.c +++ b/fs/xfs/xfs_buf.c @@ -1684,7 +1684,7

[PATCH 13/14] ext4: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- fs/ext4/ext4.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h index 164a2e0..3184c25 100644 --- a/fs/ext4/ext4.h +++ b/fs/ext4/ext4.h @@ -2916,7 +2916,7 @@ static

[PATCH 12/14] s390/topology: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- arch/s390/kernel/topology.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/s390/kernel/topology.c b/arch/s390/kernel/topology.c index 7b2b19b..820ef64 100644 ---

[PATCH 12/14] s390/topology: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- arch/s390/kernel/topology.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/s390/kernel/topology.c b/arch/s390/kernel/topology.c index 7b2b19b..820ef64 100644 ---

timerfd: use-after-free in timerfd_remove_cancel

Hello, The following program triggers use-after-free in timerfd_remove_cancel: https://gist.githubusercontent.com/dvyukov/202576d437c84ffbbe52e9ccd77e1b44/raw/5562bff8626a73627157331ea2b837f59080ac84/gistfile1.txt BUG: KASAN: use-after-free in __list_del include/linux/list.h:104 [inline] at addr

timerfd: use-after-free in timerfd_remove_cancel

Hello, The following program triggers use-after-free in timerfd_remove_cancel: https://gist.githubusercontent.com/dvyukov/202576d437c84ffbbe52e9ccd77e1b44/raw/5562bff8626a73627157331ea2b837f59080ac84/gistfile1.txt BUG: KASAN: use-after-free in __list_del include/linux/list.h:104 [inline] at addr

Re: [of/unittest] 815d74b35e: BUG: unable to handle kernel NULL pointer dereference at 00000012

On Tue, 24 Jan 2017 23:21:07 +0900 Sergey Senozhatsky wrote: > Hello, > > Cc Steven I think you wanted to Cc Peter Zijlstra on this. He's the kernel maintainer for perf. I do the more generic tracing. -- Steve > > On (01/24/17 19:20), kernel test robot wrote: >

Re: [of/unittest] 815d74b35e: BUG: unable to handle kernel NULL pointer dereference at 00000012

On Tue, 24 Jan 2017 23:21:07 +0900 Sergey Senozhatsky wrote: > Hello, > > Cc Steven I think you wanted to Cc Peter Zijlstra on this. He's the kernel maintainer for perf. I do the more generic tracing. -- Steve > > On (01/24/17 19:20), kernel test robot wrote: > > of/unittest: fix

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On Mon, Jan 30, 2017 at 05:50:03PM +, Marc Zyngier wrote: > On 30/01/17 15:02, Christoffer Dall wrote: > > On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: > >> On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim > >> wrote: > >>> Now that we maintain the

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On Mon, Jan 30, 2017 at 05:50:03PM +, Marc Zyngier wrote: > On 30/01/17 15:02, Christoffer Dall wrote: > > On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: > >> On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim > >> wrote: > >>> Now that we maintain the EL1 physical timer register

[PATCH 03/14] drm/omap: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c b/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c index

[PATCH 03/14] drm/omap: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c b/drivers/gpu/drm/omapdrm/omap_dmm_tiler.c index 3cab066..abd0b15

[PATCH 02/14] drm/exynos: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c index

[PATCH 02/14] drm/exynos: use atomic_dec_not_zero()

instead of atomic_add_unless(value, -1, 0) Signed-off-by: Fabian Frederick --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c index 745cfbd..0e191b6

[PATCH v2 3/5] gpio: 104-idio-16: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the ACCES 104-IDIO-16. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH v2 3/5] gpio: 104-idio-16: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the ACCES 104-IDIO-16. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH 01/14] locking/atomic: import atomic_dec_not_zero()

complementary definition to atomic_inc_not_zero() featured in lib/fault-inject.c Signed-off-by: Fabian Frederick --- include/linux/atomic.h | 2 ++ lib/fault-inject.c | 2 -- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/atomic.h

[PATCH 00/14] use atomic_dec_not_zero()

complementary definition to atomic_inc_not_zero() featured in lib/fault-inject.c. This small patchset moves it to include/linux/atomic.h using it instead of atomic_add_unless(value, -1, 0) s390 patches were not compile-tested. Fabian Frederick (14): locking/atomic: import atomic_dec_not_zero()

[PATCH 01/14] locking/atomic: import atomic_dec_not_zero()

complementary definition to atomic_inc_not_zero() featured in lib/fault-inject.c Signed-off-by: Fabian Frederick --- include/linux/atomic.h | 2 ++ lib/fault-inject.c | 2 -- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/atomic.h b/include/linux/atomic.h index

[PATCH 00/14] use atomic_dec_not_zero()

complementary definition to atomic_inc_not_zero() featured in lib/fault-inject.c. This small patchset moves it to include/linux/atomic.h using it instead of atomic_add_unless(value, -1, 0) s390 patches were not compile-tested. Fabian Frederick (14): locking/atomic: import atomic_dec_not_zero()

Re: [PATCH v3 24/24] drm/rockchip: dw-mipi-dsi: support read commands

On Mon, 30 Jan 2017 10:26:11 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:44PM +, John Keeping wrote: > > I haven't found any method for getting the length of a response, so this > > just uses the requested rx_len > > > > Signed-off-by: John Keeping > > --- > >

Re: [PATCH v3 24/24] drm/rockchip: dw-mipi-dsi: support read commands

On Mon, 30 Jan 2017 10:26:11 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:44PM +, John Keeping wrote: > > I haven't found any method for getting the length of a response, so this > > just uses the requested rx_len > > > > Signed-off-by: John Keeping > > --- > > v3: > > - Fix

RE: Device or HBA level QD throttling creates randomness in sequetial workload

> -Original Message- > From: Jens Axboe [mailto:ax...@kernel.dk] > Sent: Monday, January 30, 2017 10:03 PM > To: Bart Van Assche; osan...@osandov.com; kashyap.de...@broadcom.com > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > h...@infradead.org;

RE: Device or HBA level QD throttling creates randomness in sequetial workload

> -Original Message- > From: Jens Axboe [mailto:ax...@kernel.dk] > Sent: Monday, January 30, 2017 10:03 PM > To: Bart Van Assche; osan...@osandov.com; kashyap.de...@broadcom.com > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > h...@infradead.org;

Re: Device or HBA level QD throttling creates randomness in sequetial workload

On 01/30/2017 11:28 AM, Kashyap Desai wrote: >> -Original Message- >> From: Jens Axboe [mailto:ax...@kernel.dk] >> Sent: Monday, January 30, 2017 10:03 PM >> To: Bart Van Assche; osan...@osandov.com; kashyap.de...@broadcom.com >> Cc: linux-s...@vger.kernel.org;

Re: Device or HBA level QD throttling creates randomness in sequetial workload

On 01/30/2017 11:28 AM, Kashyap Desai wrote: >> -Original Message- >> From: Jens Axboe [mailto:ax...@kernel.dk] >> Sent: Monday, January 30, 2017 10:03 PM >> To: Bart Van Assche; osan...@osandov.com; kashyap.de...@broadcom.com >> Cc: linux-s...@vger.kernel.org;

[PATCH v2 5/5] gpio: ws16c48: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the WinSystems WS16C48. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH v2 4/5] gpio: gpio-mm: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the Diamond Systems GPIO-MM. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt

[PATCH v2 5/5] gpio: ws16c48: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the WinSystems WS16C48. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH v2 4/5] gpio: gpio-mm: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the Diamond Systems GPIO-MM. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt

[PATCH v2 0/5] gpio: Add support for GPIO names for several ISA_BUS_API drivers

Changes in v2: - Fixed typo in WS16C48 patch; ws14c48_names should be ws16c48_names This patchset sets the gpio_chip names option of several ISA_BUS_API GPIO drivers with an array of GPIO line names that match their respective manual documentation. This should make it easier for users to

[PATCH v2 0/5] gpio: Add support for GPIO names for several ISA_BUS_API drivers

Changes in v2: - Fixed typo in WS16C48 patch; ws14c48_names should be ws16c48_names This patchset sets the gpio_chip names option of several ISA_BUS_API GPIO drivers with an array of GPIO line names that match their respective manual documentation. This should make it easier for users to

[PATCH v2 2/5] gpio: 104-idi-48: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the ACCES 104-IDI-48. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH v2 1/5] gpio: 104-dio-48e: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the ACCES 104-DIO-48E. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH v2 1/5] gpio: 104-dio-48e: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the ACCES 104-DIO-48E. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray

[PATCH v2 2/5] gpio: 104-idi-48: Add support for GPIO names

This patch sets the gpio_chip names option with an array of GPIO line names that match the manual documentation for the ACCES 104-IDI-48. This should make it easier for users to identify which GPIO line corresponds to a respective GPIO pin on the device. Signed-off-by: William Breathitt Gray ---

Re: [PATCH v3 05/24] drm/rockchip: dw-mipi-dsi: fix generic packet status check

On Sun, Jan 29, 2017 at 01:24:25PM +, John Keeping wrote: > We want to check that both the GEN_CMD_EMPTY and GEN_PLD_W_EMPTY bits > are set so we can't just check "val & mask" because that will be true if > either bit is set. > Reviewed-by: Sean Paul > Signed-off-by:

Re: [PATCH v3 05/24] drm/rockchip: dw-mipi-dsi: fix generic packet status check

On Sun, Jan 29, 2017 at 01:24:25PM +, John Keeping wrote: > We want to check that both the GEN_CMD_EMPTY and GEN_PLD_W_EMPTY bits > are set so we can't just check "val & mask" because that will be true if > either bit is set. > Reviewed-by: Sean Paul > Signed-off-by: John Keeping >

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On 01/30/2017 01:07 PM, Eric Dumazet wrote: > On Mon, 2017-01-30 at 12:45 -0500, Boris Ostrovsky wrote: >> rx_refill_timer should be deleted as soon as we disconnect from the >> backend since otherwise it is possible for the timer to go off before >> we get to xennet_destroy_queues(). If this

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On 01/30/2017 01:07 PM, Eric Dumazet wrote: > On Mon, 2017-01-30 at 12:45 -0500, Boris Ostrovsky wrote: >> rx_refill_timer should be deleted as soon as we disconnect from the >> backend since otherwise it is possible for the timer to go off before >> we get to xennet_destroy_queues(). If this

Re: [PATCH v3 09/24] drm/rockchip: dw-mipi-dsi: only request HS clock when required

On Sun, Jan 29, 2017 at 01:24:29PM +, John Keeping wrote: > Requesting the HS clock from the PHY before we initialize it causes an > invalid signal to be sent out since the input clock is not yet > configured. The PHY databook suggests only asserting this signal when > performing HS

Re: [PATCH v3 09/24] drm/rockchip: dw-mipi-dsi: only request HS clock when required

On Sun, Jan 29, 2017 at 01:24:29PM +, John Keeping wrote: > Requesting the HS clock from the PHY before we initialize it causes an > invalid signal to be sent out since the input clock is not yet > configured. The PHY databook suggests only asserting this signal when > performing HS

Re: [PATCH 0/7] Fix issues and factorize arm/arm64 capacity information code

Hi Catalin, On 30/01/17 17:51, Catalin Marinas wrote: > On Mon, Jan 30, 2017 at 12:29:01PM +, Juri Lelli wrote: > > I'd need more advice on this set, especially on how and if patch 6 could > > fly. > > Since you got some comments and said that you are going to fix them in > the next

Re: [PATCH 0/7] Fix issues and factorize arm/arm64 capacity information code

Hi Catalin, On 30/01/17 17:51, Catalin Marinas wrote: > On Mon, Jan 30, 2017 at 12:29:01PM +, Juri Lelli wrote: > > I'd need more advice on this set, especially on how and if patch 6 could > > fly. > > Since you got some comments and said that you are going to fix them in > the next

Re: [PATCH v3 08/24] drm/rockchip: dw-mipi-dsi: respect message flags

On Sun, Jan 29, 2017 at 01:24:28PM +, John Keeping wrote: > Instead of always sending commands in LP mode, respect the > MIPI_DSI_MSG_USE_LPM flag to decide how to send each message. Also > request acks if MIPI_DSI_MSG_REQ_ACK is set. > Reviewed-by: Sean Paul >

Re: [PATCH v3 08/24] drm/rockchip: dw-mipi-dsi: respect message flags

On Sun, Jan 29, 2017 at 01:24:28PM +, John Keeping wrote: > Instead of always sending commands in LP mode, respect the > MIPI_DSI_MSG_USE_LPM flag to decide how to send each message. Also > request acks if MIPI_DSI_MSG_REQ_ACK is set. > Reviewed-by: Sean Paul > Signed-off-by: John Keeping

[PATCH 0/2] watchdog: cleanup ep93xx platform drivers

The ep93xx_wdt driver is used by EP93xx based platforms for the internal watchdog of the EP93xx processor. The TS-72xx platforms have an additional watchdog provided by the CPLD on those boards. Cleanup both drivers. H Hartley Sweeten (2): watchdog: ep93xx_wdt: cleanup and let the core handle

[PATCH 0/2] watchdog: cleanup ep93xx platform drivers

The ep93xx_wdt driver is used by EP93xx based platforms for the internal watchdog of the EP93xx processor. The TS-72xx platforms have an additional watchdog provided by the CPLD on those boards. Cleanup both drivers. H Hartley Sweeten (2): watchdog: ep93xx_wdt: cleanup and let the core handle

[PATCH 1/2] watchdog: ep93xx_wdt: cleanup and let the core handle the heartbeat

Cleanup this driver and remove the 200ms heartbeat timer. The core now has the ability to handle the heartbeat. Signed-off-by: H Hartley Sweeten Cc: Wim Van Sebroeck Cc: Guenter Roeck --- drivers/watchdog/ep93xx_wdt.c | 115

[PATCH 1/2] watchdog: ep93xx_wdt: cleanup and let the core handle the heartbeat

Cleanup this driver and remove the 200ms heartbeat timer. The core now has the ability to handle the heartbeat. Signed-off-by: H Hartley Sweeten Cc: Wim Van Sebroeck Cc: Guenter Roeck --- drivers/watchdog/ep93xx_wdt.c | 115 +- 1 file changed, 46

[PATCH] exit: fix the setns() && PR_SET_CHILD_SUBREAPER interaction

find_new_reaper() checks same_thread_group(reaper, child_reaper) to prevent the cross-namespace reparenting but this is not enough if the exiting parent was injected by setns() + fork(). Suppose we have a process P in the root namespace and some namespace X. P does setns() to enter the X

[PATCH] exit: fix the setns() && PR_SET_CHILD_SUBREAPER interaction

find_new_reaper() checks same_thread_group(reaper, child_reaper) to prevent the cross-namespace reparenting but this is not enough if the exiting parent was injected by setns() + fork(). Suppose we have a process P in the root namespace and some namespace X. P does setns() to enter the X

Re: [RFC V2 05/12] cpuset: Add cpuset_inc() inside cpuset_init()

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > Currently cpusets_enabled() wrongfully returns 0 even if we have a root > cpuset configured on the system. This got missed when jump level was > introduced in place of number_of_cpusets with the commit 664eeddeef65 > ("mm: page_alloc: use jump

Re: [RFC V2 05/12] cpuset: Add cpuset_inc() inside cpuset_init()

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > Currently cpusets_enabled() wrongfully returns 0 even if we have a root > cpuset configured on the system. This got missed when jump level was > introduced in place of number_of_cpusets with the commit 664eeddeef65 > ("mm: page_alloc: use jump

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Sun, Jan 29, 2017 at 6:54 AM, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim > wrote: >> Make cntvoff per each timer context. This is helpful to abstract kvm >> timer functions to work with timer context without

[PATCH 2/2] watchdog: ts72xx_wdt: convert driver to watchdog core

Cleanup this driver and convert it to use the watchdog framework API. Signed-off-by: H Hartley Sweeten Cc: Mika Westerberg Cc: Wim Van Sebroeck Cc: Guenter Roeck --- drivers/watchdog/ts72xx_wdt.c | 447

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Sun, Jan 29, 2017 at 6:54 AM, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim > wrote: >> Make cntvoff per each timer context. This is helpful to abstract kvm >> timer functions to work with timer context without considering timer >> types (e.g. physical timer or

[PATCH 2/2] watchdog: ts72xx_wdt: convert driver to watchdog core

Cleanup this driver and convert it to use the watchdog framework API. Signed-off-by: H Hartley Sweeten Cc: Mika Westerberg Cc: Wim Van Sebroeck Cc: Guenter Roeck --- drivers/watchdog/ts72xx_wdt.c | 447 +- 1 file changed, 93 insertions(+), 354

Re: [PATCH v3 06/24] drm/rockchip: dw-mipi-dsi: avoid out-of-bounds read on tx_buf

On Mon, 30 Jan 2017 13:01:46 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:26PM +, John Keeping wrote: > > As a side-effect of this, encode the endianness explicitly rather than > > casting a u16. > > > > Signed-off-by: John Keeping > > Reviewed-by: Chris Zhong

Re: [PATCH v3 06/24] drm/rockchip: dw-mipi-dsi: avoid out-of-bounds read on tx_buf

On Mon, 30 Jan 2017 13:01:46 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:26PM +, John Keeping wrote: > > As a side-effect of this, encode the endianness explicitly rather than > > casting a u16. > > > > Signed-off-by: John Keeping > > Reviewed-by: Chris Zhong > > --- > > v3: >

Re: setns() && PR_SET_CHILD_SUBREAPER

Hi Eric, sorry for delay, I was sick. On 01/25, Eric W. Biederman wrote: > > Oleg Nesterov writes: > > > So what do you think about the patch below? > > That does look like the correct logic. Great, > Whose tree do we want to run merge these fixes through? I can pick them >

Re: setns() && PR_SET_CHILD_SUBREAPER

Hi Eric, sorry for delay, I was sick. On 01/25, Eric W. Biederman wrote: > > Oleg Nesterov writes: > > > So what do you think about the patch below? > > That does look like the correct logic. Great, > Whose tree do we want to run merge these fixes through? I can pick them > up if that would

Re: [PATCH 1/2] watchdog: sama5d4: Cache MR instead of a partial config

On Mon, Jan 30, 2017 at 06:18:47PM +0100, Alexandre Belloni wrote: > .config is used to cache a part of WDT_MR at probe time and is not used > afterwards. Instead of doing that, actually cache MR and avoid reading it > every time it is modified. > The semantic change here is that the old code

Re: [PATCH 1/2] watchdog: sama5d4: Cache MR instead of a partial config

On Mon, Jan 30, 2017 at 06:18:47PM +0100, Alexandre Belloni wrote: > .config is used to cache a part of WDT_MR at probe time and is not used > afterwards. Instead of doing that, actually cache MR and avoid reading it > every time it is modified. > The semantic change here is that the old code

Re: [PATCH v2 0/2] drm: Add support for tiny LCD displays

On Mon, Jan 30, 2017 at 04:03:53PM +0100, Noralf Trønnes wrote: > > Den 30.01.2017 09.44, skrev Daniel Vetter: > > Hi Noralf, > > > > On Fri, Jan 27, 2017 at 08:56:29PM +0100, Noralf Trønnes wrote: > > > This is an attempt at providing a DRM version of drivers/staging/fbtft. > > > > > > The

Re: [PATCH v2 0/2] drm: Add support for tiny LCD displays

On Mon, Jan 30, 2017 at 04:03:53PM +0100, Noralf Trønnes wrote: > > Den 30.01.2017 09.44, skrev Daniel Vetter: > > Hi Noralf, > > > > On Fri, Jan 27, 2017 at 08:56:29PM +0100, Noralf Trønnes wrote: > > > This is an attempt at providing a DRM version of drivers/staging/fbtft. > > > > > > The

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On Mon, 2017-01-30 at 12:45 -0500, Boris Ostrovsky wrote: > rx_refill_timer should be deleted as soon as we disconnect from the > backend since otherwise it is possible for the timer to go off before > we get to xennet_destroy_queues(). If this happens we may dereference > queue->rx.sring which is

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On Mon, 2017-01-30 at 12:45 -0500, Boris Ostrovsky wrote: > rx_refill_timer should be deleted as soon as we disconnect from the > backend since otherwise it is possible for the timer to go off before > we get to xennet_destroy_queues(). If this happens we may dereference > queue->rx.sring which is

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On 30/01/17 17:58, Jintack Lim wrote: > On Sun, Jan 29, 2017 at 6:54 AM, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >> wrote: >>> Make cntvoff per each timer context. This is helpful to abstract kvm >>> timer functions

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On 30/01/17 17:58, Jintack Lim wrote: > On Sun, Jan 29, 2017 at 6:54 AM, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >> wrote: >>> Make cntvoff per each timer context. This is helpful to abstract kvm >>> timer functions to work with timer context without considering

Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization

On 01/30/2017 08:25 AM, Vadim Lomovtsev wrote: This patch is to address PEM initialization issue which causes network issues. It is necessary to search for _HID:PNP0A08 while requesting PEM resources via ACPI instead of "THRX0002". Since this is fixing new code, there should be no chance to

Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization

On 01/30/2017 08:25 AM, Vadim Lomovtsev wrote: This patch is to address PEM initialization issue which causes network issues. It is necessary to search for _HID:PNP0A08 while requesting PEM resources via ACPI instead of "THRX0002". Since this is fixing new code, there should be no chance to

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