[PATCH] drm: sti: sti_dvo: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 4222 664 048861316

[PATCH] drm: sti: sti_dvo: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 4222 664 048861316

[PATCH v6 3/4] ARM: dts: imx6qdl.dtsi: add "fsl,imx6q-snvs-lpgpr" node

This node is for Low Power General Purpose Register which can be used as Non-Volatile Storage. Signed-off-by: Oleksij Rempel --- arch/arm/boot/dts/imx6qdl.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl.dtsi

[PATCH v6 0/4] nvmem: upstream snvs_lpgpr driver

changes v6: - check if device is writable by reading GPR_SL and GPR_HL bits - use regmap_bulk_* functions instead of while() { regmap_read/write } - add patch for imx6ul changes v5: - use dcfg->offset instead of priv->offset. changes v4: - change dependencies in Kconfig - remove unused

[PATCH v6 3/4] ARM: dts: imx6qdl.dtsi: add "fsl,imx6q-snvs-lpgpr" node

This node is for Low Power General Purpose Register which can be used as Non-Volatile Storage. Signed-off-by: Oleksij Rempel --- arch/arm/boot/dts/imx6qdl.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi index

[PATCH v6 0/4] nvmem: upstream snvs_lpgpr driver

changes v6: - check if device is writable by reading GPR_SL and GPR_HL bits - use regmap_bulk_* functions instead of while() { regmap_read/write } - add patch for imx6ul changes v5: - use dcfg->offset instead of priv->offset. changes v4: - change dependencies in Kconfig - remove unused

[PATCH v6 4/4] ARM: imx6ul: add "fsl,imx6ul-snvs-lpgpr" node

snvs_lpgpr confirmed to work with imx6ul as well. Signed-off-by: Oleksij Rempel Tested-by: Guy Shapiro --- Documentation/devicetree/bindings/nvmem/snvs-lpgpr.txt | 3 ++- arch/arm/boot/dts/imx6ul.dtsi | 4

[PATCH v6 4/4] ARM: imx6ul: add "fsl,imx6ul-snvs-lpgpr" node

snvs_lpgpr confirmed to work with imx6ul as well. Signed-off-by: Oleksij Rempel Tested-by: Guy Shapiro --- Documentation/devicetree/bindings/nvmem/snvs-lpgpr.txt | 3 ++- arch/arm/boot/dts/imx6ul.dtsi | 4 drivers/nvmem/snvs_lpgpr.c | 1

[PATCH v6 2/4] nvmem: add snvs_lpgpr driver

This is a driver for Low Power General Purpose Register (LPGPR) available on i.MX6 SoCs in Secure Non-Volatile Storage (SNVS) of this chip. It is a 32-bit read/write register located in the low power domain. Since LPGPR is located in the battery-backed power domain, LPGPR can be used by any

[PATCH v6 1/4] nvmem: dt: document SNVS LPGPR binding

Documentation bindings for the Low Power General Purpose Register available on i.MX6 SoCs in the Secure Non-Volatile Storage. Signed-off-by: Oleksij Rempel --- .../devicetree/bindings/nvmem/snvs-lpgpr.txt | 19 +++ 1 file changed, 19

[PATCH v6 2/4] nvmem: add snvs_lpgpr driver

This is a driver for Low Power General Purpose Register (LPGPR) available on i.MX6 SoCs in Secure Non-Volatile Storage (SNVS) of this chip. It is a 32-bit read/write register located in the low power domain. Since LPGPR is located in the battery-backed power domain, LPGPR can be used by any

[PATCH v6 1/4] nvmem: dt: document SNVS LPGPR binding

Documentation bindings for the Low Power General Purpose Register available on i.MX6 SoCs in the Secure Non-Volatile Storage. Signed-off-by: Oleksij Rempel --- .../devicetree/bindings/nvmem/snvs-lpgpr.txt | 19 +++ 1 file changed, 19 insertions(+) create mode 100644

Re: Linux 4.12-rc6

On Mon, 19 Jun 2017, Hugh Dickins wrote: > On Tue, 20 Jun 2017, Linus Torvalds wrote: > > On Tue, Jun 20, 2017 at 8:26 AM, Dave Jones wrote: > > > > Hugh Dickins (1): > > > > mm: larger stack guard gap, between vmas > > > > > > This seems to be buggered. ... > >

Re: Linux 4.12-rc6

