[PATCH memory-model 6/8] kokr/locking/memory-barriers: De-emphasize smp_read_barrier_depends() some more

From: SeongJae Park This commit applies an upstream change, commit f28f0868feb1 ("locking/memory-barriers: De-emphasize smp_read_barrier_depends() some more") to the Korean version documentation. Signed-off-by: SeongJae Park Signed-off-by: Paul E.

[PATCH memory-model 6/8] kokr/locking/memory-barriers: De-emphasize smp_read_barrier_depends() some more

From: SeongJae Park This commit applies an upstream change, commit f28f0868feb1 ("locking/memory-barriers: De-emphasize smp_read_barrier_depends() some more") to the Korean version documentation. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney ---

[PATCH memory-model 8/8] atomic_ops.rst: Use `warning` rst directive

From: SeongJae Park One warning message in 'atomic_ops.rst' is not using 'warning' rst directive while others does. This commit modifies the message to use 'warning' rst directive. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney

[PATCH memory-model 5/8] kokr/memory-barriers: Fix description of data dependency barriers

From: SeongJae Park This commit applies an upstream change, commit 51de78892b12 ("memory-barriers: Fix description of data dependency barriers") to the Korean version document. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney

[PATCH memory-model 5/8] kokr/memory-barriers: Fix description of data dependency barriers

From: SeongJae Park This commit applies an upstream change, commit 51de78892b12 ("memory-barriers: Fix description of data dependency barriers") to the Korean version document. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney ---

[PATCH memory-model 8/8] atomic_ops.rst: Use `warning` rst directive

From: SeongJae Park One warning message in 'atomic_ops.rst' is not using 'warning' rst directive while others does. This commit modifies the message to use 'warning' rst directive. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney --- Documentation/core-api/atomic_ops.rst | 10

[PATCH memory-model 7/8] atomic_ops.rst: Fix wrong example code

From: SeongJae Park Example code snippets for necessary of READ_ONCE() and WRITE_ONCE() has an unnecessary line of code and wrong condition. This commit fixes them. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney

Re: [PATCH 18/18] rcu: Use pr_fmt to prefix "rcu: " to logging output

On Mon, 2018-05-14 at 15:24 -0700, Paul E. McKenney wrote: > On Mon, May 14, 2018 at 02:41:59PM -0700, Joe Perches wrote: > > On Mon, 2018-05-14 at 13:29 -0700, Paul E. McKenney wrote: > > > On Thu, May 10, 2018 at 08:45:44AM -0700, Joe Perches wrote: > > > > Use a consistent logging prefix for

[PATCH memory-model 7/8] atomic_ops.rst: Fix wrong example code

From: SeongJae Park Example code snippets for necessary of READ_ONCE() and WRITE_ONCE() has an unnecessary line of code and wrong condition. This commit fixes them. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney Acked-by: Alan Stern --- Documentation/core-api/atomic_ops.rst |

Re: [PATCH 18/18] rcu: Use pr_fmt to prefix "rcu: " to logging output

On Mon, 2018-05-14 at 15:24 -0700, Paul E. McKenney wrote: > On Mon, May 14, 2018 at 02:41:59PM -0700, Joe Perches wrote: > > On Mon, 2018-05-14 at 13:29 -0700, Paul E. McKenney wrote: > > > On Thu, May 10, 2018 at 08:45:44AM -0700, Joe Perches wrote: > > > > Use a consistent logging prefix for

[PATCH memory-model 3/8] kokr/doc: De-emphasize smp_read_barrier_depends

From: SeongJae Park This commit applies an upstream change, commit 9ad3c143d7d6 ("doc: De-emphasize smp_read_barrier_depends") to the Korean version document. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney ---

[PATCH memory-model 3/8] kokr/doc: De-emphasize smp_read_barrier_depends

From: SeongJae Park This commit applies an upstream change, commit 9ad3c143d7d6 ("doc: De-emphasize smp_read_barrier_depends") to the Korean version document. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney --- Documentation/translations/ko_KR/memory-barriers.txt | 7 +-- 1

[PATCH memory-model 2/8] kokr/doc: READ_ONCE() now implies smp_barrier_depends()

From: SeongJae Park This commit applies an upstream change, commit 40555946447a ("doc: READ_ONCE() now implies smp_barrier_depends()") to the Korean version document. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney

[PATCH memory-model 2/8] kokr/doc: READ_ONCE() now implies smp_barrier_depends()

From: SeongJae Park This commit applies an upstream change, commit 40555946447a ("doc: READ_ONCE() now implies smp_barrier_depends()") to the Korean version document. Signed-off-by: SeongJae Park Signed-off-by: Paul E. McKenney --- Documentation/translations/ko_KR/memory-barriers.txt | 15

[PATCH memory-model 0/8] memory-barriers.txt and atomic_ops.rst updates

Hello! This series contains changes to the atomic_ops.rst file and to the memory-barriers.txt file and its Korean translation. These changes are ready for inclusion into -tip. 1. Fix memory-barriers.txt's ordering example contrasting DMA to MMIO, courtesy of Will Deacon. 2-6.

[PATCH memory-model 0/8] memory-barriers.txt and atomic_ops.rst updates

Hello! This series contains changes to the atomic_ops.rst file and to the memory-barriers.txt file and its Korean translation. These changes are ready for inclusion into -tip. 1. Fix memory-barriers.txt's ordering example contrasting DMA to MMIO, courtesy of Will Deacon. 2-6.

[PATCH v2] pstore: Convert internal records to timespec64

This prepares pstore for converting the VFS layer to timespec64. Signed-off-by: Kees Cook --- I can carry this for v4.18 unless you'd like to do it as part of your series? --- drivers/firmware/efi/efi-pstore.c | 27 ++- fs/pstore/inode.c

[PATCH v2] pstore: Convert internal records to timespec64

This prepares pstore for converting the VFS layer to timespec64. Signed-off-by: Kees Cook --- I can carry this for v4.18 unless you'd like to do it as part of your series? --- drivers/firmware/efi/efi-pstore.c | 27 ++- fs/pstore/inode.c | 3 ++-

Re: [PATCHv5] gpio: Remove VLA from gpiolib

On 04/20/2018 02:02 AM, Geert Uytterhoeven wrote: Hi Laura, Thanks for your patch! On Fri, Apr 13, 2018 at 11:24 PM, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a

Re: [PATCHv5] gpio: Remove VLA from gpiolib

On 04/20/2018 02:02 AM, Geert Uytterhoeven wrote: Hi Laura, Thanks for your patch! On Fri, Apr 13, 2018 at 11:24 PM, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the

Re: [PATCH v3 3/3] mailbox: ACPI: erroneous error message when parsing the ACPI PCCT

On 05/14/2018 03:04 PM, Prakash, Prashanth wrote: > > > On 4/30/2018 6:39 PM, Al Stone wrote: >> There have been multiple reports of the following error message: >> >> [0.068293] Error parsing PCC subspaces from PCCT >> >> This error message is not correct. In multiple cases examined, the

Re: [PATCH v3 3/3] mailbox: ACPI: erroneous error message when parsing the ACPI PCCT

On 05/14/2018 03:04 PM, Prakash, Prashanth wrote: > > > On 4/30/2018 6:39 PM, Al Stone wrote: >> There have been multiple reports of the following error message: >> >> [0.068293] Error parsing PCC subspaces from PCCT >> >> This error message is not correct. In multiple cases examined, the

[PATCH 2/2] phy: qcom-qusb2: Quiet -EPROBE_DEFER from qusb2_phy_probe()

The -EPROBE_DEFER virus demands special case code to avoid printing error messages when the error is only -EPROBE_DEFER. Spread the virus to a new host: qusb2_phy_probe(). Specifically handle when our regulators might not be ready yet. Signed-off-by: Douglas Anderson ---

[PATCH 1/2] phy: qcom-qmp: Quiet -EPROBE_DEFER from qcom_qmp_phy_probe()

The -EPROBE_DEFER virus demands special case code to avoid printing error messages when the error is only -EPROBE_DEFER. Spread the virus to a new host: qcom_qmp_phy_probe(). Specifically handle when our regulators might not be ready yet. Signed-off-by: Douglas Anderson

[PATCH 2/2] phy: qcom-qusb2: Quiet -EPROBE_DEFER from qusb2_phy_probe()

