Re: [PATCH V4 1/5] nvme: do atomically bit operations on nvme_request.flags

On Thu, Mar 08, 2018 at 02:19:27PM +0800, Jianchao Wang wrote: > Do atomically bit operations on nvme_request.flags instead of > regular read/write, then we could add other flags and set/clear > them safely. > > Signed-off-by: Jianchao Wang Looks good, assuming an

Re: [PATCH V4 1/5] nvme: do atomically bit operations on nvme_request.flags

On Thu, Mar 08, 2018 at 02:19:27PM +0800, Jianchao Wang wrote: > Do atomically bit operations on nvme_request.flags instead of > regular read/write, then we could add other flags and set/clear > them safely. > > Signed-off-by: Jianchao Wang Looks good, assuming an actual need for this shows up

Re: [PATCH 05/10] hwmon: generic-pwm-tachometer: Add generic PWM based tachometer

On 07.03.2018 16:20, Guenter Roeck wrote: On 03/07/2018 01:47 AM, Rajkumar Rampelli wrote: On Wednesday 28 February 2018 07:59 PM, Guenter Roeck wrote: On 02/27/2018 11:03 PM, Mikko Perttunen wrote: On 02/28/2018 08:12 AM, Rajkumar Rampelli wrote: On Wednesday 28 February 2018 11:28 AM,

Re: [PATCH 05/10] hwmon: generic-pwm-tachometer: Add generic PWM based tachometer

On 07.03.2018 16:20, Guenter Roeck wrote: On 03/07/2018 01:47 AM, Rajkumar Rampelli wrote: On Wednesday 28 February 2018 07:59 PM, Guenter Roeck wrote: On 02/27/2018 11:03 PM, Mikko Perttunen wrote: On 02/28/2018 08:12 AM, Rajkumar Rampelli wrote: On Wednesday 28 February 2018 11:28 AM,

Re: [PATCH v12 3/6] PCI/PORTDRV: Implement generic find service