On Mon, 19 Jun 2017, Hugh Dickins wrote: > On Tue, 20 Jun 2017, Linus Torvalds wrote: > > On Tue, Jun 20, 2017 at 8:26 AM, Dave Jones wrote: > > > > Hugh Dickins (1): > > > > mm: larger stack guard gap, between vmas > > > > > > This seems to be buggered. ... > > > > So maybe that "goto

Re: [PATCH v2 2/4] drm/panel: Add support for s6e63j0x03 panel driver

On 06/19/2017 06:14 PM, Andrzej Hajda wrote: On 15.06.2017 12:03, Hoegeun Kwon wrote: This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63" physical panel. This panel is used in Samsung

Re: [PATCH v2 2/4] drm/panel: Add support for s6e63j0x03 panel driver

On 06/19/2017 06:14 PM, Andrzej Hajda wrote: On 15.06.2017 12:03, Hoegeun Kwon wrote: This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63" physical panel. This panel is used in Samsung

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, Jun 19, 2017 at 04:36:37PM -0700, Kees Cook wrote: > Some hardened environments want to build kernels with slab_nomerge > already set (so that they do not depend on remembering to set the kernel > command line option). This is desired to reduce the risk of kernel heap > overflows being

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, Jun 19, 2017 at 04:36:37PM -0700, Kees Cook wrote: > Some hardened environments want to build kernels with slab_nomerge > already set (so that they do not depend on remembering to set the kernel > command line option). This is desired to reduce the risk of kernel heap > overflows being