The -EPROBE_DEFER virus demands special case code to avoid printing error messages when the error is only -EPROBE_DEFER. Spread the virus to a new host: qusb2_phy_probe(). Specifically handle when our regulators might not be ready yet. Signed-off-by: Douglas Anderson ---

[PATCH 1/2] phy: qcom-qmp: Quiet -EPROBE_DEFER from qcom_qmp_phy_probe()

The -EPROBE_DEFER virus demands special case code to avoid printing error messages when the error is only -EPROBE_DEFER. Spread the virus to a new host: qcom_qmp_phy_probe(). Specifically handle when our regulators might not be ready yet. Signed-off-by: Douglas Anderson ---

[RFC PATCH 0/5] Add ChromeOS EC CEC Support

Hi All, The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support throught it's Embedded Controller, to enable the Linux CEC Core to communicate with it and get the CEC Physical Address from the correct HDMI Connector, the following must be added/changed: - Add the CEC sub-device

[RFC PATCH 0/5] Add ChromeOS EC CEC Support

Hi All, The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support throught it's Embedded Controller, to enable the Linux CEC Core to communicate with it and get the CEC Physical Address from the correct HDMI Connector, the following must be added/changed: - Add the CEC sub-device

[RFC PATCH 4/5] mfd: cros-ec: Introduce CEC commands and events definitions.

From: Stefan Adolfsson The EC can expose a CEC bus, this patch adds the CEC related definitions needed by the cros-ec-cec driver. Having a 16 byte mkbp event size makes it possible to send CEC messages from the EC to the AP directly inside the mkbp event instead of first

[RFC PATCH 4/5] mfd: cros-ec: Introduce CEC commands and events definitions.

From: Stefan Adolfsson The EC can expose a CEC bus, this patch adds the CEC related definitions needed by the cros-ec-cec driver. Having a 16 byte mkbp event size makes it possible to send CEC messages from the EC to the AP directly inside the mkbp event instead of first doing a notification and

[RFC PATCH 5/5] media: platform: Add Chrome OS EC CEC driver

The Chrome OS Embedded Controller can expose a CEC bus, this patch add the driver for such feature of the Embedded Controller. This driver is part of the cros-ec MFD and will be add as a sub-device when the feature bit is exposed by the EC. The controller will only handle a single logical

[PATCH] regulator: core: Quiet -EPROBE_DEFER from regulator_bulk_get()

The -EPROBE_DEFER virus demands special case code to avoid printing error messages when the error is only -EPROBE_DEFER. Spread the virus to a new host: regulator_bulk_get() Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 5 +++-- 1 file changed, 3

[RFC PATCH 5/5] media: platform: Add Chrome OS EC CEC driver

The Chrome OS Embedded Controller can expose a CEC bus, this patch add the driver for such feature of the Embedded Controller. This driver is part of the cros-ec MFD and will be add as a sub-device when the feature bit is exposed by the EC. The controller will only handle a single logical

[PATCH] regulator: core: Quiet -EPROBE_DEFER from regulator_bulk_get()

The -EPROBE_DEFER virus demands special case code to avoid printing error messages when the error is only -EPROBE_DEFER. Spread the virus to a new host: regulator_bulk_get() Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)

[RFC PATCH 3/5] drm/i915: hdmi: add CEC notifier to intel_hdmi

This patchs adds the cec_notifier feature to the intel_hdmi part of the i915 DRM driver. It uses the HDMI DRM connector name to differentiate between each HDMI ports. The changes will allow the i915 HDMI code to notify EDID and HPD changes to an eventual CEC adapter. Signed-off-by: Neil Armstrong

[RFC PATCH 1/5] mfd: cros_ec_dev: Add CEC sub-device registration

The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device when the CEC feature bit is present. Signed-off-by: Neil Armstrong --- drivers/mfd/cros_ec_dev.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/mfd/cros_ec_dev.c

[RFC PATCH 3/5] drm/i915: hdmi: add CEC notifier to intel_hdmi

This patchs adds the cec_notifier feature to the intel_hdmi part of the i915 DRM driver. It uses the HDMI DRM connector name to differentiate between each HDMI ports. The changes will allow the i915 HDMI code to notify EDID and HPD changes to an eventual CEC adapter. Signed-off-by: Neil Armstrong

[RFC PATCH 1/5] mfd: cros_ec_dev: Add CEC sub-device registration

