Re: [PATCH v4 05/19] afs: convert to new i_version API

On Tue, 2018-01-02 at 17:20 +, David Howells wrote: > Jeff Layton wrote: > > > Note that AFS has quite a different definition for this counter. AFS > > only increments it on changes to the data, not for the metadata. > > This also applies to AFS directories: create,

Re: [PATCH v4 05/19] afs: convert to new i_version API

On Tue, 2018-01-02 at 17:20 +, David Howells wrote: > Jeff Layton wrote: > > > Note that AFS has quite a different definition for this counter. AFS > > only increments it on changes to the data, not for the metadata. > > This also applies to AFS directories: create, mkdir, unlink, rmdir,

Re: [PATCH 2/2] MIPS: Remove a warning when PHYS_OFFSET is 0x0

Hi James, On Tue, Jan 2, 2018 at 10:31 AM, James Hogan wrote: > On Tue, Dec 26, 2017 at 12:37:14PM +0100, Mathieu Malaterre wrote: >> Rewrite the comparison in `else if` statement, case where `min_low_pfn > >> ARCH_PFN_OFFSET` has already been checked in the first `if`

Re: [PATCH 2/2] MIPS: Remove a warning when PHYS_OFFSET is 0x0

Hi James, On Tue, Jan 2, 2018 at 10:31 AM, James Hogan wrote: > On Tue, Dec 26, 2017 at 12:37:14PM +0100, Mathieu Malaterre wrote: >> Rewrite the comparison in `else if` statement, case where `min_low_pfn > >> ARCH_PFN_OFFSET` has already been checked in the first `if` statement: >> >> if

[PATCH v2 2/2] MIPS: Remove a warning when PHYS_OFFSET is 0x0