Re: [kernel-hardening] [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Mon, Jun 19, 2017 at 04:36:36PM -0700, Kees Cook wrote: > From: David Windsor > > Some userspace APIs (e.g. ipc, seq_file) provide precise control over > the size of kernel kmallocs, which provides a trivial way to perform > heap overflow attacks where the attacker must

Re: [kernel-hardening] [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Mon, Jun 19, 2017 at 04:36:36PM -0700, Kees Cook wrote: > From: David Windsor > > Some userspace APIs (e.g. ipc, seq_file) provide precise control over > the size of kernel kmallocs, which provides a trivial way to perform > heap overflow attacks where the attacker must control neighboring >

Re: [patch 19/55] genirq: Provide irq_fixup_move_pending()

Hi Thomas, At 06/20/2017 07:37 AM, Thomas Gleixner wrote: [...] +/** + * irq_fixup_move_pending - Cleanup irq move pending from a dying CPU + * @desc: Interrupt descpriptor to clean up + * @force_clear: If set clear the move pending bit unconditionally. + *

Re: [patch 19/55] genirq: Provide irq_fixup_move_pending()

Hi Thomas, At 06/20/2017 07:37 AM, Thomas Gleixner wrote: [...] +/** + * irq_fixup_move_pending - Cleanup irq move pending from a dying CPU + * @desc: Interrupt descpriptor to clean up + * @force_clear: If set clear the move pending bit unconditionally. + *

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, 2017-06-19 at 16:36 -0700, Kees Cook wrote: > Some hardened environments want to build kernels with slab_nomerge > already set (so that they do not depend on remembering to set the > kernel > command line option). This is desired to reduce the risk of kernel > heap > overflows being able

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, 2017-06-19 at 16:36 -0700, Kees Cook wrote: > Some hardened environments want to build kernels with slab_nomerge > already set (so that they do not depend on remembering to set the > kernel > command line option). This is desired to reduce the risk of kernel > heap > overflows being able

Re: [kernel-hardening] [PATCH 17/23] dcache: define usercopy region in dentry_cache slab cache

On Mon, Jun 19, 2017 at 04:36:31PM -0700, Kees Cook wrote: > From: David Windsor > > When a dentry name is short enough, it can be stored directly in > the dentry itself. These dentry short names, stored in struct > dentry.d_iname and therefore contained in the dentry_cache

Re: [kernel-hardening] [PATCH 17/23] dcache: define usercopy region in dentry_cache slab cache

On Mon, Jun 19, 2017 at 04:36:31PM -0700, Kees Cook wrote: > From: David Windsor > > When a dentry name is short enough, it can be stored directly in > the dentry itself. These dentry short names, stored in struct > dentry.d_iname and therefore contained in the dentry_cache slab cache, > need

Re: [kernel-hardening] [PATCH 21/23] usercopy: Restrict non-usercopy caches to size 0

Hi David + Kees, On Mon, Jun 19, 2017 at 04:36:35PM -0700, Kees Cook wrote: > With all known usercopied cache whitelists now defined in the kernel, switch > the default usercopy region of kmem_cache_create() to size 0. Any new caches > with usercopy regions will now need to use

Re: [kernel-hardening] [PATCH 21/23] usercopy: Restrict non-usercopy caches to size 0

Hi David + Kees, On Mon, Jun 19, 2017 at 04:36:35PM -0700, Kees Cook wrote: > With all known usercopied cache whitelists now defined in the kernel, switch > the default usercopy region of kmem_cache_create() to size 0. Any new caches > with usercopy regions will now need to use

Re: [PATCH v10 4/5] i2c: aspeed: added driver for Aspeed I2C

I thought all of the comments made sense and will be addressed in my next revision, except the following: >> +static int aspeed_i2c_recover_bus(struct aspeed_i2c_bus *bus) >> +{ >> + unsigned long time_left, flags; >> + int ret = 0; >> + u32 command; >> + >> +

Re: [PATCH v10 4/5] i2c: aspeed: added driver for Aspeed I2C

I thought all of the comments made sense and will be addressed in my next revision, except the following: >> +static int aspeed_i2c_recover_bus(struct aspeed_i2c_bus *bus) >> +{ >> + unsigned long time_left, flags; >> + int ret = 0; >> + u32 command; >> + >> +

Re: [PATCH v5 6/6] ARM: dts: imx6: RIoTboard provide standby on power off option

On 20.06.2017 02:19, Stephen Boyd wrote: On 06/19, Oleksij Rempel wrote: This board, as well as some other boards with i.MX6 and a PMIC, uses a "MPIC_STBY_REQ" line to notify the PMIC about a state change. PMIC_STBY_REQ? Ok, thanks.

Re: [PATCH v5 6/6] ARM: dts: imx6: RIoTboard provide standby on power off option

On 20.06.2017 02:19, Stephen Boyd wrote: On 06/19, Oleksij Rempel wrote: This board, as well as some other boards with i.MX6 and a PMIC, uses a "MPIC_STBY_REQ" line to notify the PMIC about a state change. PMIC_STBY_REQ? Ok, thanks.

linux-next: manual merge of the tty tree with the arm-soc tree

Hi Greg, Today's linux-next merge of the tty tree got a conflict in: include/linux/platform_data/atmel.h between commit: 8a3d809373c6 ("ARM: at91: remove atmel_nand_data") from the arm-soc tree and commit: 92c8f7c0e109 ("tty/serial: atmel: make the driver DT only") from the tty tree.

linux-next: manual merge of the tty tree with the arm-soc tree

Hi Greg, Today's linux-next merge of the tty tree got a conflict in: include/linux/platform_data/atmel.h between commit: 8a3d809373c6 ("ARM: at91: remove atmel_nand_data") from the arm-soc tree and commit: 92c8f7c0e109 ("tty/serial: atmel: make the driver DT only") from the tty tree.

Re: [PATCH v3 1/4] sparc64: Add 16GB hugepage support

You need to provide a proper "[PATCH xxx 0/N] " header posting explaining what the series is doing at a high level, how it is doing it, and why it is doing it that way. A patch series is a collection of related patches attempting to achieve a specific high level end goal. If, instead, these are

Re: [PATCH v3 1/4] sparc64: Add 16GB hugepage support

You need to provide a proper "[PATCH xxx 0/N] " header posting explaining what the series is doing at a high level, how it is doing it, and why it is doing it that way. A patch series is a collection of related patches attempting to achieve a specific high level end goal. If, instead, these are

Re: [PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.

On 06/16/2017 08:13 PM, Eric Anholt wrote: Archit Taneja writes: On 06/16/2017 02:11 AM, Eric Anholt wrote: If the panel-bridge is being set up after the drm_mode_config_reset(), then the connector's state would never get initialized, and we'd dereference the NULL

Re: [PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.

On 06/16/2017 08:13 PM, Eric Anholt wrote: Archit Taneja writes: On 06/16/2017 02:11 AM, Eric Anholt wrote: If the panel-bridge is being set up after the drm_mode_config_reset(), then the connector's state would never get initialized, and we'd dereference the NULL in the hotplug path. We

[PATCH 3/3] arm64: dts: register Hi3660's thermal sensor

Bind thermal sensor driver for Hi3660. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- arch/arm64/boot/dts/hisilicon/hi3660.dtsi |7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi

[PATCH 2/3] thermal: hisilicon: add thermal sensor driver for Hi3660

This patch adds the support for thermal sensor of Hi3660 SoC. this will register sensors for thermal framework and use device tree to bind cooling device. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- drivers/thermal/Kconfig | 10

[PATCH 3/3] arm64: dts: register Hi3660's thermal sensor

Bind thermal sensor driver for Hi3660. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- arch/arm64/boot/dts/hisilicon/hi3660.dtsi |7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi index

[PATCH 2/3] thermal: hisilicon: add thermal sensor driver for Hi3660

This patch adds the support for thermal sensor of Hi3660 SoC. this will register sensors for thermal framework and use device tree to bind cooling device. Signed-off-by: Tao Wang Signed-off-by: Leo Yan --- drivers/thermal/Kconfig | 10 ++ drivers/thermal/Makefile |1 +

[PATCH 1/3] dt-bindings: Document the hi3660 thermal sensor bindings

This adds documentation of device tree bindings for the thermal sensor controller of hi3660 SoC. Signed-off-by: Tao Wang --- .../devicetree/bindings/thermal/hi3660-thermal.txt | 17 + 1 file changed, 17 insertions(+) create mode 100644

[PATCH 1/3] dt-bindings: Document the hi3660 thermal sensor bindings

This adds documentation of device tree bindings for the thermal sensor controller of hi3660 SoC. Signed-off-by: Tao Wang --- .../devicetree/bindings/thermal/hi3660-thermal.txt | 17 + 1 file changed, 17 insertions(+) create mode 100644

Re: Linux 4.12-rc6

On Mon, Jun 19, 2017 at 08:12:12PM -0700, Hugh Dickins wrote: > for Dave perhaps to try - but probably he's shut down now, so I'll > then grab a trinity, and see what luck I have with it. Almost shutdown, but not quite. Coincidentally, coverity just finished the rc6 run, and barfed this up..

Re: Linux 4.12-rc6

On Mon, Jun 19, 2017 at 08:12:12PM -0700, Hugh Dickins wrote: > for Dave perhaps to try - but probably he's shut down now, so I'll > then grab a trinity, and see what luck I have with it. Almost shutdown, but not quite. Coincidentally, coverity just finished the rc6 run, and barfed this up..

Re: [PATCH] crypto: caam: make of_device_ids const.

On Fri, Jun 16, 2017 at 02:46:44PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH] crypto: caam: make of_device_ids const.

On Fri, Jun 16, 2017 at 02:46:44PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH] crypto: n2: make of_device_ids const

On Thu, Jun 15, 2017 at 05:28:10PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH] crypto: n2: make of_device_ids const

On Thu, Jun 15, 2017 at 05:28:10PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH][crypto-next] crypto: cavium: fix spelling mistake "Revsion" -> "Revision"

On Tue, Jun 13, 2017 at 09:52:54AM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in seq_printf message > > Signed-off-by: Colin Ian King Patch applied. Thanks. -- Email: Herbert Xu

Re: [PATCH][crypto-next] crypto: cavium: fix spelling mistake "Revsion" -> "Revision"

On Tue, Jun 13, 2017 at 09:52:54AM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in seq_printf message > > Signed-off-by: Colin Ian King Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key:

Re: [PATCH v2 0/3] add support of hardware random generator on MediaTek MT7622

On Mon, Jun 12, 2017 at 11:56:53PM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > Changes since v1: > - update the bindings with the specific "mediatek,mt7622-rng" > instead of the generic one as "mediatek,generic-rng" > > The series add support of hardware

Re: [PATCH v2 0/3] add support of hardware random generator on MediaTek MT7622

On Mon, Jun 12, 2017 at 11:56:53PM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > Changes since v1: > - update the bindings with the specific "mediatek,mt7622-rng" > instead of the generic one as "mediatek,generic-rng" > > The series add support of hardware RNG on MediaTek MT7622

Re: [PATCH][crypto-next] crypto: omap-aes: fix spelling mistake "Encryptio" -> "Encryption"

On Tue, Jun 13, 2017 at 09:46:47AM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in pr_err message > > Signed-off-by: Colin Ian King Patch applied. Thanks. -- Email: Herbert Xu

Re: [PATCH][crypto-next] crypto: omap-aes: fix spelling mistake "Encryptio" -> "Encryption"

On Tue, Jun 13, 2017 at 09:46:47AM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in pr_err message > > Signed-off-by: Colin Ian King Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key:

Re: [PATCH] rsa-pkcs1pad: use constant time memory comparison for MACs

On Sun, Jun 11, 2017 at 11:20:23PM +0200, Jason A. Donenfeld wrote: > Otherwise, we enable all sorts of forgeries via timing attack. > > Signed-off-by: Jason A. Donenfeld > Suggested-by: Stephan Müller > Cc: sta...@vger.kernel.org > Cc: Herbert Xu

Re: [PATCH] rsa-pkcs1pad: use constant time memory comparison for MACs

On Sun, Jun 11, 2017 at 11:20:23PM +0200, Jason A. Donenfeld wrote: > Otherwise, we enable all sorts of forgeries via timing attack. > > Signed-off-by: Jason A. Donenfeld > Suggested-by: Stephan Müller > Cc: sta...@vger.kernel.org > Cc: Herbert Xu > Cc: linux-cry...@vger.kernel.org Patch

Re: WMI and Kernel:User interface

On Mon, Jun 19, 2017 at 03:10:09PM -0700, Andy Lutomirski wrote: > On Tue, Jun 13, 2017 at 9:38 PM, Greg Kroah-Hartman > wrote: > > On Tue, Jun 13, 2017 at 10:07:19AM -0700, Darren Hart wrote: > >> On Tue, Jun 13, 2017 at 06:52:47PM +0200, Greg Kroah-Hartman wrote: >

Re: WMI and Kernel:User interface

On Mon, Jun 19, 2017 at 03:10:09PM -0700, Andy Lutomirski wrote: > On Tue, Jun 13, 2017 at 9:38 PM, Greg Kroah-Hartman > wrote: > > On Tue, Jun 13, 2017 at 10:07:19AM -0700, Darren Hart wrote: > >> On Tue, Jun 13, 2017 at 06:52:47PM +0200, Greg Kroah-Hartman wrote: > >> > > As a concrete example,

[PATCH] regulator: lp87565: Fix the initial voltage range

The latest documentation reveals that initial voltage range that is supported is starting from 0.6V for all the PMICs belonging to lp87565 family. Fix the same. Signed-off-by: Keerthy Fixes: f0168a9bf ("regulator: lp87565: Add support for lp87565 PMIC regulators") ---

[PATCH] regulator: lp87565: Fix the initial voltage range

The latest documentation reveals that initial voltage range that is supported is starting from 0.6V for all the PMICs belonging to lp87565 family. Fix the same. Signed-off-by: Keerthy Fixes: f0168a9bf ("regulator: lp87565: Add support for lp87565 PMIC regulators") ---

Re: [PATCH] crypto: crypto4xx - fix an error code

On Sat, Jun 10, 2017 at 02:54:33PM +0200, Christophe JAILLET wrote: > If 'kzalloc' fails, we return 0 which means success. > return -ENOMEM instead as already done a few lines above. > > Signed-off-by: Christophe JAILLET Patch applied. Thanks. -- Email: Herbert

Re: [PATCH] crypto: crypto4xx - fix an error code

On Sat, Jun 10, 2017 at 02:54:33PM +0200, Christophe JAILLET wrote: > If 'kzalloc' fails, we return 0 which means success. > return -ENOMEM instead as already done a few lines above. > > Signed-off-by: Christophe JAILLET Patch applied. Thanks. -- Email: Herbert Xu Home Page:

Re: [PATCH v2 1/2] selftests: lib: Skip tests on missing test modules

Hi Kees, On 20 June 2017 at 00:21, Kees Cook wrote: > On Mon, Jun 19, 2017 at 6:44 AM, Sumit Semwal wrote: >> With older kernels, printf.sh and bitmap.sh fail because they can't find >> the respective test modules they are looking for. >> >> Add

Re: [PATCH v2 1/2] selftests: lib: Skip tests on missing test modules

Hi Kees, On 20 June 2017 at 00:21, Kees Cook wrote: > On Mon, Jun 19, 2017 at 6:44 AM, Sumit Semwal wrote: >> With older kernels, printf.sh and bitmap.sh fail because they can't find >> the respective test modules they are looking for. >> >> Add the skip portion on missing the respective

Re: [PATCH v2] gpio: lp87565: Add support for GPIO

On Thursday 15 June 2017 12:03 PM, Keerthy wrote: > Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported > and can be configured in Open-drain output or Push-pull output. > > Signed-off-by: Keerthy > --- > > Latest version of mfd patch: > >

Re: [PATCH v2] gpio: lp87565: Add support for GPIO

On Thursday 15 June 2017 12:03 PM, Keerthy wrote: > Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported > and can be configured in Open-drain output or Push-pull output. > > Signed-off-by: Keerthy > --- > > Latest version of mfd patch: > >

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

Hi, Andrew On 2017/6/20 5:54, Andrew Lunn wrote: > On Mon, Jun 19, 2017 at 02:00:43PM -0700, Florian Fainelli wrote: >> On 06/16/2017 02:24 AM, Lin Yun Sheng wrote: >>> This patch fixes the phy loopback self_test failed issue. when >>> Marvell Phy Module is loaded, it will powerdown fiber when

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

Hi, Andrew On 2017/6/20 5:54, Andrew Lunn wrote: > On Mon, Jun 19, 2017 at 02:00:43PM -0700, Florian Fainelli wrote: >> On 06/16/2017 02:24 AM, Lin Yun Sheng wrote: >>> This patch fixes the phy loopback self_test failed issue. when >>> Marvell Phy Module is loaded, it will powerdown fiber when

Re: Linux 4.12-rc6

On Tue, 20 Jun 2017, Linus Torvalds wrote: > On Tue, Jun 20, 2017 at 8:26 AM, Dave Jones wrote: > > > Hugh Dickins (1): > > > mm: larger stack guard gap, between vmas > > > > This seems to be buggered. > > > > 002331 0396712307 0 2 kernel BUG at

Re: Linux 4.12-rc6

On Tue, 20 Jun 2017, Linus Torvalds wrote: > On Tue, Jun 20, 2017 at 8:26 AM, Dave Jones wrote: > > > Hugh Dickins (1): > > > mm: larger stack guard gap, between vmas > > > > This seems to be buggered. > > > > 002331 0396712307 0 2 kernel BUG at mm/mmap.c:1963! > > 002332

Re: [PATCH v6 09/12] Input: Add power key driver for Rockchip RK805 PMIC

On Thu, Jun 08, 2017 at 03:30:27PM +0800, Jianhong Chen wrote: > From: chenjh > > This driver provides a input driver for the power > key on the Rockchip RK805 PMIC. > > Signed-off-by: chenjh > --- > drivers/input/misc/Kconfig| 6 +++ >

Re: [PATCH v6 09/12] Input: Add power key driver for Rockchip RK805 PMIC

On Thu, Jun 08, 2017 at 03:30:27PM +0800, Jianhong Chen wrote: > From: chenjh > > This driver provides a input driver for the power > key on the Rockchip RK805 PMIC. > > Signed-off-by: chenjh > --- > drivers/input/misc/Kconfig| 6 +++ > drivers/input/misc/Makefile | 1 + >

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

hi, Florian On 2017/6/20 5:00, Florian Fainelli wrote: > On 06/16/2017 02:24 AM, Lin Yun Sheng wrote: >> This patch fixes the phy loopback self_test failed issue. when >> Marvell Phy Module is loaded, it will powerdown fiber when doing >> phy loopback self test, which cause phy loopback self_test

Re: [PATCH NET] net/hns:bugfix of ethtool -t phy self_test

hi, Florian On 2017/6/20 5:00, Florian Fainelli wrote: > On 06/16/2017 02:24 AM, Lin Yun Sheng wrote: >> This patch fixes the phy loopback self_test failed issue. when >> Marvell Phy Module is loaded, it will powerdown fiber when doing >> phy loopback self test, which cause phy loopback self_test

Re: [GIT PULL] NTB bug fixes for v4.12

On Tue, Jun 20, 2017 at 2:42 AM, Jon Mason wrote: > Hello Linus, > Here are a few NTB bug fixes for 4.12. So I pulled this, mainly because it removed more lines than it added due to the revert. But generally I absolutely *hate* pulling stuff that I can see was committed just

Re: [GIT PULL] NTB bug fixes for v4.12

On Tue, Jun 20, 2017 at 2:42 AM, Jon Mason wrote: > Hello Linus, > Here are a few NTB bug fixes for 4.12. So I pulled this, mainly because it removed more lines than it added due to the revert. But generally I absolutely *hate* pulling stuff that I can see was committed just hours ago. Why was

[PATCH v4] platform/x86: dell-laptop: Fix bogus keyboard backlight sysfs interface

Dell Latitude 3160 does not have keyboard backlight, but there is a sysfs interface for it, which does nothing at all. KBD_LED_ON_TOKEN is the only token can be found. Since it doesn't have KBD_LED_OFF_TOKEN or KBD_LED_AUTO_*_TOKEN, it should be safe to assume at least two tokens should be

[PATCH v4] platform/x86: dell-laptop: Fix bogus keyboard backlight sysfs interface

Dell Latitude 3160 does not have keyboard backlight, but there is a sysfs interface for it, which does nothing at all. KBD_LED_ON_TOKEN is the only token can be found. Since it doesn't have KBD_LED_OFF_TOKEN or KBD_LED_AUTO_*_TOKEN, it should be safe to assume at least two tokens should be

[PATCH] mm: Add SLUB free list pointer obfuscation

This SLUB free list pointer obfuscation code is modified from Brad Spengler/PaX Team's code in the last public patch of grsecurity/PaX based on my understanding of the code. Changes or omissions from the original code are mine and don't reflect the original grsecurity/PaX code. This adds a

[PATCH] mm: Add SLUB free list pointer obfuscation

This SLUB free list pointer obfuscation code is modified from Brad Spengler/PaX Team's code in the last public patch of grsecurity/PaX based on my understanding of the code. Changes or omissions from the original code are mine and don't reflect the original grsecurity/PaX code. This adds a

Re: [PATCH] x86/mm: Don't reenter flush_tlb_func_common()

On 2017/6/19 23:05, Andy Lutomirski wrote: > On Mon, Jun 19, 2017 at 6:33 AM, zhong jiang wrote: >> On 2017/6/19 12:48, Andy Lutomirski wrote: >>> It was historically possible to have two concurrent TLB flushes >>> targeting the same CPU: one initiated locally and one

Re: [PATCH] x86/mm: Don't reenter flush_tlb_func_common()

On 2017/6/19 23:05, Andy Lutomirski wrote: > On Mon, Jun 19, 2017 at 6:33 AM, zhong jiang wrote: >> On 2017/6/19 12:48, Andy Lutomirski wrote: >>> It was historically possible to have two concurrent TLB flushes >>> targeting the same CPU: one initiated locally and one initiated >>> remotely.

[PATCH v2 1/3] fsi: Add fsi_master_rescan()

We'll want non-core fsi code to trigger a rescan, so introduce a non-static fsi_master_rescan() function. Use this for the existing unscan/scan behaviour too. Signed-off-by: Jeremy Kerr Reviewed-by: Joel Stanley Reviewed-by: Christopher Bostic

[PATCH v2 1/3] fsi: Add fsi_master_rescan()

We'll want non-core fsi code to trigger a rescan, so introduce a non-static fsi_master_rescan() function. Use this for the existing unscan/scan behaviour too. Signed-off-by: Jeremy Kerr Reviewed-by: Joel Stanley Reviewed-by: Christopher Bostic --- v2: - Add

Re: [PATCH 3.10 060/268] xen/gntdev: Use VM_MIXEDMAP instead of VM_IO to avoid NUMA balancing

On Mon, 19 Jun 2017, Willy Tarreau wrote: > From: Boris Ostrovsky > > commit 30faaafdfa0c754c91bac60f216c9f34a2bfdf7e upstream. > > Commit 9c17d96500f7 ("xen/gntdev: Grant maps should not be subject to > NUMA balancing") set VM_IO flag to prevent grant maps from

Re: [PATCH 3.10 060/268] xen/gntdev: Use VM_MIXEDMAP instead of VM_IO to avoid NUMA balancing

On Mon, 19 Jun 2017, Willy Tarreau wrote: > From: Boris Ostrovsky > > commit 30faaafdfa0c754c91bac60f216c9f34a2bfdf7e upstream. > > Commit 9c17d96500f7 ("xen/gntdev: Grant maps should not be subject to > NUMA balancing") set VM_IO flag to prevent grant maps from being > subjected to NUMA

Re: Linux 4.12-rc6

On Tue, Jun 20, 2017 at 10:32:00AM +0800, Linus Torvalds wrote: > On Tue, Jun 20, 2017 at 8:26 AM, Dave Jones wrote: > > > Hugh Dickins (1): > > > mm: larger stack guard gap, between vmas > > > > This seems to be buggered. > > > > 002331 0396712307 0 2

Re: Linux 4.12-rc6

On Tue, Jun 20, 2017 at 10:32:00AM +0800, Linus Torvalds wrote: > On Tue, Jun 20, 2017 at 8:26 AM, Dave Jones wrote: > > > Hugh Dickins (1): > > > mm: larger stack guard gap, between vmas > > > > This seems to be buggered. > > > > 002331 0396712307 0 2 kernel BUG at

Re: [PATCH] mm/list_lru.c: use cond_resched_lock() for nlru->lock

Hello, On 6/17/2017 4:44 PM, Vladimir Davydov wrote: That said, I think it would be better to patch shrink_dcache_sb() or dentry_lru_isolate_shrink() instead of list_lru_walk() in order to fix this lockup. Thanks for the review. I will enhance the patch as per your suggestion. -- Qualcomm

Re: [PATCH v5 0/4] tty/serial: meson_uart: add support for core clock handling

On Mon, Jun 19, 2017 at 10:43:05AM +0200, Neil Armstrong wrote: > On 06/14/2017 10:29 AM, Neil Armstrong wrote: > > This patchset is a re-spin of Helmut Klein's v3 patchset at [0] and the v4 > > patchset at [1]. > > > > Initially, the original patchset was made to enable usage on the non-AO > >

Re: [PATCH] mm/list_lru.c: use cond_resched_lock() for nlru->lock

Hello, On 6/17/2017 4:44 PM, Vladimir Davydov wrote: That said, I think it would be better to patch shrink_dcache_sb() or dentry_lru_isolate_shrink() instead of list_lru_walk() in order to fix this lockup. Thanks for the review. I will enhance the patch as per your suggestion. -- Qualcomm

Re: [PATCH v5 0/4] tty/serial: meson_uart: add support for core clock handling

On Mon, Jun 19, 2017 at 10:43:05AM +0200, Neil Armstrong wrote: > On 06/14/2017 10:29 AM, Neil Armstrong wrote: > > This patchset is a re-spin of Helmut Klein's v3 patchset at [0] and the v4 > > patchset at [1]. > > > > Initially, the original patchset was made to enable usage on the non-AO > >

Re: [PATCHv2 3/3] mm: Use updated pmdp_invalidate() inteface to track dirty/accessed bits

Hello Kirill, On Mon, Jun 19, 2017 at 05:03:23PM +0300, Kirill A. Shutemov wrote: > On Fri, Jun 16, 2017 at 11:53:33PM +0900, Minchan Kim wrote: > > Hi Andrea, > > > > On Fri, Jun 16, 2017 at 04:27:20PM +0200, Andrea Arcangeli wrote: > > > Hello Minchan, > > > > > > On Fri, Jun 16, 2017 at

Re: [PATCHv2 3/3] mm: Use updated pmdp_invalidate() inteface to track dirty/accessed bits

Hello Kirill, On Mon, Jun 19, 2017 at 05:03:23PM +0300, Kirill A. Shutemov wrote: > On Fri, Jun 16, 2017 at 11:53:33PM +0900, Minchan Kim wrote: > > Hi Andrea, > > > > On Fri, Jun 16, 2017 at 04:27:20PM +0200, Andrea Arcangeli wrote: > > > Hello Minchan, > > > > > > On Fri, Jun 16, 2017 at

RE: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI

Hi, > From: Bastien Nocera [mailto:had...@hadess.net] > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch > exported by ACPI > > On Mon, 2017-06-19 at 01:43 +, Zheng, Lv wrote: > > > > > > > > If you implement it in such a way that GNOME settings daemon > > >

RE: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI

Hi, > From: Bastien Nocera [mailto:had...@hadess.net] > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch > exported by ACPI > > On Mon, 2017-06-19 at 01:43 +, Zheng, Lv wrote: > > > > > > > > If you implement it in such a way that GNOME settings daemon > > >

Re: [PATCH v2 06/12] Input: wm97xx: add new AC97 bus support

On Mon, Jun 19, 2017 at 09:27:03AM +0200, Robert Jarzmik wrote: > This adds support for the new AC97 bus code, which discovers the devices > rather than uses platform data. > > As part of this discovery, it enables a multi-function device wm97xx, > which supports touchscreen, battery, ADC and an

Re: [PATCH v2 06/12] Input: wm97xx: add new AC97 bus support

On Mon, Jun 19, 2017 at 09:27:03AM +0200, Robert Jarzmik wrote: > This adds support for the new AC97 bus code, which discovers the devices > rather than uses platform data. > > As part of this discovery, it enables a multi-function device wm97xx, > which supports touchscreen, battery, ADC and an

<    1   2   3   4   5   6   7   8   9   10   >