The EC can expose a CEC bus, thus add the cros-ec-cec MFD sub-device when the CEC feature bit is present. Signed-off-by: Neil Armstrong --- drivers/mfd/cros_ec_dev.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/mfd/cros_ec_dev.c b/drivers/mfd/cros_ec_dev.c index

[RFC PATCH 2/5] media: cec-notifier: Get notifier by device and connector name

In non device-tree world, we can need to get the notifier by the driver name directly and eventually defer probe if not yet created. This patch adds a variant of the get function by using the device name instead and will not create a notifier if not yet created. But the i915 driver exposes at

[RFC PATCH 2/5] media: cec-notifier: Get notifier by device and connector name

In non device-tree world, we can need to get the notifier by the driver name directly and eventually defer probe if not yet created. This patch adds a variant of the get function by using the device name instead and will not create a notifier if not yet created. But the i915 driver exposes at

Re: [PATCH tip/core/rcu 0/21] Contention reduction for v4.18

On Tue, May 15, 2018 at 08:21:20AM +1000, Nicholas Piggin wrote: > On Mon, 14 May 2018 09:09:07 -0700 > "Paul E. McKenney" wrote: > > > On Mon, May 14, 2018 at 04:42:33PM +1000, Nicholas Piggin wrote: > > > On Sun, 22 Apr 2018 20:02:58 -0700 > > > "Paul E. McKenney"

Re: [PATCH tip/core/rcu 0/21] Contention reduction for v4.18

On Tue, May 15, 2018 at 08:21:20AM +1000, Nicholas Piggin wrote: > On Mon, 14 May 2018 09:09:07 -0700 > "Paul E. McKenney" wrote: > > > On Mon, May 14, 2018 at 04:42:33PM +1000, Nicholas Piggin wrote: > > > On Sun, 22 Apr 2018 20:02:58 -0700 > > > "Paul E. McKenney" wrote: > > > > > > >

Re: [PATCH] MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs

On Mon, May 14, 2018 at 04:49:43PM +0100, Maciej W. Rozycki wrote: > Check the TIF_32BIT_FPREGS task setting of the tracee rather than the > tracer in determining the layout of floating-point general registers in > the floating-point context, correcting access to odd-numbered registers > for

Re: [PATCH] MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs

On Mon, May 14, 2018 at 04:49:43PM +0100, Maciej W. Rozycki wrote: > Check the TIF_32BIT_FPREGS task setting of the tracee rather than the > tracer in determining the layout of floating-point general registers in > the floating-point context, correcting access to odd-numbered registers > for

Re: [PATCH] net/mlx5: Use 'kvfree()' for memory allocated by 'kvzalloc()'

On Mon, May 14, 2018 at 11:56 AM, David Miller wrote: > From: Christophe JAILLET > Date: Sat, 12 May 2018 19:09:25 +0200 > >> 'out' is allocated with 'kvzalloc()'. 'kvfree()' must be used to free it. >> >> Signed-off-by: Christophe JAILLET

Re: [PATCH] net/mlx5: Use 'kvfree()' for memory allocated by 'kvzalloc()'

On Mon, May 14, 2018 at 11:56 AM, David Miller wrote: > From: Christophe JAILLET > Date: Sat, 12 May 2018 19:09:25 +0200 > >> 'out' is allocated with 'kvzalloc()'. 'kvfree()' must be used to free it. >> >> Signed-off-by: Christophe JAILLET > > Saeed, I assume I will see this in one of your

[PATCH] objtool: ignore INT3 padding

NOP padding doesn't count as unreachable instruction neither should INT3. Signed-off-by: Alexey Dobriyan --- tools/objtool/arch.h|3 ++- tools/objtool/arch/x86/decode.c |4 tools/objtool/check.c |3 +++ 3 files changed, 9

[PATCH] objtool: ignore INT3 padding

NOP padding doesn't count as unreachable instruction neither should INT3. Signed-off-by: Alexey Dobriyan --- tools/objtool/arch.h|3 ++- tools/objtool/arch/x86/decode.c |4 tools/objtool/check.c |3 +++ 3 files changed, 9 insertions(+), 1 deletion(-) ---

Re: [PATCH 1/2] mips: xilfpga: stop generating useless dtb.o