Rewrite the comparison in `else if` statement, case where `min_low_pfn > ARCH_PFN_OFFSET` has already been checked in the first `if` statement: if (min_low_pfn > ARCH_PFN_OFFSET) { Fix non-fatal warning during compilation using W=1: arch/mips/kernel/setup.c: In function ‘bootmem_init’:

[PATCH v2 2/2] MIPS: Remove a warning when PHYS_OFFSET is 0x0

Rewrite the comparison in `else if` statement, case where `min_low_pfn > ARCH_PFN_OFFSET` has already been checked in the first `if` statement: if (min_low_pfn > ARCH_PFN_OFFSET) { Fix non-fatal warning during compilation using W=1: arch/mips/kernel/setup.c: In function ‘bootmem_init’:

[PATCH v2 1/2] MIPS: Make declaration for function `memory_region_available` static

Fix non-fatal warning during compilation using W=1: arch/mips/kernel/setup.c:158:13: warning: no previous prototype for ‘memory_region_available’ [-Wmissing-prototypes] bool __init memory_region_available(phys_addr_t start, phys_addr_t size) ^~~ Signed-off-by:

[PATCH v2 1/2] MIPS: Make declaration for function `memory_region_available` static

Fix non-fatal warning during compilation using W=1: arch/mips/kernel/setup.c:158:13: warning: no previous prototype for ‘memory_region_available’ [-Wmissing-prototypes] bool __init memory_region_available(phys_addr_t start, phys_addr_t size) ^~~ Signed-off-by:

correct section for cpu_tss_rw?

(emailing the folks listed from running `./scripts/get_maintainer.pl -f` on arch/x86/kernel/process.c, arch/x86/include/asm/processor.h, and include/linux/percpu-defs.h) Clang emits the following warning: arch/x86/kernel/process.c:50:11: warning: section does not match previous declaration

correct section for cpu_tss_rw?

(emailing the folks listed from running `./scripts/get_maintainer.pl -f` on arch/x86/kernel/process.c, arch/x86/include/asm/processor.h, and include/linux/percpu-defs.h) Clang emits the following warning: arch/x86/kernel/process.c:50:11: warning: section does not match previous declaration

Re: [PATCH 05/12] openvswitch: drop unneeded newline

From: Julia Lawall Date: Wed, 27 Dec 2017 15:51:38 +0100 > OVS_NLERR prints a newline at the end of the message string, so the > message string does not need to include a newline explicitly. Done > using Coccinelle. > > Signed-off-by: Julia Lawall

Re: [PATCH 05/12] openvswitch: drop unneeded newline

From: Julia Lawall Date: Wed, 27 Dec 2017 15:51:38 +0100 > OVS_NLERR prints a newline at the end of the message string, so the > message string does not need to include a newline explicitly. Done > using Coccinelle. > > Signed-off-by: Julia Lawall Applied.

Re: [PATCH 03/12] net: dccp: drop unneeded newline

From: Julia Lawall Date: Wed, 27 Dec 2017 15:51:36 +0100 > DCCP_CRIT prints some other text and then a newline after the message > string, so the message string does not need to include a newline > explicitly. Done using Coccinelle. > > Signed-off-by: Julia Lawall

Re: [PATCH 03/12] net: dccp: drop unneeded newline

From: Julia Lawall Date: Wed, 27 Dec 2017 15:51:36 +0100 > DCCP_CRIT prints some other text and then a newline after the message > string, so the message string does not need to include a newline > explicitly. Done using Coccinelle. > > Signed-off-by: Julia Lawall Applied.

Re: [PATCH v2 02/21] nvmem: Introduce devm_nvmem_(un)register()

On Tue, Jan 2, 2018 at 3:44 AM, Srinivas Kandagatla wrote: > Thanks for the patch, > > On 01/01/18 23:22, Andrey Smirnov wrote: >> >> Introduce devm_nvmem_register()/devm_nvmem_unregister() to make >> .remove() unnecessary in trivial drivers. >> >> Cc: Srinivas

Re: [PATCH v2 02/21] nvmem: Introduce devm_nvmem_(un)register()

On Tue, Jan 2, 2018 at 3:44 AM, Srinivas Kandagatla wrote: > Thanks for the patch, > > On 01/01/18 23:22, Andrey Smirnov wrote: >> >> Introduce devm_nvmem_register()/devm_nvmem_unregister() to make >> .remove() unnecessary in trivial drivers. >> >> Cc: Srinivas Kandagatla >> Cc: Heiko Stuebner

Re: [PATCH v2 01/21] nvmem: core: Allow specifying device name verbatim

On Tue, Jan 2, 2018 at 3:44 AM, Srinivas Kandagatla wrote: > Thanks for the Patch, > > On 01/01/18 23:22, Andrey Smirnov wrote: >> >> Add code to allow avoid having nvmem core append a numeric suffix to >> the end of the name by passing config->id of -1. >> >> Cc:

Re: [PATCH v2 01/21] nvmem: core: Allow specifying device name verbatim

On Tue, Jan 2, 2018 at 3:44 AM, Srinivas Kandagatla wrote: > Thanks for the Patch, > > On 01/01/18 23:22, Andrey Smirnov wrote: >> >> Add code to allow avoid having nvmem core append a numeric suffix to >> the end of the name by passing config->id of -1. >> >> Cc: Srinivas Kandagatla >> Cc:

[PATCH v2] platform/x86: silead_dmi: Add entry for the Teclast X98 Plus II

Add touchscreen platform data for the Teclast X98 Plus II tablet. Signed-off-by: Paul Cercueil Acked-by: Hans de Goede --- drivers/platform/x86/silead_dmi.c | 24 1 file changed, 24 insertions(+) v2: Rebased on top of

Re: [PATCH v17 0/5] ZII RAVE platform driver

On Tue, Jan 2, 2018 at 7:17 AM, Lee Jones wrote: > On Wed, 20 Dec 2017, Andrey Smirnov wrote: > >> Everyone: >> >> This patch series is v17 of the driver for supervisory processor found >> on RAVE series of devices from ZII. Supervisory processor is a PIC >> microcontroller

[PATCH v2] platform/x86: silead_dmi: Add entry for the Teclast X98 Plus II

Add touchscreen platform data for the Teclast X98 Plus II tablet. Signed-off-by: Paul Cercueil Acked-by: Hans de Goede --- drivers/platform/x86/silead_dmi.c | 24 1 file changed, 24 insertions(+) v2: Rebased on top of

Re: [PATCH v17 0/5] ZII RAVE platform driver

On Tue, Jan 2, 2018 at 7:17 AM, Lee Jones wrote: > On Wed, 20 Dec 2017, Andrey Smirnov wrote: > >> Everyone: >> >> This patch series is v17 of the driver for supervisory processor found >> on RAVE series of devices from ZII. Supervisory processor is a PIC >> microcontroller connected to various

RE: [PATCH v2] MIPS: Add nonxstack=on|off kernel parameter

Hi Miodrag, > > I presume what you > > actually want here is for the kernel to lie & indicate to whatever part > > of Android that performs this check that the stack is non-executable > > even when it is really executable? > > Basically yes, because we do not have other options at this point.

RE: [PATCH v2] MIPS: Add nonxstack=on|off kernel parameter

Hi Miodrag, > > I presume what you > > actually want here is for the kernel to lie & indicate to whatever part > > of Android that performs this check that the stack is non-executable > > even when it is really executable? > > Basically yes, because we do not have other options at this point.

Re: [PATCH v2 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC

On 1/2/2018 12:12 PM, Keith Busch wrote: > On Tue, Jan 02, 2018 at 08:25:08AM -0500, Sinan Kaya wrote: >>> 2. A DPC event suppresses the error message required for the Linux >>> AER driver to run. How can AER and DPC run concurrently? >>> >> >> As we briefly discussed in previous email exchanges,

Re: [PATCH v2 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC

On 1/2/2018 12:12 PM, Keith Busch wrote: > On Tue, Jan 02, 2018 at 08:25:08AM -0500, Sinan Kaya wrote: >>> 2. A DPC event suppresses the error message required for the Linux >>> AER driver to run. How can AER and DPC run concurrently? >>> >> >> As we briefly discussed in previous email exchanges,

Re: [PATCH 4.9 00/75] 4.9.74-stable review

From: Neal Cardwell Date: Tue, 2 Jan 2018 11:57:59 -0500 > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: >> This is the start of the stable review cycle for the 4.9.74 release. >> There are 75 patches in this series, all will be

Re: [RFC PATCH v2 1/1] drm/tegra: sor: Fix hang on tegra124 due to NULL clk_out

On 20/12/17 18:15, Thierry Reding wrote: > On Wed, Dec 20, 2017 at 11:32:23AM +, Guillaume Tucker wrote: >> When neither HDMI nor DP is supported such as on the tegra124, the >> sor->clk_out is not initialised and remains NULL. In this case, the >> parent clock can't be assigned to it so

Re: [PATCH 4.9 00/75] 4.9.74-stable review

From: Neal Cardwell Date: Tue, 2 Jan 2018 11:57:59 -0500 > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: >> This is the start of the stable review cycle for the 4.9.74 release. >> There are 75 patches in this series, all will be posted as a response >> to this one. If anyone has

Re: [RFC PATCH v2 1/1] drm/tegra: sor: Fix hang on tegra124 due to NULL clk_out

On 20/12/17 18:15, Thierry Reding wrote: > On Wed, Dec 20, 2017 at 11:32:23AM +, Guillaume Tucker wrote: >> When neither HDMI nor DP is supported such as on the tegra124, the >> sor->clk_out is not initialised and remains NULL. In this case, the >> parent clock can't be assigned to it so

Re: [PATCH v4 0/7] ARM: davinci: convert to common clock framework​

On 01/02/2018 11:10 AM, David Lechner wrote: and add "earlyprintk" to the kernel command line options. The "clk_ignore_unused" command line option could be useful as well

Re: [PATCH v4 0/7] ARM: davinci: convert to common clock framework​

On 01/02/2018 11:10 AM, David Lechner wrote: and add "earlyprintk" to the kernel command line options. The "clk_ignore_unused" command line option could be useful as well

cgroups(7): documenting cgroups v2 thread mode

Hello Tejun and all, To date, the cgroups(7) manual page does not document thread mode (added in Linux 4.14). Furthermore, the documentation in Documentation/cgroup-v2.txt is, I think, a little thin. I have attempted to address this by adding some extensive documentation to the cgroups(7)

cgroups(7): documenting cgroups v2 thread mode

Hello Tejun and all, To date, the cgroups(7) manual page does not document thread mode (added in Linux 4.14). Furthermore, the documentation in Documentation/cgroup-v2.txt is, I think, a little thin. I have attempted to address this by adding some extensive documentation to the cgroups(7)

Re: [PATCH -next] xen/pvcalls: use GFP_ATOMIC under spin lock

On 12/27/2017 10:46 PM, Wei Yongjun wrote: > A spin lock is taken here so we should use GFP_ATOMIC. > > Fixes: 9774c6cca266 ("xen/pvcalls: implement accept command") > Signed-off-by: Wei Yongjun Applied to for-linus-4.15 -boris

Re: [PATCH -next] xen/pvcalls: use GFP_ATOMIC under spin lock

On 12/27/2017 10:46 PM, Wei Yongjun wrote: > A spin lock is taken here so we should use GFP_ATOMIC. > > Fixes: 9774c6cca266 ("xen/pvcalls: implement accept command") > Signed-off-by: Wei Yongjun Applied to for-linus-4.15 -boris

cgroups(7): documenting cgroup.stat

Hello Roman, I wish to add documentation to cgroups(7) for the cgroup.stat file that you added in Linux 4.14. I wrote some text based on your text added to the cgroup-v2.txt file, but added some pieces, and also have a question (see below). The plain-text version for (easy review) is shown below.

cgroups(7): documenting cgroup.stat

Hello Roman, I wish to add documentation to cgroups(7) for the cgroup.stat file that you added in Linux 4.14. I wrote some text based on your text added to the cgroup-v2.txt file, but added some pieces, and also have a question (see below). The plain-text version for (easy review) is shown below.

Re: [PATCH 4.9 00/75] 4.9.74-stable review

On Tue, Jan 02, 2018 at 08:49:05AM -0800, Guenter Roeck wrote: > On Mon, Jan 01, 2018 at 03:31:37PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.9 00/75] 4.9.74-stable review

On Tue, Jan 02, 2018 at 08:49:05AM -0800, Guenter Roeck wrote: > On Mon, Jan 01, 2018 at 03:31:37PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one.

cgroups(7): documenting cgroups v2 delegation

Hello Tejun and Serge The delegation feature of cgroups v2 has of course been around for a while now, but was not documented so far in cgroups(7). I have written some text to describe the delegation feature. I would be happy to receive suggestions for fixes, improvements, or corrections to

cgroups(7): documenting cgroups v2 delegation

Hello Tejun and Serge The delegation feature of cgroups v2 has of course been around for a while now, but was not documented so far in cgroups(7). I have written some text to describe the delegation feature. I would be happy to receive suggestions for fixes, improvements, or corrections to

Re: [alsa-devel] [PATCH 15/27] ALSA: hda - Use timecounter_initialize interface

On Tue, Jan 02, 2018 at 11:15:45AM -0600, Pierre-Louis Bossart wrote: > I wrote the code for HDaudio and I remember wasting time trying to figure > out the gory details of the cycle counter stuff when all I wanted was a > conversion from a 24MHz counter to ns values using a 125/3 operation in the

Re: [alsa-devel] [PATCH 15/27] ALSA: hda - Use timecounter_initialize interface

On Tue, Jan 02, 2018 at 11:15:45AM -0600, Pierre-Louis Bossart wrote: > I wrote the code for HDaudio and I remember wasting time trying to figure > out the gory details of the cycle counter stuff when all I wanted was a > conversion from a 24MHz counter to ns values using a 125/3 operation in the

cgroups(7): extending man-pages documentation for cgroups v2

Hello Tejun (and Roman and Serge), There are some older features, as well as new features in cgroups v2 that have not so far been documented in the cgroups(7) manual page. I have been working on patches to add documentation for these features, and the man-pages branch containing these patches

cgroups(7): extending man-pages documentation for cgroups v2

Hello Tejun (and Roman and Serge), There are some older features, as well as new features in cgroups v2 that have not so far been documented in the cgroups(7) manual page. I have been working on patches to add documentation for these features, and the man-pages branch containing these patches

Re: [PATCH 4.9 00/75] 4.9.74-stable review

On Tue, Jan 02, 2018 at 11:57:59AM -0500, Neal Cardwell wrote: > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a

Re: [PATCH 4.9 00/75] 4.9.74-stable review

On Tue, Jan 02, 2018 at 11:57:59AM -0500, Neal Cardwell wrote: > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency

On 1/2/2018 1:10 PM, Randy Dunlap wrote: >>> config ACPI_I2C_OPREGION >>> bool "ACPI I2C Operation region support" >>> - depends on I2C=y && ACPI >>> + depends on I2C && ACPI >>> default y >>> help >>> Say Y here if you want to enable ACPI I2C operation region support. >>>

Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency

On 1/2/2018 1:10 PM, Randy Dunlap wrote: >>> config ACPI_I2C_OPREGION >>> bool "ACPI I2C Operation region support" >>> - depends on I2C=y && ACPI >>> + depends on I2C && ACPI >>> default y >>> help >>> Say Y here if you want to enable ACPI I2C operation region support. >>>

Re: BUG: unable to handle kernel paging request in ipcget

On Sat, Dec 23, 2017 at 2:07 AM, Dmitry Vyukov wrote: > On Sat, Dec 23, 2017 at 10:59 AM, Manfred Spraul > wrote: >> Hi, >> >> On 12/23/2017 08:33 AM, syzbot wrote: >>> >>> Hello, >>> >>> syzkaller hit the following crash on >>>

Re: BUG: unable to handle kernel paging request in ipcget

On Sat, Dec 23, 2017 at 2:07 AM, Dmitry Vyukov wrote: > On Sat, Dec 23, 2017 at 10:59 AM, Manfred Spraul > wrote: >> Hi, >> >> On 12/23/2017 08:33 AM, syzbot wrote: >>> >>> Hello, >>> >>> syzkaller hit the following crash on >>> 6084b576dca2e898f5c101baef151f7bfdbb606d >>>

Re: [PATCH v6 4/5] clk: aspeed: Register gated clocks

On 12/30, Benjamin Herrenschmidt wrote: > On Tue, 2017-12-26 at 17:32 -0800, Stephen Boyd wrote: > > > I noticed we do have a few i2c based clock drivers... how are they ever > > > supposed to work ? i2c bus controllers are allowed to sleep and the i2c > > > core takes mutexes... > > > > We have

Re: [PATCH v6 4/5] clk: aspeed: Register gated clocks

On 12/30, Benjamin Herrenschmidt wrote: > On Tue, 2017-12-26 at 17:32 -0800, Stephen Boyd wrote: > > > I noticed we do have a few i2c based clock drivers... how are they ever > > > supposed to work ? i2c bus controllers are allowed to sleep and the i2c > > > core takes mutexes... > > > > We have

Re: [PATCH v2 0/2] clk: qcom: MISC RCG changes for SDM845

On 01/02, Amit Nischal wrote: > Changes in v2: > * Changed usage of clk_hw_is_prepared() to __clk_is_enabled() > in clk_rcg2_shared_ops to fix build test error. Please change it to read the hardware directly and not use __clk_is_enabled() or clk_hw_is_prepared(). -- Qualcomm Innovation

Re: [PATCH v2 0/2] clk: qcom: MISC RCG changes for SDM845

On 01/02, Amit Nischal wrote: > Changes in v2: > * Changed usage of clk_hw_is_prepared() to __clk_is_enabled() > in clk_rcg2_shared_ops to fix build test error. Please change it to read the hardware directly and not use __clk_is_enabled() or clk_hw_is_prepared(). -- Qualcomm Innovation

[GIT PULL 0/5] EFI updates for v4.16

The following changes since commit 30a7acd573899fd8b8ac39236eff6468b195ac7d: Linux 4.15-rc6 (2017-12-31 14:47:43 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next for you to fetch changes up to

[GIT PULL 0/5] EFI updates for v4.16

The following changes since commit 30a7acd573899fd8b8ac39236eff6468b195ac7d: Linux 4.15-rc6 (2017-12-31 14:47:43 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next for you to fetch changes up to

[PATCH 1/5] efi/capsule-loader: pr_err() strings should end with newlines

From: Arvind Yadav pr_err() messages should terminated with a new-line to avoid other messages being concatenated onto the end. Signed-off-by: Arvind Yadav Signed-off-by: Matt Fleming Signed-off-by: Ard Biesheuvel

[PATCH 1/5] efi/capsule-loader: pr_err() strings should end with newlines

From: Arvind Yadav pr_err() messages should terminated with a new-line to avoid other messages being concatenated onto the end. Signed-off-by: Arvind Yadav Signed-off-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/capsule-loader.c | 2 +- 1 file changed, 1

[PATCH 2/5] arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set

The UEFI memory map is a bit vague about how to interpret the EFI_MEMORY_XP attribute when it is combined with EFI_MEMORY_RP and/or EFI_MEMORY_WP, which have retroactively been redefined as cacheability attributes rather than permission attributes. So let's ignore EFI_MEMORY_XP if _RP and/or _WP

[PATCH 3/5] efi: Use PTR_ERR_OR_ZERO()

From: Vasyl Gomonovych Fix ptr_ret.cocci warnings: drivers/firmware/efi/efi.c:610:8-14: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Signed-off-by: Vasyl Gomonovych

[PATCH 3/5] efi: Use PTR_ERR_OR_ZERO()

From: Vasyl Gomonovych Fix ptr_ret.cocci warnings: drivers/firmware/efi/efi.c:610:8-14: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Signed-off-by: Vasyl Gomonovych Signed-off-by: Matt

[PATCH 2/5] arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set

The UEFI memory map is a bit vague about how to interpret the EFI_MEMORY_XP attribute when it is combined with EFI_MEMORY_RP and/or EFI_MEMORY_WP, which have retroactively been redefined as cacheability attributes rather than permission attributes. So let's ignore EFI_MEMORY_XP if _RP and/or _WP

[PATCH 5/5] efi: parse ARM error information value

From: Tyler Baicar ARM errors just print out the error information value, then the value needs to be manually decoded as per the UEFI spec. Add decoding of the ARM error information value so that the kernel logs capture all of the valid information at first glance. ARM

[PATCH 5/5] efi: parse ARM error information value

From: Tyler Baicar ARM errors just print out the error information value, then the value needs to be manually decoded as per the UEFI spec. Add decoding of the ARM error information value so that the kernel logs capture all of the valid information at first glance. ARM error information value

[PATCH 4/5] efi: move ARM CPER code to new file

From: Tyler Baicar The ARM CPER code is currently mixed in with the other CPER code. Move it to a new file to separate it from the rest of the CPER code. Signed-off-by: Tyler Baicar Cc: Matt Fleming Signed-off-by: Ard

[PATCH 4/5] efi: move ARM CPER code to new file

From: Tyler Baicar The ARM CPER code is currently mixed in with the other CPER code. Move it to a new file to separate it from the rest of the CPER code. Signed-off-by: Tyler Baicar Cc: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/Kconfig| 5 ++

Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency

On 01/02/2018 10:07 AM, Sinan Kaya wrote: > +linux-acpi > > On 11/22/2017 12:05 PM, Eric Auger wrote: >> If CONFIG_I2C=m we fail getting ACPI_I2C_OPREGION set. Let's >> make ACPI_I2C_OPREGION depend on I2C. >> >> Signed-off-by: Eric Auger >> --- >> drivers/i2c/Kconfig | 2

Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency

On 01/02/2018 10:07 AM, Sinan Kaya wrote: > +linux-acpi > > On 11/22/2017 12:05 PM, Eric Auger wrote: >> If CONFIG_I2C=m we fail getting ACPI_I2C_OPREGION set. Let's >> make ACPI_I2C_OPREGION depend on I2C. >> >> Signed-off-by: Eric Auger >> --- >> drivers/i2c/Kconfig | 2 +- >> 1 file changed,

Re: [PATCH] arm64: dts: angler: add pstore-ramoops support

On Wed, Dec 27, 2017 at 11:38 PM, wrote: > From: Zhuowei Zhang > > Support pstore-ramoops for retrieving kernel oops and panics after reboot. > > The address and configs are taken from the downstream kernel's device tree. > > Signed-off-by:

Re: [PATCH] arm64: dts: angler: add pstore-ramoops support

On Wed, Dec 27, 2017 at 11:38 PM, wrote: > From: Zhuowei Zhang > > Support pstore-ramoops for retrieving kernel oops and panics after reboot. > > The address and configs are taken from the downstream kernel's device tree. > > Signed-off-by: Zhuowei Zhang Reviewed-by: Kees Cook -Kees > ---

Re: [PATCH v5 03/78] xarray: Add the xa_lock to the radix_tree_root

On Tue, Dec 26, 2017 at 07:58:15PM -0800, Matthew Wilcox wrote: > On Tue, Dec 26, 2017 at 07:43:40PM -0800, Matthew Wilcox wrote: > > Also add the xa_lock() and xa_unlock() family of wrappers to make it > > easier to use the lock. If we could rely on -fplan9-extensions in > > the

Re: [PATCH v5 03/78] xarray: Add the xa_lock to the radix_tree_root

On Tue, Dec 26, 2017 at 07:58:15PM -0800, Matthew Wilcox wrote: > On Tue, Dec 26, 2017 at 07:43:40PM -0800, Matthew Wilcox wrote: > > Also add the xa_lock() and xa_unlock() family of wrappers to make it > > easier to use the lock. If we could rely on -fplan9-extensions in > > the

Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency

+linux-acpi On 11/22/2017 12:05 PM, Eric Auger wrote: > If CONFIG_I2C=m we fail getting ACPI_I2C_OPREGION set. Let's > make ACPI_I2C_OPREGION depend on I2C. > > Signed-off-by: Eric Auger > --- > drivers/i2c/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency

+linux-acpi On 11/22/2017 12:05 PM, Eric Auger wrote: > If CONFIG_I2C=m we fail getting ACPI_I2C_OPREGION set. Let's > make ACPI_I2C_OPREGION depend on I2C. > > Signed-off-by: Eric Auger > --- > drivers/i2c/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH] x86/Kconfig: remove stale comment for ARCH_HAS_REFCOUNT

On Fri, Dec 29, 2017 at 11:53 AM, Eric Biggers wrote: > From: Eric Biggers > > ARCH_HAS_REFCOUNT is no longer marked as broken ('if BROKEN'), so remove > the stale comment regarding it being broken. > > Signed-off-by: Eric Biggers >

Re: [PATCH] x86/Kconfig: remove stale comment for ARCH_HAS_REFCOUNT

On Fri, Dec 29, 2017 at 11:53 AM, Eric Biggers wrote: > From: Eric Biggers > > ARCH_HAS_REFCOUNT is no longer marked as broken ('if BROKEN'), so remove > the stale comment regarding it being broken. > > Signed-off-by: Eric Biggers > --- > arch/x86/Kconfig | 1 - > 1 file changed, 1 deletion(-)

Re: [PATCH] cgroup/cpuset: fix circular locking dependency

On Tue, Jan 02, 2018 at 09:44:08AM -0800, Paul E. McKenney wrote: > On Tue, Jan 02, 2018 at 08:16:56AM -0800, Tejun Heo wrote: > > Hello, > > > > On Fri, Dec 29, 2017 at 02:07:16AM +0530, Prateek Sood wrote: > > > task T is waiting for cpuset_mutex acquired > > > by kworker/2:1 > > > > > > sh

Re: [PATCH] cgroup/cpuset: fix circular locking dependency

On Tue, Jan 02, 2018 at 09:44:08AM -0800, Paul E. McKenney wrote: > On Tue, Jan 02, 2018 at 08:16:56AM -0800, Tejun Heo wrote: > > Hello, > > > > On Fri, Dec 29, 2017 at 02:07:16AM +0530, Prateek Sood wrote: > > > task T is waiting for cpuset_mutex acquired > > > by kworker/2:1 > > > > > > sh

Re: [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC

On 02/01/18 16:17, PrasannaKumar Muralidharan wrote: Hi Srinivas, On 2 January 2018 at 17:31, Srinivas Kandagatla wrote: On 28/12/17 21:29, Mathieu Malaterre wrote: This patchset bring support for read-only access to the JZ4780 efuse as found on MIPS

Re: [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC

On 02/01/18 16:17, PrasannaKumar Muralidharan wrote: Hi Srinivas, On 2 January 2018 at 17:31, Srinivas Kandagatla wrote: On 28/12/17 21:29, Mathieu Malaterre wrote: This patchset bring support for read-only access to the JZ4780 efuse as found on MIPS Creator CI20. To keep the driver as

[PATCH 1/6] slimbus: avoid null pointer dereference on msg

From: Colin Ian King The pointer msg is checked to see if it is null at the start of the function and jumps to the error exit label reterr that then dereferences msg when it prints a dev_err error message. Avoid this potential null pointer dereference by only printing

[PATCH 1/6] slimbus: avoid null pointer dereference on msg

From: Colin Ian King The pointer msg is checked to see if it is null at the start of the function and jumps to the error exit label reterr that then dereferences msg when it prints a dev_err error message. Avoid this potential null pointer dereference by only printing the error message if msg is

[PATCH 4/6] slimbus: Use GFP_ATOMIC under spin lock

From: Wei Yongjun A spin lock is taken here so we should use GFP_ATOMIC. Signed-off-by: Wei Yongjun Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/messaging.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 0/6] slimbus: sparse and CoverityScan fixes

From: Srinivas Kandagatla Hi Greg, Here are few patches which are submitted in the list few days back, these also fix some of the sparse errors reported. Thanks, Srini Colin Ian King (3): slimbus: avoid null pointer dereference on msg slimbus: fix retries

[PATCH 0/6] slimbus: sparse and CoverityScan fixes

From: Srinivas Kandagatla Hi Greg, Here are few patches which are submitted in the list few days back, these also fix some of the sparse errors reported. Thanks, Srini Colin Ian King (3): slimbus: avoid null pointer dereference on msg slimbus: fix retries comparison to correctly identify

[PATCH 4/6] slimbus: Use GFP_ATOMIC under spin lock

From: Wei Yongjun A spin lock is taken here so we should use GFP_ATOMIC. Signed-off-by: Wei Yongjun Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/messaging.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/slimbus/messaging.c b/drivers/slimbus/messaging.c

[PATCH 2/6] slimbus: fix retries comparison to correctly identify failed allocation

From: Colin Ian King Currently the check for too many retries fails because retries is actually -1 when the retry loop terminates if no pbuf can be allocated because of the post decrement on retries. Fix this by not comparing retries with zero but instead check if it

[PATCH 3/6] slimbus: make functions slim_ack_txn and slim_alloc_txbuf static

From: Colin Ian King The functions slim_ack_txn and slim_alloc_txbuf are local to the source and do not need to be in global scope, so make them static. Cleans up sparse warnings: symbol 'slim_ack_txn' was not declared. Should it be static? symbol 'slim_alloc_txbuf'

[PATCH 2/6] slimbus: fix retries comparison to correctly identify failed allocation

From: Colin Ian King Currently the check for too many retries fails because retries is actually -1 when the retry loop terminates if no pbuf can be allocated because of the post decrement on retries. Fix this by not comparing retries with zero but instead check if it is negative. Detected by

[PATCH 3/6] slimbus: make functions slim_ack_txn and slim_alloc_txbuf static

From: Colin Ian King The functions slim_ack_txn and slim_alloc_txbuf are local to the source and do not need to be in global scope, so make them static. Cleans up sparse warnings: symbol 'slim_ack_txn' was not declared. Should it be static? symbol 'slim_alloc_txbuf' was not declared. Should it

[PATCH 5/6] slimbus: Fix missing unlock on error in slim_msg_response()

From: Wei Yongjun Add the missing unlock before return from function slim_msg_response() in the error handling case. Signed-off-by: Wei Yongjun Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/messaging.c |

[PATCH 5/6] slimbus: Fix missing unlock on error in slim_msg_response()

From: Wei Yongjun Add the missing unlock before return from function slim_msg_response() in the error handling case. Signed-off-by: Wei Yongjun Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/messaging.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/slimbus/messaging.c

[PATCH 6/6] slimbus: qcom: Fix return value check in qcom_slim_probe()

From: Wei Yongjun In case of error, the function devm_ioremap_resource() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by: Wei Yongjun Signed-off-by: Srinivas

[PATCH 6/6] slimbus: qcom: Fix return value check in qcom_slim_probe()

From: Wei Yongjun In case of error, the function devm_ioremap_resource() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by: Wei Yongjun Signed-off-by: Srinivas Kandagatla --- drivers/slimbus/qcom-ctrl.c | 4 ++--

[PATCH v17 2/4] net: e100: Replace PCI pool old API

From: Romain Perier The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin

[PATCH v17 2/4] net: e100: Replace PCI pool old API

From: Romain Perier The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Acked-by: Jeff Kirsher Acked-by: David S. Miller Tested-by: Peter Senna Tschudin ---

[PATCH v17 0/4] Replace PCI pool by DMA pool API

by the dma pool API and remove the defines. Changes in v17: - Rebased series onto next-20180102 - Added Acked-by tags by David S. Miller on patches 02/04 and 03/04 Changes in v16: - Rebased series onto next-20171215 - I have fixed patch 04/04, so it can be applied - Added Acked-by for Bjorn

[PATCH v17 0/4] Replace PCI pool by DMA pool API

by the dma pool API and remove the defines. Changes in v17: - Rebased series onto next-20180102 - Added Acked-by tags by David S. Miller on patches 02/04 and 03/04 Changes in v16: - Rebased series onto next-20171215 - I have fixed patch 04/04, so it can be applied - Added Acked-by for Bjorn

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