On 2018-03-06 19:32, Sinan Kaya wrote: On 2/28/2018 12:04 PM, Oza Pawandeep wrote: +struct pcie_port_service_driver *pcie_port_find_service(struct pci_dev *dev, + u32 service) +{ + struct pcie_port_service_driver *drv = NULL; Remove

Re: [PATCH v12 3/6] PCI/PORTDRV: Implement generic find service

On 2018-03-06 19:32, Sinan Kaya wrote: On 2/28/2018 12:04 PM, Oza Pawandeep wrote: +struct pcie_port_service_driver *pcie_port_find_service(struct pci_dev *dev, + u32 service) +{ + struct pcie_port_service_driver *drv = NULL; Remove

[tip:x86/pti] x86/vsyscall/64: Drop "native" vsyscalls

Commit-ID: 076ca272a14cea558b1092ec85cea08510283f2a Gitweb: https://git.kernel.org/tip/076ca272a14cea558b1092ec85cea08510283f2a Author: Andy Lutomirski AuthorDate: Wed, 7 Mar 2018 11:12:27 -0800 Committer: Ingo Molnar CommitDate: Thu, 8 Mar 2018

[tip:x86/pti] x86/vsyscall/64: Drop "native" vsyscalls

Commit-ID: 076ca272a14cea558b1092ec85cea08510283f2a Gitweb: https://git.kernel.org/tip/076ca272a14cea558b1092ec85cea08510283f2a Author: Andy Lutomirski AuthorDate: Wed, 7 Mar 2018 11:12:27 -0800 Committer: Ingo Molnar CommitDate: Thu, 8 Mar 2018 06:48:15 +0100 x86/vsyscall/64: Drop

Re: [PATCH V2 3/5] genirq/affinity: move actual irq vector spread into one helper

Can you fix this up and resend? On Tue, Mar 06, 2018 at 12:28:32AM +0800, kbuild test robot wrote: > Hi Ming, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on tip/irq/core] > [also build test WARNING on v4.16-rc4 next-20180305] > [if your patch is

Re: [PATCH V2 3/5] genirq/affinity: move actual irq vector spread into one helper

Can you fix this up and resend? On Tue, Mar 06, 2018 at 12:28:32AM +0800, kbuild test robot wrote: > Hi Ming, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on tip/irq/core] > [also build test WARNING on v4.16-rc4 next-20180305] > [if your patch is

Re: [PATCH v2 1/2] dt-bindings: watchdog: Add Nuvoton NPCM description

On 5 March 2018 at 13:45, Joel Stanley wrote: > These bindings describe the watchdog IP as used by the Nuvoton NPCM750 > (Poleg) BMC SoC. > > Signed-off-by: Joel Stanley > --- > V2: Add optional timeout property > --- > .../bindings/watchdog/nuvoton,npcm-wdt.txt

Re: [PATCH v2 1/2] dt-bindings: watchdog: Add Nuvoton NPCM description

On 5 March 2018 at 13:45, Joel Stanley wrote: > These bindings describe the watchdog IP as used by the Nuvoton NPCM750 > (Poleg) BMC SoC. > > Signed-off-by: Joel Stanley > --- > V2: Add optional timeout property > --- > .../bindings/watchdog/nuvoton,npcm-wdt.txt | 28 >

[PATCH v5 3/3] arm64: dts: rockchip: kevin: Avoid wakeup when inserting the pen

Add wakeup event action for Pen Insert gpio key, to avoid wakeup when inserting the pen. Signed-off-by: Jeffy Chen Tested-by: Enric Balletbo i Serra --- Changes in v5: None Changes in v4: Include dt-binding gpio-keys.h Changes in v3:

[PATCH v5 3/3] arm64: dts: rockchip: kevin: Avoid wakeup when inserting the pen

Add wakeup event action for Pen Insert gpio key, to avoid wakeup when inserting the pen. Signed-off-by: Jeffy Chen Tested-by: Enric Balletbo i Serra --- Changes in v5: None Changes in v4: Include dt-binding gpio-keys.h Changes in v3: None Changes in v2: Specify wakeup event action instead of

Re: [PATCH V2 1/3] x86/efi: Call efi_delete_dummy_variable() during efi subsystem initialization

Hello Sai, On 5 March 2018 at 23:23, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Invoking efi_runtime_services() through efi_workqueue means all accesses > to efi_runtime_services() should be done after efi_rts_wq has been

Re: [PATCH V2 1/3] x86/efi: Call efi_delete_dummy_variable() during efi subsystem initialization

Hello Sai, On 5 March 2018 at 23:23, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Invoking efi_runtime_services() through efi_workqueue means all accesses > to efi_runtime_services() should be done after efi_rts_wq has been > created. efi_delete_dummy_variable() calls set_variable(),

Re: [PATCH V2] nvme-pci: assign separate irq vectors for adminq and ioq0

On Thu, Mar 01, 2018 at 09:10:42AM -0700, Keith Busch wrote: > On Thu, Mar 01, 2018 at 11:03:30PM +0800, Ming Lei wrote: > > If all CPUs for the 1st IRQ vector of admin queue are offline, then I > > guess NVMe can't work any more. > > Yikes, with respect to admin commands, it appears you're right

Re: [PATCH V2] nvme-pci: assign separate irq vectors for adminq and ioq0

On Thu, Mar 01, 2018 at 09:10:42AM -0700, Keith Busch wrote: > On Thu, Mar 01, 2018 at 11:03:30PM +0800, Ming Lei wrote: > > If all CPUs for the 1st IRQ vector of admin queue are offline, then I > > guess NVMe can't work any more. > > Yikes, with respect to admin commands, it appears you're right

Re: [PATCH 5/6] dma-mapping: support fsl-mc bus

On Tue, Mar 06, 2018 at 04:41:56AM +, Nipun Gupta wrote: > Sorry for asking a trivial question - looking into dma_configure() I see that > PCI is used in the start and the end of the API. > In the end part pci_put_host_bridge_device() is called. > So are two bus callbacks something like

Re: [PATCH 5/6] dma-mapping: support fsl-mc bus

On Tue, Mar 06, 2018 at 04:41:56AM +, Nipun Gupta wrote: > Sorry for asking a trivial question - looking into dma_configure() I see that > PCI is used in the start and the end of the API. > In the end part pci_put_host_bridge_device() is called. > So are two bus callbacks something like

Re: [PATCH] fix compilation of 64-bit kernel with 32-bit compiler

On Thu, Mar 08, 2018 at 01:11:26AM -0500, Mikulas Patocka wrote: > The patch b5bc2231b8ad4387c9641f235ca0ad8cd300b6df ("objtool: Add > retpoline validation") broke compiling 64-bit kernel with 32-bit compiler. > > This patch fixes the following error and a large number of "can't find > rela for

Re: [PATCH] fix compilation of 64-bit kernel with 32-bit compiler

On Thu, Mar 08, 2018 at 01:11:26AM -0500, Mikulas Patocka wrote: > The patch b5bc2231b8ad4387c9641f235ca0ad8cd300b6df ("objtool: Add > retpoline validation") broke compiling 64-bit kernel with 32-bit compiler. > > This patch fixes the following error and a large number of "can't find > rela for

Re: [PATCH] net: xfrm: use preempt-safe this_cpu_read() in ipcomp_alloc_tfms()

On Wed, Mar 07, 2018 at 11:24:16AM -0800, Greg Hackmann wrote: > f7c83bcbfaf5 ("net: xfrm: use __this_cpu_read per-cpu helper") added a > __this_cpu_read() call inside ipcomp_alloc_tfms(). Since this call was > introduced, the rules around per-cpu accessors have been tightened and >

Re: [PATCH] net: xfrm: use preempt-safe this_cpu_read() in ipcomp_alloc_tfms()

On Wed, Mar 07, 2018 at 11:24:16AM -0800, Greg Hackmann wrote: > f7c83bcbfaf5 ("net: xfrm: use __this_cpu_read per-cpu helper") added a > __this_cpu_read() call inside ipcomp_alloc_tfms(). Since this call was > introduced, the rules around per-cpu accessors have been tightened and >

RE: [PATCH 2/2] platform/x86: dell-*: Add interface for switchable graphics status query

> -Original Message- > From: Kai-Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Thursday, March 8, 2018 3:12 PM > To: mj...@srcf.ucam.org; pali.ro...@gmail.com; dvh...@infradead.org; > a...@infradead.org; Limonciello, Mario ; > ti...@suse.com > Cc:

RE: [PATCH 2/2] platform/x86: dell-*: Add interface for switchable graphics status query

> -Original Message- > From: Kai-Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Thursday, March 8, 2018 3:12 PM > To: mj...@srcf.ucam.org; pali.ro...@gmail.com; dvh...@infradead.org; > a...@infradead.org; Limonciello, Mario ; > ti...@suse.com > Cc:

[PATCH v5 1/3] Input: gpio-keys - add support for wakeup event action

Add support for specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. This would allow the device to configure when to wakeup the system. For example a gpio-keys input device for pen insert, may only want to wakeup the system when ejecting the pen.

[PATCH v5 1/3] Input: gpio-keys - add support for wakeup event action

Add support for specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. This would allow the device to configure when to wakeup the system. For example a gpio-keys input device for pen insert, may only want to wakeup the system when ejecting the pen.

Re: [PATCH v4 1/3] Input: gpio-keys - add support for wakeup event action

Hi Andy, Thanks for your reply. On 03/07/2018 07:57 PM, Andy Shevchenko wrote: On Tue, Mar 6, 2018 at 9:44 AM, Jeffy Chen wrote: Add support for specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. This would allow

Re: [PATCH v4 1/3] Input: gpio-keys - add support for wakeup event action

Hi Andy, Thanks for your reply. On 03/07/2018 07:57 PM, Andy Shevchenko wrote: On Tue, Mar 6, 2018 at 9:44 AM, Jeffy Chen wrote: Add support for specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. This would allow the device to configure when

[PATCH v5 0/3] gpio-keys: Add support for specifying wakeup event action

On chromebook kevin, we are using gpio-keys for pen insert event. But we only want it to wakeup the system when ejecting the pen. So we may need to change the interrupt trigger type during suspending. Changes in v5: Remove unneeded irq_wake flag as Andy suggested. Changes in v4: Add dt-binding

[PATCH v5 2/3] Input: gpio-keys - allow setting wakeup event action in DT

Allow specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. Reviewed-by: Rob Herring Signed-off-by: Jeffy Chen --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: Specify

[PATCH v5 0/3] gpio-keys: Add support for specifying wakeup event action

On chromebook kevin, we are using gpio-keys for pen insert event. But we only want it to wakeup the system when ejecting the pen. So we may need to change the interrupt trigger type during suspending. Changes in v5: Remove unneeded irq_wake flag as Andy suggested. Changes in v4: Add dt-binding

[PATCH v5 2/3] Input: gpio-keys - allow setting wakeup event action in DT

Allow specifying event actions to trigger wakeup when using the gpio-keys input device as a wakeup source. Reviewed-by: Rob Herring Signed-off-by: Jeffy Chen --- Changes in v5: None Changes in v4: None Changes in v3: None Changes in v2: Specify wakeup event action instead of irq trigger type

RE: [PATCH 1/2] dell-led: Change dell-led.h to dell-common.h

> -Original Message- > From: Kai-Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Thursday, March 8, 2018 3:12 PM > To: mj...@srcf.ucam.org; pali.ro...@gmail.com; dvh...@infradead.org; > a...@infradead.org; Limonciello, Mario ; > ti...@suse.com > Cc:

RE: [PATCH 1/2] dell-led: Change dell-led.h to dell-common.h

> -Original Message- > From: Kai-Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Thursday, March 8, 2018 3:12 PM > To: mj...@srcf.ucam.org; pali.ro...@gmail.com; dvh...@infradead.org; > a...@infradead.org; Limonciello, Mario ; > ti...@suse.com > Cc:

Re: [PATCH 10/11] Staging: iio: accel: Add comments about units in data read function

On Wed, Mar 07, 2018 at 08:50:30PM +, Jonathan Cameron wrote: > On Mon, 5 Mar 2018 13:19:29 +0530 > Himanshu Jha wrote: > > > Clarify the conversion and formation of resultant data in the > > adis16201_read_raw() with sufficient comments. > > > > Signed-off-by:

Re: [PATCH 10/11] Staging: iio: accel: Add comments about units in data read function

On Wed, Mar 07, 2018 at 08:50:30PM +, Jonathan Cameron wrote: > On Mon, 5 Mar 2018 13:19:29 +0530 > Himanshu Jha wrote: > > > Clarify the conversion and formation of resultant data in the > > adis16201_read_raw() with sufficient comments. > > > > Signed-off-by: Himanshu Jha > This is fine

Re: [PATCH 1/2] dell-led: Change dell-led.h to dell-common.h

On Thu, 08 Mar 2018 08:12:06 +0100, Kai-Heng Feng wrote: > > This header will be used for more than just led. Change it to a more > generic name. > > Signed-off-by: Kai-Heng Feng Not sure whether dell-common.h is the best name, but I have no time for bikeshedding.

Re: [PATCH 1/2] dell-led: Change dell-led.h to dell-common.h

On Thu, 08 Mar 2018 08:12:06 +0100, Kai-Heng Feng wrote: > > This header will be used for more than just led. Change it to a more > generic name. > > Signed-off-by: Kai-Heng Feng Not sure whether dell-common.h is the best name, but I have no time for bikeshedding. For the sound change, feel

[PATCH v2] f2fs: add nowait aio support

From: Hyunchul Lee This patch adds nowait aio support[1]. Return EAGAIN if any of the following checks fail for direct I/O: - i_rwsem is not lockable - Blocks are not allocated at the write location And xfstests generic/471 is passed. [1]: 6be96d "Introduce RWF_NOWAIT

[PATCH v2] f2fs: add nowait aio support

From: Hyunchul Lee This patch adds nowait aio support[1]. Return EAGAIN if any of the following checks fail for direct I/O: - i_rwsem is not lockable - Blocks are not allocated at the write location And xfstests generic/471 is passed. [1]: 6be96d "Introduce RWF_NOWAIT and

[PATCH v2 4/4] clk: qcom: Add Global Clock controller (GCC) driver for SDM845

From: Taniya Das Add support for the global clock controller found on SDM845 based devices. This should allow most non-multimedia device drivers to probe and control their clocks. Signed-off-by: Taniya Das Signed-off-by: Amit Nischal

[PATCH v2 4/4] clk: qcom: Add Global Clock controller (GCC) driver for SDM845

From: Taniya Das Add support for the global clock controller found on SDM845 based devices. This should allow most non-multimedia device drivers to probe and control their clocks. Signed-off-by: Taniya Das Signed-off-by: Amit Nischal --- .../devicetree/bindings/clock/qcom,gcc.txt |

[PATCH v2 2/4] clk: qcom: Configure the RCGs to a safe source as needed

For some root clock generators, there could be child branches which are controlled by an entity other than application processor subsystem. For such RCGs, as per application processor subsystem clock driver, all of its downstream clocks are disabled and RCG is in disabled state but in actual

[PATCH v2 1/4] clk: qcom: Clear hardware clock control bit of RCG

For upcoming targets like sdm845, POR value of the hardware clock control bit is set for most of root clocks which needs to be cleared for software to be able to control. For older targets like MSM8996, this bit is reserved bit and having POR value as 0 so this patch will work for the older

[PATCH v2 2/4] clk: qcom: Configure the RCGs to a safe source as needed

For some root clock generators, there could be child branches which are controlled by an entity other than application processor subsystem. For such RCGs, as per application processor subsystem clock driver, all of its downstream clocks are disabled and RCG is in disabled state but in actual

[PATCH v2 1/4] clk: qcom: Clear hardware clock control bit of RCG

For upcoming targets like sdm845, POR value of the hardware clock control bit is set for most of root clocks which needs to be cleared for software to be able to control. For older targets like MSM8996, this bit is reserved bit and having POR value as 0 so this patch will work for the older

[PATCH v2 3/4] clk: qcom: Add support for controlling Fabia PLL

Fabia PLL is a Digital Frequency Locked Loop (DFLL) clock generator which has a wide range of frequency output. It supports dynamic updating of the output frequency ("frequency slewing") without need to turn off the PLL before configuration. Add support for initial configuration and programming

[PATCH v2 3/4] clk: qcom: Add support for controlling Fabia PLL

Fabia PLL is a Digital Frequency Locked Loop (DFLL) clock generator which has a wide range of frequency output. It supports dynamic updating of the output frequency ("frequency slewing") without need to turn off the PLL before configuration. Add support for initial configuration and programming

[PATCH v2 0/4] Misc patches to support clocks for SDM845

Changes in v2: Fixup for recalc_rate ops for clk_rcg2_shared_ops: There could be few scenarios where shared clocks are configured at rate other than CXO by boot. In those cases there would be a mismatch between the rate calculated by the recalc shared ops and the actual HW register configuration.

[PATCH v2 0/4] Misc patches to support clocks for SDM845

Changes in v2: Fixup for recalc_rate ops for clk_rcg2_shared_ops: There could be few scenarios where shared clocks are configured at rate other than CXO by boot. In those cases there would be a mismatch between the rate calculated by the recalc shared ops and the actual HW register configuration.

[PATCH AUTOSEL for 4.15 02/78] drm/amdgpu: use polling mem to set SDMA3 wptr for VF

From: Pixel Ding [ Upstream commit 2ffe31deb27579e2f2c9444e01f4d8abf385d145 ] On Tonga VF, there're 2 sources updating wptr registers for sdma3: 1) polling mem and 2) doorbell. When doorbell and polling mem are both enabled on sdma3, there will be collision hit in occasion

[PATCH AUTOSEL for 4.15 02/78] drm/amdgpu: use polling mem to set SDMA3 wptr for VF

From: Pixel Ding [ Upstream commit 2ffe31deb27579e2f2c9444e01f4d8abf385d145 ] On Tonga VF, there're 2 sources updating wptr registers for sdma3: 1) polling mem and 2) doorbell. When doorbell and polling mem are both enabled on sdma3, there will be collision hit in occasion between those two

[PATCH AUTOSEL for 4.15 03/78] Bluetooth: hci_qca: Avoid setup failure on missing rampatch

From: Loic Poulain [ Upstream commit ba8f3597900291a93604643017fff66a14546015 ] Assuming that the original code idea was to enable in-band sleeping only if the setup_rome method returns succes and run in 'standard' mode otherwise, we should not return setup_rome return

[PATCH AUTOSEL for 4.15 03/78] Bluetooth: hci_qca: Avoid setup failure on missing rampatch

From: Loic Poulain [ Upstream commit ba8f3597900291a93604643017fff66a14546015 ] Assuming that the original code idea was to enable in-band sleeping only if the setup_rome method returns succes and run in 'standard' mode otherwise, we should not return setup_rome return value which makes

[PATCH AUTOSEL for 4.15 06/78] dt-bindings: net: add TI CC2560 Bluetooth chip

From: David Lechner [ Upstream commit 07c7edd0db441f83087470add5be280cc018 ] This adds a compatible string for the Texas Instruments CC2560 Bluetooth chip to the existing TI WiLink shared transport bindings. These chips are similar enough that the same bindings work

[PATCH AUTOSEL for 4.15 06/78] dt-bindings: net: add TI CC2560 Bluetooth chip

From: David Lechner [ Upstream commit 07c7edd0db441f83087470add5be280cc018 ] This adds a compatible string for the Texas Instruments CC2560 Bluetooth chip to the existing TI WiLink shared transport bindings. These chips are similar enough that the same bindings work for both. The file is

[PATCH 2/2] platform/x86: dell-*: Add interface for switchable graphics status query

On some Dell platforms, there's a BIOS option "Enable Switchable Graphics". This information is useful if we want to do different things based on this value, e.g. disable unused audio controller that comes with the discrete graphics. Signed-off-by: Kai-Heng Feng ---

[PATCH 2/2] platform/x86: dell-*: Add interface for switchable graphics status query

On some Dell platforms, there's a BIOS option "Enable Switchable Graphics". This information is useful if we want to do different things based on this value, e.g. disable unused audio controller that comes with the discrete graphics. Signed-off-by: Kai-Heng Feng ---

Re: [PATCH 4.15 000/122] 4.15.8-stable review

On 8 March 2018 at 01:06, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.8 release. > There are 122 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please

Re: [PATCH 4.15 000/122] 4.15.8-stable review

On 8 March 2018 at 01:06, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.8 release. > There are 122 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. > >

[PATCH 1/2] dell-led: Change dell-led.h to dell-common.h

This header will be used for more than just led. Change it to a more generic name. Signed-off-by: Kai-Heng Feng --- drivers/platform/x86/dell-laptop.c | 2 +- include/linux/{dell-led.h => dell-common.h} | 4 ++-- sound/pci/hda/dell_wmi_helper.c

[PATCH 1/2] dell-led: Change dell-led.h to dell-common.h

This header will be used for more than just led. Change it to a more generic name. Signed-off-by: Kai-Heng Feng --- drivers/platform/x86/dell-laptop.c | 2 +- include/linux/{dell-led.h => dell-common.h} | 4 ++-- sound/pci/hda/dell_wmi_helper.c | 2 +- 3 files changed, 4

[PATCH AUTOSEL for 4.15 05/78] cpufreq: longhaul: Revert transition_delay_us to 200 ms

From: Viresh Kumar [ Upstream commit 1d0d064307cbfd8546841f6e9d94d02c55e45e1e ] The commit e948bc8fbee0 ("cpufreq: Cap the default transition delay value to 10 ms") caused a regression on EPIA-M min-ITX computer where shutdown or reboot hangs occasionally with a print

[PATCH AUTOSEL for 4.15 05/78] cpufreq: longhaul: Revert transition_delay_us to 200 ms

From: Viresh Kumar [ Upstream commit 1d0d064307cbfd8546841f6e9d94d02c55e45e1e ] The commit e948bc8fbee0 ("cpufreq: Cap the default transition delay value to 10 ms") caused a regression on EPIA-M min-ITX computer where shutdown or reboot hangs occasionally with a print message like: longhaul:

[PATCH AUTOSEL for 4.15 01/78] ipmi_si: Fix error handling of platform device

From: Corey Minyard [ Upstream commit 174134ac760275457bb0d1560a0dbe6cf8a12ad6 ] Cleanup of platform devices created by the IPMI driver was not being done correctly and could result in a memory leak. So create a local boolean to know how to clean up those platform devices.

[PATCH AUTOSEL for 4.15 01/78] ipmi_si: Fix error handling of platform device

From: Corey Minyard [ Upstream commit 174134ac760275457bb0d1560a0dbe6cf8a12ad6 ] Cleanup of platform devices created by the IPMI driver was not being done correctly and could result in a memory leak. So create a local boolean to know how to clean up those platform devices. Reported-by: David

[PATCH AUTOSEL for 4.15 07/78] media: c8sectpfe: fix potential NULL pointer dereference in c8sectpfe_timer_interrupt

From: "Gustavo A. R. Silva" [ Upstream commit baed3c4bc4c13de93e0dba0a26d601411ebcb389 ] _channel_ is being dereferenced before it is null checked, hence there is a potential null pointer dereference. Fix this by moving the pointer dereference after _channel_ has been

[PATCH AUTOSEL for 4.15 07/78] media: c8sectpfe: fix potential NULL pointer dereference in c8sectpfe_timer_interrupt

From: "Gustavo A. R. Silva" [ Upstream commit baed3c4bc4c13de93e0dba0a26d601411ebcb389 ] _channel_ is being dereferenced before it is null checked, hence there is a potential null pointer dereference. Fix this by moving the pointer dereference after _channel_ has been null checked. This issue

[PATCH AUTOSEL for 4.15 04/78] Bluetooth: btqcomsmd: Fix skb double free corruption

From: Loic Poulain [ Upstream commit 67b8fbead4685b36d290a0ef91c6ddffc4920ec9 ] In case of hci send frame failure, skb is still owned by the caller (hci_core) and then should not be freed. This fixes crash on dragonboard-410c when sending SCO packet. skb is freed by

[PATCH AUTOSEL for 4.15 10/78] dm: ensure bio submission follows a depth-first tree walk

From: NeilBrown [ Upstream commit 18a25da84354c6bb655320de6072c00eda6eb602 ] A dm device can, in general, represent a tree of targets, each of which handles a sub-range of the range of blocks handled by the parent. The bio sequencing managed by generic_make_request() requires

[PATCH AUTOSEL for 4.15 13/78] hv_netvsc: Fix the receive buffer size limit

From: Haiyang Zhang [ Upstream commit 11b2b653102571ac791885324371d9a1a17b900e ] The max should be 31 MB on host with NVSP version > 2. On legacy hosts (NVSP version <=2) only 15 MB receive buffer is allowed, otherwise the buffer request will be rejected by the host,

[PATCH AUTOSEL for 4.15 04/78] Bluetooth: btqcomsmd: Fix skb double free corruption

From: Loic Poulain [ Upstream commit 67b8fbead4685b36d290a0ef91c6ddffc4920ec9 ] In case of hci send frame failure, skb is still owned by the caller (hci_core) and then should not be freed. This fixes crash on dragonboard-410c when sending SCO packet. skb is freed by both btqcomsmd and

[PATCH AUTOSEL for 4.15 10/78] dm: ensure bio submission follows a depth-first tree walk

From: NeilBrown [ Upstream commit 18a25da84354c6bb655320de6072c00eda6eb602 ] A dm device can, in general, represent a tree of targets, each of which handles a sub-range of the range of blocks handled by the parent. The bio sequencing managed by generic_make_request() requires that bios are

[PATCH AUTOSEL for 4.15 13/78] hv_netvsc: Fix the receive buffer size limit

From: Haiyang Zhang [ Upstream commit 11b2b653102571ac791885324371d9a1a17b900e ] The max should be 31 MB on host with NVSP version > 2. On legacy hosts (NVSP version <=2) only 15 MB receive buffer is allowed, otherwise the buffer request will be rejected by the host, resulting vNIC not coming

[PATCH AUTOSEL for 4.15 11/78] IB/ipoib: Warn when one port fails to initialize

From: Yuval Shaia [ Upstream commit ac6dbf7fa4707c75a247b540cc0b5c881f3d0ba8 ] If one port fails to initialize an error message should indicate the reason and driver should continue serving the working port(s) and other HCA(s). Fixes: e4b2d06892c7 ("IB/ipoib: Remove

[PATCH AUTOSEL for 4.15 11/78] IB/ipoib: Warn when one port fails to initialize

From: Yuval Shaia [ Upstream commit ac6dbf7fa4707c75a247b540cc0b5c881f3d0ba8 ] If one port fails to initialize an error message should indicate the reason and driver should continue serving the working port(s) and other HCA(s). Fixes: e4b2d06892c7 ("IB/ipoib: Remove device when one port fails

[PATCH AUTOSEL for 4.15 08/78] drm/msm: fix leak in failed get_pages

From: Prakash Kamliya [ Upstream commit 62e3a3e342af3c313ab38603811ecdb1fcc79edb ] get_pages doesn't keep a reference of the pages allocated when it fails later in the code path. This can lead to a memory leak. Keep reference of the allocated pages so that it can be

[PATCH AUTOSEL for 4.15 08/78] drm/msm: fix leak in failed get_pages

From: Prakash Kamliya [ Upstream commit 62e3a3e342af3c313ab38603811ecdb1fcc79edb ] get_pages doesn't keep a reference of the pages allocated when it fails later in the code path. This can lead to a memory leak. Keep reference of the allocated pages so that it can be freed when

[PATCH AUTOSEL for 4.15 16/78] KVM: x86: add support for emulating UMIP

From: Paolo Bonzini [ Upstream commit 66336cab3531d3325ebde36a047250c42cb5 ] The User-Mode Instruction Prevention feature present in recent Intel processor prevents a group of instructions (sgdt, sidt, sldt, smsw, and str) from being executed with CPL > 0. Otherwise, a

[PATCH AUTOSEL for 4.15 16/78] KVM: x86: add support for emulating UMIP

From: Paolo Bonzini [ Upstream commit 66336cab3531d3325ebde36a047250c42cb5 ] The User-Mode Instruction Prevention feature present in recent Intel processor prevents a group of instructions (sgdt, sidt, sldt, smsw, and str) from being executed with CPL > 0. Otherwise, a general protection

[PATCH AUTOSEL for 4.15 12/78] RDMA/iwpm: Fix uninitialized error code in iwpm_send_mapinfo()

From: Geert Uytterhoeven [ Upstream commit 302d6424e4a293a5761997e6c9fc3dfb1e4c355f ] With gcc-4.1.2: drivers/infiniband/core/iwpm_util.c: In function ‘iwpm_send_mapinfo’: drivers/infiniband/core/iwpm_util.c:647: warning: ‘ret’ may be used uninitialized in this

[PATCH AUTOSEL for 4.15 12/78] RDMA/iwpm: Fix uninitialized error code in iwpm_send_mapinfo()

From: Geert Uytterhoeven [ Upstream commit 302d6424e4a293a5761997e6c9fc3dfb1e4c355f ] With gcc-4.1.2: drivers/infiniband/core/iwpm_util.c: In function ‘iwpm_send_mapinfo’: drivers/infiniband/core/iwpm_util.c:647: warning: ‘ret’ may be used uninitialized in this function Indeed, if

Re: [PATCH] kbuild: Handle builtin dtb files containing hyphens

On Wed, Mar 07, 2018 at 03:19:11PM -0800, Frank Rowand wrote: > On 03/07/18 12:25, James Hogan wrote: > > On Wed, Mar 07, 2018 at 12:11:41PM -0800, Frank Rowand wrote: > >> On 03/07/18 06:06, James Hogan wrote: > >>> Quite a lot of dts files have hyphens, but its only a problem on MIPS > >>> where

Re: [PATCH] kbuild: Handle builtin dtb files containing hyphens

On Wed, Mar 07, 2018 at 03:19:11PM -0800, Frank Rowand wrote: > On 03/07/18 12:25, James Hogan wrote: > > On Wed, Mar 07, 2018 at 12:11:41PM -0800, Frank Rowand wrote: > >> On 03/07/18 06:06, James Hogan wrote: > >>> Quite a lot of dts files have hyphens, but its only a problem on MIPS > >>> where

[PATCH AUTOSEL for 4.15 14/78] hv_netvsc: Fix the TX/RX buffer default sizes

From: Haiyang Zhang [ Upstream commit 41f61db2cd24d5ad802386719cccde1479aa82a6 ] The values were not computed correctly. There are no significant visible impact, though. The intended size of RX buffer is 16 MB, and the default slot size is 1728. So, NETVSC_DEFAULT_RX

[PATCH AUTOSEL for 4.15 14/78] hv_netvsc: Fix the TX/RX buffer default sizes

From: Haiyang Zhang [ Upstream commit 41f61db2cd24d5ad802386719cccde1479aa82a6 ] The values were not computed correctly. There are no significant visible impact, though. The intended size of RX buffer is 16 MB, and the default slot size is 1728. So, NETVSC_DEFAULT_RX should be 16*1024*1024 /

[PATCH AUTOSEL for 4.15 18/78] libbpf: prefer global symbols as bpf program name source

From: Roman Gushchin [ Upstream commit fe4d44b23f6b38194a92c6b8a50d921a071c4db4 ] Libbpf picks the name of the first symbol in the corresponding elf section to use as a program name. But without taking symbol's scope into account it may end's up with some local label as a program

[PATCH AUTOSEL for 4.15 18/78] libbpf: prefer global symbols as bpf program name source

From: Roman Gushchin [ Upstream commit fe4d44b23f6b38194a92c6b8a50d921a071c4db4 ] Libbpf picks the name of the first symbol in the corresponding elf section to use as a program name. But without taking symbol's scope into account it may end's up with some local label as a program name. E.g.: $

[PATCH] vfio-mdev/samples: change RDI interrupt condition

When FIFO mode is enabled, the receive data available interrupt (UART_IIR_RDI in code) should be triggered when the number of data in FIFO is equal or larger than interrupt trigger level. This patch changes the trigger level check to ensure multiple bytes received from upper layer can trigger RDI

[PATCH AUTOSEL for 4.15 17/78] spi: sh-msiof: Avoid writing to registers from spi_master.setup()

From: Geert Uytterhoeven [ Upstream commit 7ff0b53c4051145d1cf992d2f60987e6447eed4f ] The spi_master.setup() callback must not change configuration registers, as that could corrupt I/O that is in progress for other SPI slaves. The only exception is the configuration of

[PATCH AUTOSEL for 4.15 17/78] spi: sh-msiof: Avoid writing to registers from spi_master.setup()

From: Geert Uytterhoeven [ Upstream commit 7ff0b53c4051145d1cf992d2f60987e6447eed4f ] The spi_master.setup() callback must not change configuration registers, as that could corrupt I/O that is in progress for other SPI slaves. The only exception is the configuration of the native chip select

[PATCH] vfio-mdev/samples: change RDI interrupt condition

When FIFO mode is enabled, the receive data available interrupt (UART_IIR_RDI in code) should be triggered when the number of data in FIFO is equal or larger than interrupt trigger level. This patch changes the trigger level check to ensure multiple bytes received from upper layer can trigger RDI

[PATCH AUTOSEL for 4.15 22/78] ath10k: handling qos at STA side based on AP WMM enable/disable

From: Balaji Pothunoori [ Upstream commit 07ffb4497360ae8789f0fec8171ee952304d ] Data packets are not sent by STA in case of STA joined to non QOS AP (WMM disabled AP). This is happening because of STA is sending data packets to firmware from host with qos enabled

[PATCH AUTOSEL for 4.15 22/78] ath10k: handling qos at STA side based on AP WMM enable/disable

From: Balaji Pothunoori [ Upstream commit 07ffb4497360ae8789f0fec8171ee952304d ] Data packets are not sent by STA in case of STA joined to non QOS AP (WMM disabled AP). This is happening because of STA is sending data packets to firmware from host with qos enabled along with non qos queue

[PATCH AUTOSEL for 4.15 23/78] media: [RESEND] media: dvb-frontends: Add delay to Si2168 restart

From: Ron Economos [ Upstream commit 380a6c86457573aa42d27ae11e025eb25941a0b7 ] On faster CPUs a delay is required after the resume command and the restart command. Without the delay, the restart command often returns -EREMOTEIO and the Si2168 does not restart. Note that

[PATCH AUTOSEL for 4.15 23/78] media: [RESEND] media: dvb-frontends: Add delay to Si2168 restart

From: Ron Economos [ Upstream commit 380a6c86457573aa42d27ae11e025eb25941a0b7 ] On faster CPUs a delay is required after the resume command and the restart command. Without the delay, the restart command often returns -EREMOTEIO and the Si2168 does not restart. Note that this patch fixes the

[PATCH AUTOSEL for 4.15 25/78] tty: goldfish: Enable 'earlycon' only if built-in

From: Sebastian Andrzej Siewior [ Upstream commit 6a28fd2bbc94bfca105632e5ef8a9dbe63ba0b39 ] Commit 3840ed9548f7 ("tty: goldfish: Implement support for kernel 'earlycon' parameter") breaks an allmodconfig config on x86: | LD vmlinux.o | MODPOST vmlinux.o

[PATCH AUTOSEL for 4.15 25/78] tty: goldfish: Enable 'earlycon' only if built-in

From: Sebastian Andrzej Siewior [ Upstream commit 6a28fd2bbc94bfca105632e5ef8a9dbe63ba0b39 ] Commit 3840ed9548f7 ("tty: goldfish: Implement support for kernel 'earlycon' parameter") breaks an allmodconfig config on x86: | LD vmlinux.o | MODPOST vmlinux.o |drivers/tty/serial/earlycon.o:

  1   2   3   4   5   6   7   8   9   10   >