On Wed, Apr 25, 2018 at 11:10:35PM +0200, Alexandre Belloni wrote: > a dtb.o is generated from nexys4ddr.dts but this is never used since it has > been moved to mips/generic with commit b35565bb16a5 ("MIPS: generic: Add > support > for MIPSfpga") > > Signed-off-by: Alexandre Belloni

Re: [PATCH 1/2] mips: xilfpga: stop generating useless dtb.o

On Wed, Apr 25, 2018 at 11:10:35PM +0200, Alexandre Belloni wrote: > a dtb.o is generated from nexys4ddr.dts but this is never used since it has > been moved to mips/generic with commit b35565bb16a5 ("MIPS: generic: Add > support > for MIPSfpga") > > Signed-off-by: Alexandre Belloni Both

Re: [PATCH 18/18] rcu: Use pr_fmt to prefix "rcu: " to logging output

On Mon, May 14, 2018 at 02:41:59PM -0700, Joe Perches wrote: > On Mon, 2018-05-14 at 13:29 -0700, Paul E. McKenney wrote: > > On Thu, May 10, 2018 at 08:45:44AM -0700, Joe Perches wrote: > > > Use a consistent logging prefix for all rcu related output. > > > > > > Signed-off-by: Joe Perches

Re: [PATCH 18/18] rcu: Use pr_fmt to prefix "rcu: " to logging output

On Mon, May 14, 2018 at 02:41:59PM -0700, Joe Perches wrote: > On Mon, 2018-05-14 at 13:29 -0700, Paul E. McKenney wrote: > > On Thu, May 10, 2018 at 08:45:44AM -0700, Joe Perches wrote: > > > Use a consistent logging prefix for all rcu related output. > > > > > > Signed-off-by: Joe Perches > >

Re: [PATCH tip/core/rcu 0/21] Contention reduction for v4.18

On Mon, 14 May 2018 09:09:07 -0700 "Paul E. McKenney" wrote: > On Mon, May 14, 2018 at 04:42:33PM +1000, Nicholas Piggin wrote: > > On Sun, 22 Apr 2018 20:02:58 -0700 > > "Paul E. McKenney" wrote: > > > > > Hello! > > > > > > This

Re: [PATCH tip/core/rcu 0/21] Contention reduction for v4.18

On Mon, 14 May 2018 09:09:07 -0700 "Paul E. McKenney" wrote: > On Mon, May 14, 2018 at 04:42:33PM +1000, Nicholas Piggin wrote: > > On Sun, 22 Apr 2018 20:02:58 -0700 > > "Paul E. McKenney" wrote: > > > > > Hello! > > > > > > This series reduces lock contention on the root rcu_node > > >

linux-next: Signed-off-by missing for commit in the pm tree

Hi Rafael, Commit e689ba60f1f0 ("Merge branch 'opp/genpd-pstate-updates' of git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm") is missing a Signed-off-by from its author and committer. This is probably because (despite its description) this is not a merge commit - it seems to have

linux-next: Signed-off-by missing for commit in the pm tree

Hi Rafael, Commit e689ba60f1f0 ("Merge branch 'opp/genpd-pstate-updates' of git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm") is missing a Signed-off-by from its author and committer. This is probably because (despite its description) this is not a merge commit - it seems to have

Re: [RFC PATCH 02/10] dt-bindings: devfreq: rk3399_dmc: Add rockchip,pmu phandle.

Hi, On 2018년 05월 15일 06:16, Enric Balletbo i Serra wrote: > The Rockchip DMC (Dynamic Memory Interface) needs to access to the PMU > general register files to know the DRAM type, so add a phandle to the > syscon that manages these registers. > > Signed-off-by: Enric Balletbo i Serra

Re: [RFC PATCH 02/10] dt-bindings: devfreq: rk3399_dmc: Add rockchip,pmu phandle.

Hi, On 2018년 05월 15일 06:16, Enric Balletbo i Serra wrote: > The Rockchip DMC (Dynamic Memory Interface) needs to access to the PMU > general register files to know the DRAM type, so add a phandle to the > syscon that manages these registers. > > Signed-off-by: Enric Balletbo i Serra > --- > >

Re: [RFC PATCH 03/10] devfreq: rk3399_dmc: Pass ODT and auto power down parameters to TF-A.

Hi, On 2018년 05월 15일 06:16, Enric Balletbo i Serra wrote: > Trusted Firmware-A (TF-A) for rk3399 implements a SiP call to get the > on-die termination (ODT) and auto power down parameters from kernel, > this patch adds the functionality to do this. Also, if DDR clock > frequency is lower than the

Re: [RFC PATCH 03/10] devfreq: rk3399_dmc: Pass ODT and auto power down parameters to TF-A.

Hi, On 2018년 05월 15일 06:16, Enric Balletbo i Serra wrote: > Trusted Firmware-A (TF-A) for rk3399 implements a SiP call to get the > on-die termination (ODT) and auto power down parameters from kernel, > this patch adds the functionality to do this. Also, if DDR clock > frequency is lower than the

Re: [PATCH] KVM: fix spelling mistake: "cop_unsuable" -> "cop_unusable"

On Mon, May 14, 2018 at 06:23:50PM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in debugfs_entries text > > Signed-off-by: Colin Ian King Adding KVM folk. Its a fairly trivial change so I'll just take

Re: [PATCH] KVM: fix spelling mistake: "cop_unsuable" -> "cop_unusable"

On Mon, May 14, 2018 at 06:23:50PM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in debugfs_entries text > > Signed-off-by: Colin Ian King Adding KVM folk. Its a fairly trivial change so I'll just take it as a fix via the MIPS tree unless anybody objects.

Re: [PATCH] i2c: hix5hd2: remove some dead code

On Wed, May 09, 2018 at 09:46:03PM +0200, Peter Rosin wrote: > The else branch cannot be taken as i will always equal num. > Get rid of the whole construct. > > Signed-off-by: Peter Rosin Applied to for-next, thanks! signature.asc Description: PGP signature

Re: [PATCH] i2c: hix5hd2: remove some dead code

On Wed, May 09, 2018 at 09:46:03PM +0200, Peter Rosin wrote: > The else branch cannot be taken as i will always equal num. > Get rid of the whole construct. > > Signed-off-by: Peter Rosin Applied to for-next, thanks! signature.asc Description: PGP signature

Re: [PATCH v2] arm64: dts: qcom: Collapse usb support into one node

Quoting Yossi Mansharoff (2018-04-17 06:56:30) > We currently have three device nodes for the same USB hardware > block, as evident by the reuse of the same reg address multiple > times. Now that the chipidea driver fully supports OTG with the > MSM wrapper we can collapse all these nodes into one

Re: [PATCH v2] arm64: dts: qcom: Collapse usb support into one node

Quoting Yossi Mansharoff (2018-04-17 06:56:30) > We currently have three device nodes for the same USB hardware > block, as evident by the reuse of the same reg address multiple > times. Now that the chipidea driver fully supports OTG with the > MSM wrapper we can collapse all these nodes into one

Re: [tip:x86/pti 14/14] arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0x51: unreachable instruction

On Mon, May 14, 2018 at 09:44:48PM +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti > head: 51bad67ffbce0aaa44579f84ef5d05597054ec6a > commit: 51bad67ffbce0aaa44579f84ef5d05597054ec6a [14/14] x86/asm: Pad > assembly functions with

Re: [tip:x86/pti 14/14] arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0x51: unreachable instruction

On Mon, May 14, 2018 at 09:44:48PM +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti > head: 51bad67ffbce0aaa44579f84ef5d05597054ec6a > commit: 51bad67ffbce0aaa44579f84ef5d05597054ec6a [14/14] x86/asm: Pad > assembly functions with

Re: [PATCH 3.18 00/23] 3.18.109-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.109 release. > There are 23 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 3.18 00/23] 3.18.109-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.109 release. > There are 23 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.4 00/56] 4.4.132-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.132 release. > There are 56 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.4 00/56] 4.4.132-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.132 release. > There are 56 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 00/36] 4.9.100-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.100 release. > There are 36 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 00/36] 4.9.100-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.100 release. > There are 36 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.14 00/62] 4.14.41-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.41 release. > There are 62 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.14 00/62] 4.14.41-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.41 release. > There are 62 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.16 00/72] 4.16.9-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.16.9 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.16 00/72] 4.16.9-stable review

On 05/14/2018 12:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.16.9 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH 2/2] ARM: dts: chromecast: use PWM for LEDs

Control the Chromecast's two LEDs using PWM instead of GPIO pins. This allows for variable brightness. Signed-off-by: Thomas Hebb --- .../boot/dts/berlin2cd-google-chromecast.dts | 20 ++- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git

[PATCH 1/2] pwm: berlin: Don't use broken prescaler values

Six of the eight prescaler values available for Berlin PWM are not true prescalers but rather internal shifts that throw away the high bits of TCNT. Currently, we attempt to use those high bits, leading to erratic behavior. Restrict the prescaler configurations we select to only the two that

[PATCH 2/2] ARM: dts: chromecast: use PWM for LEDs

Control the Chromecast's two LEDs using PWM instead of GPIO pins. This allows for variable brightness. Signed-off-by: Thomas Hebb --- .../boot/dts/berlin2cd-google-chromecast.dts | 20 ++- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git

[PATCH 1/2] pwm: berlin: Don't use broken prescaler values

Six of the eight prescaler values available for Berlin PWM are not true prescalers but rather internal shifts that throw away the high bits of TCNT. Currently, we attempt to use those high bits, leading to erratic behavior. Restrict the prescaler configurations we select to only the two that

Re: [PATCH v4 6/6] devfreq: rk3399_dmc: fix spelling mistakes.

On 2018년 05월 14일 19:23, MyungJoo Ham wrote: >> Fix some spelling mistakes in error and debug messages. >> >> Signed-off-by: Enric Balletbo i Serra >> --- >> >> Changes in v4: >> - [6/6] Introduce this new patch that fixes some spelling. >> >> Changes in v3: None >>

Re: [PATCH v4 6/6] devfreq: rk3399_dmc: fix spelling mistakes.

On 2018년 05월 14일 19:23, MyungJoo Ham wrote: >> Fix some spelling mistakes in error and debug messages. >> >> Signed-off-by: Enric Balletbo i Serra >> --- >> >> Changes in v4: >> - [6/6] Introduce this new patch that fixes some spelling. >> >> Changes in v3: None >> Changes in v2: None >> >>

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

Hi Jakub, On Mon, 14 May 2018 13:41:40 -0700 Jakub Kicinski wrote: > > On Mon, 14 May 2018 11:57:00 +1000, Stephen Rothwell wrote: > > diff --cc tools/lib/bpf/libbpf.c > > index 8da4eeb101a6,df54c4c9e48a.. > > --- a/tools/lib/bpf/libbpf.c > > +++

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

Hi Jakub, On Mon, 14 May 2018 13:41:40 -0700 Jakub Kicinski wrote: > > On Mon, 14 May 2018 11:57:00 +1000, Stephen Rothwell wrote: > > diff --cc tools/lib/bpf/libbpf.c > > index 8da4eeb101a6,df54c4c9e48a.. > > --- a/tools/lib/bpf/libbpf.c > > +++ b/tools/lib/bpf/libbpf.c > > @@@

[PATCH] ARM: dts: chromecast: override bad bootloader memory info

On the Chromecast, the bootloader provides us with an ATAG_MEM of start=0x0100 and size=0x3eff8000. This is clearly incorrect, as the range given encompasses nearly a GiB but the Chromecast only has 512MiB of RAM! Additionally, this causes the kernel to be decompressed at 0x8000, below the

[PATCH] ARM: dts: chromecast: override bad bootloader memory info

On the Chromecast, the bootloader provides us with an ATAG_MEM of start=0x0100 and size=0x3eff8000. This is clearly incorrect, as the range given encompasses nearly a GiB but the Chromecast only has 512MiB of RAM! Additionally, this causes the kernel to be decompressed at 0x8000, below the

[PATCH] Documentation: arm: clean up Marvell Berlin family info

Remove dead links, make spacing consistent, and note that the family was acquired by Synaptics in 2017. Signed-off-by: Thomas Hebb --- Documentation/arm/Marvell/README | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git

[PATCH] Documentation: arm: clean up Marvell Berlin family info

Remove dead links, make spacing consistent, and note that the family was acquired by Synaptics in 2017. Signed-off-by: Thomas Hebb --- Documentation/arm/Marvell/README | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/Documentation/arm/Marvell/README

Re: [PATCH ghak81 RFC V2 5/5] audit: collect audit task parameters

On Sat, May 12, 2018 at 9:58 PM, Richard Guy Briggs wrote: > The audit-related parameters in struct task_struct should ideally be > collected together and accessed through a standard audit API. > > Collect the existing loginuid, sessionid and audit_context together in a > new

Re: [PATCH ghak81 RFC V2 5/5] audit: collect audit task parameters

On Sat, May 12, 2018 at 9:58 PM, Richard Guy Briggs wrote: > The audit-related parameters in struct task_struct should ideally be > collected together and accessed through a standard audit API. > > Collect the existing loginuid, sessionid and audit_context together in a > new struct

Re: linux-next: Tree for May 14

Hi Andy, On Mon, 14 May 2018 20:14:57 +0300 Andy Shevchenko wrote: > > On Mon, May 14, 2018 at 3:40 PM, Stephen Rothwell > wrote: > > On Mon, 14 May 2018 10:26:07 +0300 Andy Shevchenko > > wrote: > > > BTW, the

Re: linux-next: Tree for May 14

Hi Andy, On Mon, 14 May 2018 20:14:57 +0300 Andy Shevchenko wrote: > > On Mon, May 14, 2018 at 3:40 PM, Stephen Rothwell > wrote: > > On Mon, 14 May 2018 10:26:07 +0300 Andy Shevchenko > > wrote: > > > BTW, the drivers-x86 tree I have is > > > >

Re: [PATCH ghak81 RFC V2 4/5] audit: use inline function to set audit context

On Sat, May 12, 2018 at 9:58 PM, Richard Guy Briggs wrote: > Recognizing that the audit context is an internal audit value, use an > access function to set the audit context pointer for the task > rather than reaching directly into the task struct to set it. > > Signed-off-by:

Re: [PATCH ghak81 RFC V2 4/5] audit: use inline function to set audit context

On Sat, May 12, 2018 at 9:58 PM, Richard Guy Briggs wrote: > Recognizing that the audit context is an internal audit value, use an > access function to set the audit context pointer for the task > rather than reaching directly into the task struct to set it. > > Signed-off-by: Richard Guy Briggs

Re: [PATCH 2/2] x86/mm: Introduce 'no5lvl' kernel parameter

On Sun, May 13, 2018 at 09:55:00PM +, Thomas Gleixner wrote: > On Fri, 11 May 2018, Kirill A. Shutemov wrote: > > --- a/arch/x86/kernel/cpu/common.c > > +++ b/arch/x86/kernel/cpu/common.c > > @@ -1008,6 +1008,12 @@ static void __init early_identify_cpu(struct > > cpuinfo_x86 *c) > > */ >

Re: [PATCH 2/2] x86/mm: Introduce 'no5lvl' kernel parameter

On Sun, May 13, 2018 at 09:55:00PM +, Thomas Gleixner wrote: > On Fri, 11 May 2018, Kirill A. Shutemov wrote: > > --- a/arch/x86/kernel/cpu/common.c > > +++ b/arch/x86/kernel/cpu/common.c > > @@ -1008,6 +1008,12 @@ static void __init early_identify_cpu(struct > > cpuinfo_x86 *c) > > */ >

Re: [PATCH 2/2] media: i2c: mt9t112: Add device tree support

Hi Jacopo, On Mon, May 14, 2018 at 04:30:44PM +0200, jacopo mondi wrote: > Hi Sakari, > > On Mon, May 07, 2018 at 12:32:19PM +0300, Sakari Ailus wrote: > > Hi Jacopo, > > > > On Wed, Apr 25, 2018 at 01:00:14PM +0200, Jacopo Mondi wrote: > > [snip] > > > > static int mt9t112_probe(struct

Re: [PATCH 2/2] media: i2c: mt9t112: Add device tree support

Hi Jacopo, On Mon, May 14, 2018 at 04:30:44PM +0200, jacopo mondi wrote: > Hi Sakari, > > On Mon, May 07, 2018 at 12:32:19PM +0300, Sakari Ailus wrote: > > Hi Jacopo, > > > > On Wed, Apr 25, 2018 at 01:00:14PM +0200, Jacopo Mondi wrote: > > [snip] > > > > static int mt9t112_probe(struct

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