[PATCH AUTOSEL for 4.4 06/25] dt-bindings: clockgen: Add compatible string for LS1012A

From: Harninder Rai [ Upstream commit 73447f68d7b2bc1df870da88b0e21d2bc1afc025 ] Signed-off-by: Harninder Rai Signed-off-by: Bhaskar Upadhaya Acked-by: Rob Herring Signed-off-by: Shawn Guo

[PATCH AUTOSEL for 4.4 05/25] ARM: dts: imx53-qsb-common: fix FEC pinmux config

From: Patrick Bruenn [ Upstream commit 8b649e426336d7d4800ff9c82858328f4215ba01 ] The pinmux configuration in device tree was different from manual muxing in /board/freescale/mx53loco/mx53loco.c All pins were configured as NO_PAD_CTL(1 << 31), which was fine as the bootloader already did the

[PATCH AUTOSEL for 4.4 07/25] drm: drm_minor_register(): Clean up debugfs on failure

From: Noralf Trønnes [ Upstream commit a67834f8bfa1e2f48bb27d07b9a552ba7c3af82a ] Call drm_debugfs_cleanup() in case drm_debugfs_init() fails to cover for failure in the drm_driver.debugfs_init callback. Signed-off-by: Noralf Trønnes Signed-off-by: Daniel Vetter Link:

[PATCH AUTOSEL for 4.4 06/25] dt-bindings: clockgen: Add compatible string for LS1012A

From: Harninder Rai [ Upstream commit 73447f68d7b2bc1df870da88b0e21d2bc1afc025 ] Signed-off-by: Harninder Rai Signed-off-by: Bhaskar Upadhaya Acked-by: Rob Herring Signed-off-by: Shawn Guo Signed-off-by: Sasha Levin --- Documentation/devicetree/bindings/clock/qoriq-clock.txt | 1 + 1 file

[PATCH AUTOSEL for 4.9 45/50] s390/qeth: fix retrieval of vipa and proxy-arp addresses

From: Ursula Braun [ Upstream commit e48b9eaaa29a0a7d5da2df136b07eefa0180d584 ] qeth devices in layer3 mode need a separate handling of vipa and proxy-arp addresses. vipa and proxy-arp addresses processed by qeth can be read from userspace. Introduced with commit

[PATCH AUTOSEL for 4.9 45/50] s390/qeth: fix retrieval of vipa and proxy-arp addresses

From: Ursula Braun [ Upstream commit e48b9eaaa29a0a7d5da2df136b07eefa0180d584 ] qeth devices in layer3 mode need a separate handling of vipa and proxy-arp addresses. vipa and proxy-arp addresses processed by qeth can be read from userspace. Introduced with commit 5f78e29ceebf ("qeth: optimize

[PATCH AUTOSEL for 4.9 32/50] netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family

From: Liping Zhang [ Upstream commit f169fd695b192dd7b23aff8e69d25a1bc881bbfa ] After adding the following nft rule, then ping 224.0.0.1: # nft add rule netdev t c pkttype host counter The warning complain message will be printed out again and again: WARNING: CPU: 0

[PATCH AUTOSEL for 4.4 01/25] [media] adv7604: Initialize drive strength to default when using DT

From: Lars-Peter Clausen [ Upstream commit da8892d410db224d9a24104529794e6e37e0c100 ] The adv7604 driver platform data contains fields for configuring the drive strength of the output pins. When probing the driver through DT these fields are not explicitly initialized, which

[PATCH AUTOSEL for 4.4 09/25] iommu/arm-smmu-v3: Clear prior settings when updating STEs

From: Nate Watterson [ Upstream commit 810871c57011eb3e89e6768932757f169d666cd2 ] To prevent corruption of the stage-1 context pointer field when updating STEs, rebuild the entire containing dword instead of clearing individual fields. Signed-off-by: Nate Watterson

[PATCH AUTOSEL for 4.9 32/50] netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family

From: Liping Zhang [ Upstream commit f169fd695b192dd7b23aff8e69d25a1bc881bbfa ] After adding the following nft rule, then ping 224.0.0.1: # nft add rule netdev t c pkttype host counter The warning complain message will be printed out again and again: WARNING: CPU: 0 PID: 10182 at

[PATCH AUTOSEL for 4.4 01/25] [media] adv7604: Initialize drive strength to default when using DT

From: Lars-Peter Clausen [ Upstream commit da8892d410db224d9a24104529794e6e37e0c100 ] The adv7604 driver platform data contains fields for configuring the drive strength of the output pins. When probing the driver through DT these fields are not explicitly initialized, which means they are left

[PATCH AUTOSEL for 4.4 09/25] iommu/arm-smmu-v3: Clear prior settings when updating STEs

From: Nate Watterson [ Upstream commit 810871c57011eb3e89e6768932757f169d666cd2 ] To prevent corruption of the stage-1 context pointer field when updating STEs, rebuild the entire containing dword instead of clearing individual fields. Signed-off-by: Nate Watterson Signed-off-by: Will Deacon

[PATCH AUTOSEL for 4.9 22/50] iio: pressure: ms5611: claim direct mode during oversampling changes

From: Alison Schofield [ Upstream commit 3bc1abcddb24f55b9c251e03caa4f9bd22ff748b ] Driver was checking for direct mode before changing oversampling ratios, but was not locking it. Use the claim/release helper functions to guarantee the device stays in direct mode while

[PATCH AUTOSEL for 4.9 09/50] PM / OPP: Error out on failing to add static OPPs for v1 bindings

From: Viresh Kumar [ Upstream commit 04a86a84c42ca18f37ab446127dc619b41dd3b23 ] The code adding static OPPs for V2 bindings already does so. Make the V1 bindings specific code behave the same. Signed-off-by: Viresh Kumar Reviewed-by: Stephen

[PATCH AUTOSEL for 4.9 22/50] iio: pressure: ms5611: claim direct mode during oversampling changes

From: Alison Schofield [ Upstream commit 3bc1abcddb24f55b9c251e03caa4f9bd22ff748b ] Driver was checking for direct mode before changing oversampling ratios, but was not locking it. Use the claim/release helper functions to guarantee the device stays in direct mode while the oversampling ratios

[PATCH AUTOSEL for 4.9 09/50] PM / OPP: Error out on failing to add static OPPs for v1 bindings

From: Viresh Kumar [ Upstream commit 04a86a84c42ca18f37ab446127dc619b41dd3b23 ] The code adding static OPPs for V2 bindings already does so. Make the V1 bindings specific code behave the same. Signed-off-by: Viresh Kumar Reviewed-by: Stephen Boyd Signed-off-by: Rafael J. Wysocki

[PATCH AUTOSEL for 4.9 17/50] ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6

From: Tony Lindgren [ Upstream commit 4cd6a59f5c1a9b0cca0da09fbba42b9450ffc899 ] We have more than four uarts on some SoCs and that can cause noise with errors while booting. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin

[PATCH AUTOSEL for 4.9 17/50] ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6

From: Tony Lindgren [ Upstream commit 4cd6a59f5c1a9b0cca0da09fbba42b9450ffc899 ] We have more than four uarts on some SoCs and that can cause noise with errors while booting. Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin --- arch/arm/configs/omap2plus_defconfig | 1 + 1 file

[PATCH AUTOSEL for 4.9 27/50] dt-bindings: Add vendor prefix for LEGO

From: David Lechner [ Upstream commit 7dcc31e2e68a386a29070384b51683ece80982bf ] Add a vendor prefix for LEGO Systems A/S Acked-by: Rob Herring Signed-off-by: David Lechner Signed-off-by: Sekhar Nori Signed-off-by:

[PATCH AUTOSEL for 4.9 27/50] dt-bindings: Add vendor prefix for LEGO

From: David Lechner [ Upstream commit 7dcc31e2e68a386a29070384b51683ece80982bf ] Add a vendor prefix for LEGO Systems A/S Acked-by: Rob Herring Signed-off-by: David Lechner Signed-off-by: Sekhar Nori Signed-off-by: Sasha Levin --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1

[PATCH AUTOSEL for 4.9 19/50] crypto: vmx - disable preemption to enable vsx in aes_ctr.c

From: Li Zhong [ Upstream commit 7dede913fc2ab9c0d3bff3a49e26fa9e858b0c13 ] Some preemptible check warnings were reported from enable_kernel_vsx(). This patch disables preemption in aes_ctr.c before enabling vsx, and they are now consistent with other files in the same

[PATCH AUTOSEL for 4.9 18/50] arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA

From: Will Deacon [ Upstream commit 4a8d8a14c0d08c2437cb80c05e88f6cc1ca3fb2c ] The arm64 DMA-mapping implementation sets the DMA ops to the IOMMU DMA ops if we detect that an IOMMU is present for the master and the DMA ranges are valid. In the case when the IOMMU domain

[PATCH AUTOSEL for 4.9 14/50] pinctrl: baytrail: Fix debugfs offset output

From: Alexander Stein [ Upstream commit 3655a1ca6bd8e7300f2bb196208d5139aa6b2eda ] Apparently each GPIO pad's register are 16 bytes, so multiply the pad_map by that. The same is done in byt_gpio_reg the only other place where pad_map is used.

[PATCH AUTOSEL for 4.9 19/50] crypto: vmx - disable preemption to enable vsx in aes_ctr.c

From: Li Zhong [ Upstream commit 7dede913fc2ab9c0d3bff3a49e26fa9e858b0c13 ] Some preemptible check warnings were reported from enable_kernel_vsx(). This patch disables preemption in aes_ctr.c before enabling vsx, and they are now consistent with other files in the same directory.

[PATCH AUTOSEL for 4.9 18/50] arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA

From: Will Deacon [ Upstream commit 4a8d8a14c0d08c2437cb80c05e88f6cc1ca3fb2c ] The arm64 DMA-mapping implementation sets the DMA ops to the IOMMU DMA ops if we detect that an IOMMU is present for the master and the DMA ranges are valid. In the case when the IOMMU domain for the device is not

[PATCH AUTOSEL for 4.9 14/50] pinctrl: baytrail: Fix debugfs offset output

From: Alexander Stein [ Upstream commit 3655a1ca6bd8e7300f2bb196208d5139aa6b2eda ] Apparently each GPIO pad's register are 16 bytes, so multiply the pad_map by that. The same is done in byt_gpio_reg the only other place where pad_map is used. Signed-off-by: Alexander Stein Signed-off-by:

[PATCH AUTOSEL for 4.9 03/50] PCI: mvebu: Handle changes to the bridge windows while enabled

From: Jason Gunthorpe [ Upstream commit d9bf28e2650fe3eeefed7e34841aea07d10c6543 ] The PCI core will write to the bridge window config multiple times while they are enabled. This can lead to mbus failures like this: mvebu_mbus: cannot add window '4:e8',

[PATCH AUTOSEL for 4.9 04/50] sched/core: Add missing update_rq_clock() call in sched_move_task()

From: Peter Zijlstra [ Upstream commit 1b1d62254df0fe42a711eb71948f915918987790 ] Bug was noticed via this warning: WARNING: CPU: 6 PID: 1 at kernel/sched/sched.h:804 detach_task_cfs_rq+0x8e8/0xb80 rq->clock_update_flags < RQCF_ACT_SKIP Modules linked in: CPU: 6

[PATCH AUTOSEL for 4.9 08/50] EDAC, amd64: Add x86cpuid sanity check during init

From: Yazen Ghannam [ Upstream commit 1bd9900b8301fc505f032c90ea487824cf824e99 ] Match one of the devices in amd64_cpuids[] before loading the module. This is an additional sanity check against users trying to load amd64_edac_mod on unsupported systems. Signed-off-by:

[PATCH AUTOSEL for 4.9 03/50] PCI: mvebu: Handle changes to the bridge windows while enabled

From: Jason Gunthorpe [ Upstream commit d9bf28e2650fe3eeefed7e34841aea07d10c6543 ] The PCI core will write to the bridge window config multiple times while they are enabled. This can lead to mbus failures like this: mvebu_mbus: cannot add window '4:e8', conflicts with another window

[PATCH AUTOSEL for 4.9 04/50] sched/core: Add missing update_rq_clock() call in sched_move_task()

From: Peter Zijlstra [ Upstream commit 1b1d62254df0fe42a711eb71948f915918987790 ] Bug was noticed via this warning: WARNING: CPU: 6 PID: 1 at kernel/sched/sched.h:804 detach_task_cfs_rq+0x8e8/0xb80 rq->clock_update_flags < RQCF_ACT_SKIP Modules linked in: CPU: 6 PID: 1 Comm: systemd

[PATCH AUTOSEL for 4.9 08/50] EDAC, amd64: Add x86cpuid sanity check during init

From: Yazen Ghannam [ Upstream commit 1bd9900b8301fc505f032c90ea487824cf824e99 ] Match one of the devices in amd64_cpuids[] before loading the module. This is an additional sanity check against users trying to load amd64_edac_mod on unsupported systems. Signed-off-by: Yazen Ghannam Cc:

Re: [PATCH review for 4.4 14/24] dmaengine: sun6i: allow build on ARM64 platforms (sun50i)

On Sun, Oct 08, 2017 at 10:27:45AM +0800, Icenowy Zheng wrote: > > >于 2017年10月8日 GMT+08:00 上午6:37:46, "Levin, Alexander (Sasha Levin)" ><alexander.le...@verizon.com> 写到: >>From: Icenowy Zheng <icen...@aosc.xyz> >> >>[ Upstream commit c429c

Re: [PATCH review for 4.4 14/24] dmaengine: sun6i: allow build on ARM64 platforms (sun50i)

On Sun, Oct 08, 2017 at 10:27:45AM +0800, Icenowy Zheng wrote: > > >于 2017年10月8日 GMT+08:00 上午6:37:46, "Levin, Alexander (Sasha Levin)" > 写到: >>From: Icenowy Zheng >> >>[ Upstream commit c429ceb1e18252122ba96b52e689dcf87103c186 ] >> >>As 64-

Re: [PATCH review for 4.9 39/50] ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches

On Mon, Oct 09, 2017 at 09:36:56AM +0100, Mark Brown wrote: >On Sat, Oct 07, 2017 at 10:36:55PM +0000, Levin, Alexander (Sasha Levin) wrote: >> From: Matt Ranostay <matt@ranostay.consulting> >> >> [ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ] >> >

Re: [PATCH review for 4.9 39/50] ASoC: omap-mcbsp: Add PM QoS support for McBSP to prevent glitches

On Mon, Oct 09, 2017 at 09:36:56AM +0100, Mark Brown wrote: >On Sat, Oct 07, 2017 at 10:36:55PM +0000, Levin, Alexander (Sasha Levin) wrote: >> From: Matt Ranostay >> >> [ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ] >> >> We can get audio err

Re: [PATCH review for 4.9 31/50] xen/manage: correct return value check on xenbus_scanf()

On Tue, Oct 10, 2017 at 08:49:13AM -0400, Boris Ostrovsky wrote: >On 10/07/2017 06:36 PM, Levin, Alexander (Sasha Levin) wrote: >> From: Jan Beulich <jbeul...@suse.com> >> >> [ Upstream commit 4fed1b125eb6252bde478665fc05d4819f774fa8 ] >> >> A negative r

Re: [PATCH review for 4.9 31/50] xen/manage: correct return value check on xenbus_scanf()

On Tue, Oct 10, 2017 at 08:49:13AM -0400, Boris Ostrovsky wrote: >On 10/07/2017 06:36 PM, Levin, Alexander (Sasha Levin) wrote: >> From: Jan Beulich >> >> [ Upstream commit 4fed1b125eb6252bde478665fc05d4819f774fa8 ] >> >> A negative return value indicat

Re: [PATCH v2] net/sock: Update sk rcu iterator macro.

On Mon, Oct 23, 2017 at 11:39:22AM -0400, Tim Hansen wrote: >Mark hlist nodes in sk rcu iterator as protected by the rcu. >hlist_next_rcu accomplishes this and silences the warnings >sparse throws for net/ipv4/udp.c and net/ipv6/udp.c. > >Found with make C=1 net/ipv4/udp.o on linux-next tag

Re: [PATCH v2] net/sock: Update sk rcu iterator macro.

On Mon, Oct 23, 2017 at 11:39:22AM -0400, Tim Hansen wrote: >Mark hlist nodes in sk rcu iterator as protected by the rcu. >hlist_next_rcu accomplishes this and silences the warnings >sparse throws for net/ipv4/udp.c and net/ipv6/udp.c. > >Found with make C=1 net/ipv4/udp.o on linux-next tag

Re: [PATCH 4.4 02/50] drm: bridge: add DT bindings for TI ths8135

On Thu, Oct 19, 2017 at 11:37:20AM +0200, Greg Kroah-Hartman wrote: >On Mon, Oct 16, 2017 at 08:05:53PM +0100, Ben Hutchings wrote: >> On Fri, 2017-10-06 at 10:52 +0200, Greg Kroah-Hartman wrote: >> > 4.4-stable review patch.  If anyone has any objections, please let me >> > know. >> > >> >

Re: [PATCH 4.4 02/50] drm: bridge: add DT bindings for TI ths8135

On Thu, Oct 19, 2017 at 11:37:20AM +0200, Greg Kroah-Hartman wrote: >On Mon, Oct 16, 2017 at 08:05:53PM +0100, Ben Hutchings wrote: >> On Fri, 2017-10-06 at 10:52 +0200, Greg Kroah-Hartman wrote: >> > 4.4-stable review patch.  If anyone has any objections, please let me >> > know. >> > >> >

Re: [PATCH] kmemcheck: correctly remove kmemcheck call from dma_map_sg_attrs

On Fri, Oct 13, 2017 at 09:11:21AM +0200, Michal Hocko wrote: >On Thu 12-10-17 19:22:05, Sasha Levin wrote: >> We have missed removing some code as part of removing the kmemcheck >> hooks. >> >> Unfourtenatly this got missed during my review, and the code was >> still building. >> >> Reported-by:

Re: [PATCH] kmemcheck: correctly remove kmemcheck call from dma_map_sg_attrs

On Fri, Oct 13, 2017 at 09:11:21AM +0200, Michal Hocko wrote: >On Thu 12-10-17 19:22:05, Sasha Levin wrote: >> We have missed removing some code as part of removing the kmemcheck >> hooks. >> >> Unfourtenatly this got missed during my review, and the code was >> still building. >> >> Reported-by:

[PATCH] kmemcheck: correctly remove kmemcheck call from dma_map_sg_attrs

We have missed removing some code as part of removing the kmemcheck hooks. Unfourtenatly this got missed during my review, and the code was still building. Reported-by: Michal Hocko Signed-off-by: Sasha Levin --- include/linux/dma-mapping.h | 4

[PATCH] kmemcheck: correctly remove kmemcheck call from dma_map_sg_attrs

We have missed removing some code as part of removing the kmemcheck hooks. Unfourtenatly this got missed during my review, and the code was still building. Reported-by: Michal Hocko Signed-off-by: Sasha Levin --- include/linux/dma-mapping.h | 4 +--- 1 file changed, 1 insertion(+), 3

Re: [PATCH v2 1/4] kmemcheck: remove annotations

On Wed, Oct 11, 2017 at 03:17:32PM +0200, Michal Hocko wrote: >On Sat 07-10-17 03:02:13, Sasha Levin wrote: >> Remove kmemcheck annotations, and calls to kmemcheck from the kernel. > >How did you generate this? I suspect a git grep + sed? Because this >doesn't seem to be correct. I didn't get

Re: [PATCH v2 1/4] kmemcheck: remove annotations

On Wed, Oct 11, 2017 at 03:17:32PM +0200, Michal Hocko wrote: >On Sat 07-10-17 03:02:13, Sasha Levin wrote: >> Remove kmemcheck annotations, and calls to kmemcheck from the kernel. > >How did you generate this? I suspect a git grep + sed? Because this >doesn't seem to be correct. I didn't get

Re: [PATCH] 9p: set page uptodate when required in write_end()

Linus, Al, Can one of you please pick this one directly? This has been on LKML since April, but the 9p maintainers seem to be MIA? On Thu, Jun 01, 2017 at 10:31:09PM -0400, Sasha Levin wrote: >Ping? > >On Mon, Apr 10, 2017 at 02:46:57PM -0400, Sasha Levin wrote: >> From: Alexander Levin

Re: [PATCH] 9p: set page uptodate when required in write_end()

Linus, Al, Can one of you please pick this one directly? This has been on LKML since April, but the 9p maintainers seem to be MIA? On Thu, Jun 01, 2017 at 10:31:09PM -0400, Sasha Levin wrote: >Ping? > >On Mon, Apr 10, 2017 at 02:46:57PM -0400, Sasha Levin wrote: >> From: Alexander Levin >> >>

[GIT PULL for-4.9 20/48] net/mlx4_core: Fix VF overwrite of module param which disables DMFS on new probed PFs

From: Majd Dibbiny [ Upstream commit 95f1ba9a24af9769f6e20dfe9a77c863f253f311 ] In the VF driver, module parameter mlx4_log_num_mgm_entry_size was mistakenly overwritten -- and in a manner which overrode the device-managed flow steering option encoded in the parameter.

[GIT PULL for-4.9 20/48] net/mlx4_core: Fix VF overwrite of module param which disables DMFS on new probed PFs

From: Majd Dibbiny [ Upstream commit 95f1ba9a24af9769f6e20dfe9a77c863f253f311 ] In the VF driver, module parameter mlx4_log_num_mgm_entry_size was mistakenly overwritten -- and in a manner which overrode the device-managed flow steering option encoded in the parameter. log_num_mgm_entry_size

[GIT PULL for-4.9 18/48] md/linear: shutup lockdep warnning

From: Shaohua Li [ Upstream commit d939cdfde34f50b95254b375f498447c82190b3e ] Commit 03a9e24(md linear: fix a race between linear_add() and linear_congested()) introduces the warnning. Acked-by: Coly Li Signed-off-by: Shaohua Li Signed-off-by: Sasha

[GIT PULL for-4.9 18/48] md/linear: shutup lockdep warnning

From: Shaohua Li [ Upstream commit d939cdfde34f50b95254b375f498447c82190b3e ] Commit 03a9e24(md linear: fix a race between linear_add() and linear_congested()) introduces the warnning. Acked-by: Coly Li Signed-off-by: Shaohua Li Signed-off-by: Sasha Levin --- drivers/md/linear.c | 3 ++- 1

[GIT PULL for-4.9 16/48] Btrfs: send, fix failure to rename top level inode due to name collision

From: Robbie Ko [ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ] Under certain situations, an incremental send operation can fail due to a premature attempt to create a new top level inode (a direct child of the subvolume/snapshot root) whose name collides

[GIT PULL for-4.9 04/48] irqchip/crossbar: Fix incorrect type of local variables

From: Franck Demathieu [ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ] The max and entry variables are unsigned according to the dt-bindings. Fix following 3 sparse issues (-Wtypesign): drivers/irqchip/irq-crossbar.c:222:52: warning: incorrect type in

[GIT PULL for-4.9 16/48] Btrfs: send, fix failure to rename top level inode due to name collision

From: Robbie Ko [ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ] Under certain situations, an incremental send operation can fail due to a premature attempt to create a new top level inode (a direct child of the subvolume/snapshot root) whose name collides with another inode that

[GIT PULL for-4.9 04/48] irqchip/crossbar: Fix incorrect type of local variables

From: Franck Demathieu [ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ] The max and entry variables are unsigned according to the dt-bindings. Fix following 3 sparse issues (-Wtypesign): drivers/irqchip/irq-crossbar.c:222:52: warning: incorrect type in argument 3 (different

[GIT PULL for-4.9 09/48] mac80211: fix power saving clients handling in iwlwifi

From: Emmanuel Grumbach [ Upstream commit d98937f4ea713d21e0fcc345919f86c877dd8d6f ] iwlwifi now supports RSS and can't let mac80211 track the PS state based on the Rx frames since they can come out of order. iwlwifi is now advertising AP_LINK_PS, and uses explicit

[GIT PULL for-4.9 09/48] mac80211: fix power saving clients handling in iwlwifi

From: Emmanuel Grumbach [ Upstream commit d98937f4ea713d21e0fcc345919f86c877dd8d6f ] iwlwifi now supports RSS and can't let mac80211 track the PS state based on the Rx frames since they can come out of order. iwlwifi is now advertising AP_LINK_PS, and uses explicit notifications to teach

[GIT PULL for-4.9 15/48] sched/fair: Update rq clock before changing a task's CPU affinity

From: Wanpeng Li [ Upstream commit a499c3ead88ccf147fc50689e85a530ad923ce36 ] This is triggered during boot when CONFIG_SCHED_DEBUG is enabled: [ cut here ] WARNING: CPU: 6 PID: 81 at kernel/sched/sched.h:812 set_next_entity+0x11d/0x380

[GIT PULL for-4.9 15/48] sched/fair: Update rq clock before changing a task's CPU affinity

From: Wanpeng Li [ Upstream commit a499c3ead88ccf147fc50689e85a530ad923ce36 ] This is triggered during boot when CONFIG_SCHED_DEBUG is enabled: [ cut here ] WARNING: CPU: 6 PID: 81 at kernel/sched/sched.h:812 set_next_entity+0x11d/0x380 rq->clock_update_flags <

[GIT PULL for-4.9 06/48] mac80211_hwsim: check HWSIM_ATTR_RADIO_NAME length

From: Johannes Berg [ Upstream commit ff4dd73dd2b4806419f8ff65cbce11d5019548d0 ] Unfortunately, the nla policy was defined to have HWSIM_ATTR_RADIO_NAME as an NLA_STRING, rather than NLA_NUL_STRING, so we can't use it as a NUL-terminated string in the kernel. Rather

[GIT PULL for-4.9 06/48] mac80211_hwsim: check HWSIM_ATTR_RADIO_NAME length

From: Johannes Berg [ Upstream commit ff4dd73dd2b4806419f8ff65cbce11d5019548d0 ] Unfortunately, the nla policy was defined to have HWSIM_ATTR_RADIO_NAME as an NLA_STRING, rather than NLA_NUL_STRING, so we can't use it as a NUL-terminated string in the kernel. Rather than break the API,

[GIT PULL for-4.9 03/48] watchdog: kempld: fix gcc-4.3 build

From: Arnd Bergmann [ Upstream commit 3736d4eb6af37492aeded7fec0072dedd959c842 ] gcc-4.3 can't decide whether the constant value in kempld_prescaler[PRESCALER_21] is built-time constant or not, and gets confused by the logic in do_div(): drivers/watchdog/kempld_wdt.o: In

[GIT PULL for-4.9 05/48] initramfs: finish fput() before accessing any binary from initramfs

From: Lokesh Vutla [ Upstream commit 08865514805d2de8e7002fa8149c5de3e391f412 ] Commit 4a9d4b024a31 ("switch fput to task_work_add") implements a schedule_work() for completing fput(), but did not guarantee calling __fput() after unpacking initramfs. Because of this, there

[GIT PULL for-4.9 03/48] watchdog: kempld: fix gcc-4.3 build

From: Arnd Bergmann [ Upstream commit 3736d4eb6af37492aeded7fec0072dedd959c842 ] gcc-4.3 can't decide whether the constant value in kempld_prescaler[PRESCALER_21] is built-time constant or not, and gets confused by the logic in do_div(): drivers/watchdog/kempld_wdt.o: In function

[GIT PULL for-4.9 05/48] initramfs: finish fput() before accessing any binary from initramfs

From: Lokesh Vutla [ Upstream commit 08865514805d2de8e7002fa8149c5de3e391f412 ] Commit 4a9d4b024a31 ("switch fput to task_work_add") implements a schedule_work() for completing fput(), but did not guarantee calling __fput() after unpacking initramfs. Because of this, there is a possibility

[GIT PULL for-4.9 14/48] f2fs: do SSR for data when there is enough free space

From: Yunlong Song [ Upstream commit 035e97adab26c1121cedaeb9bd04cf48a8e8cf51 ] In allocate_segment_by_default(), need_SSR() already detected it's time to do SSR. So, let's try to find victims for data segments more aggressively in time. Signed-off-by: Yunlong Song

[GIT PULL for-4.9 14/48] f2fs: do SSR for data when there is enough free space

From: Yunlong Song [ Upstream commit 035e97adab26c1121cedaeb9bd04cf48a8e8cf51 ] In allocate_segment_by_default(), need_SSR() already detected it's time to do SSR. So, let's try to find victims for data segments more aggressively in time. Signed-off-by: Yunlong Song Signed-off-by: Jaegeuk Kim

[GIT PULL for-4.9 01/48] xen-netback: Use GFP_ATOMIC to allocate hash

From: Anoob Soman [ Upstream commit 9f674e48c13dcbc31ac903433727837795b81efe ] Allocation of new_hash, inside xenvif_new_hash(), always happen in softirq context, so use GFP_ATOMIC instead of GFP_KERNEL for new hash allocation. Signed-off-by: Anoob Soman

[GIT PULL for-4.9 01/48] xen-netback: Use GFP_ATOMIC to allocate hash

From: Anoob Soman [ Upstream commit 9f674e48c13dcbc31ac903433727837795b81efe ] Allocation of new_hash, inside xenvif_new_hash(), always happen in softirq context, so use GFP_ATOMIC instead of GFP_KERNEL for new hash allocation. Signed-off-by: Anoob Soman Signed-off-by: David S. Miller

[GIT PULL for-4.9 11/48] staging: vchiq_2835_arm: Make cache-line-size a required DT property

From: Michael Zoran [ Upstream commit 6cf1bf636a067eb308cb3a8322b9d6b1844a075d ] The original github source allowed for the cache-line-size property to be missing. Since recent firmwares also require this property, it makes sense to always require it in the driver as well.

[GIT PULL for-4.9 11/48] staging: vchiq_2835_arm: Make cache-line-size a required DT property

From: Michael Zoran [ Upstream commit 6cf1bf636a067eb308cb3a8322b9d6b1844a075d ] The original github source allowed for the cache-line-size property to be missing. Since recent firmwares also require this property, it makes sense to always require it in the driver as well. If the

[GIT PULL for-4.9 10/48] net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

From: Eric Dumazet [ Upstream commit 47d3a07528ecbbccf53bc4390d70b4e3d1c04fcf ] The cited commit makes a great job of finding optimal shift/multiplier values assuming a 10 seconds wrap around, but forgot to change the overflow_period computation. It overflows in

[GIT PULL for-4.9 10/48] net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

From: Eric Dumazet [ Upstream commit 47d3a07528ecbbccf53bc4390d70b4e3d1c04fcf ] The cited commit makes a great job of finding optimal shift/multiplier values assuming a 10 seconds wrap around, but forgot to change the overflow_period computation. It overflows in cyclecounter_cyc2ns(), and the

[GIT PULL for-4.9 29/48] qede: Prevent index problems in loopback test

From: Sudarsana Reddy Kalluru [ Upstream commit afe981d664aeeebc8d1bcbd7d2070b5432edaecb ] Driver currently utilizes the same loop variable in two nested loops. Signed-off-by: Sudarsana Reddy Kalluru Signed-off-by: Yuval Mintz

[GIT PULL for-4.9 29/48] qede: Prevent index problems in loopback test

From: Sudarsana Reddy Kalluru [ Upstream commit afe981d664aeeebc8d1bcbd7d2070b5432edaecb ] Driver currently utilizes the same loop variable in two nested loops. Signed-off-by: Sudarsana Reddy Kalluru Signed-off-by: Yuval Mintz Signed-off-by: David S. Miller Signed-off-by: Sasha Levin ---

[GIT PULL for-4.9 07/48] ALSA: hda: Add Geminilake HDMI codec ID

From: Vinod Koul [ Upstream commit 126cfa2f5e15ae2ca7f70be71b07e6cd8d2b44d1 ] Geminilake HDMI codec 0x280d is similar to previous platforms, so add it with similar ops as previous. Signed-off-by: Senthilnathan Veppur Signed-off-by: Vinod

[GIT PULL for-4.9 07/48] ALSA: hda: Add Geminilake HDMI codec ID

From: Vinod Koul [ Upstream commit 126cfa2f5e15ae2ca7f70be71b07e6cd8d2b44d1 ] Geminilake HDMI codec 0x280d is similar to previous platforms, so add it with similar ops as previous. Signed-off-by: Senthilnathan Veppur Signed-off-by: Vinod Koul Signed-off-by: Takashi Iwai Signed-off-by: Sasha

[GIT PULL for-4.9 08/48] qed: Don't use attention PTT for configuring BW

From: "Mintz, Yuval" [ Upstream commit 6f437d431930ff86e4a971d29321951faadb97c7 ] Commit 653d2ffd6405 ("qed*: Fix link indication race") introduced another race - one of the inner functions called from the link-change flow is explicitly using the slowpath context

[GIT PULL for-4.9 08/48] qed: Don't use attention PTT for configuring BW

From: "Mintz, Yuval" [ Upstream commit 6f437d431930ff86e4a971d29321951faadb97c7 ] Commit 653d2ffd6405 ("qed*: Fix link indication race") introduced another race - one of the inner functions called from the link-change flow is explicitly using the slowpath context dedicated PTT instead of

[GIT PULL for-4.9 21/48] crypto: xts - Add ECB dependency

From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher the XTS mode is based on ECB, so the mode must select ECB otherwise it can fail to initialize.

[GIT PULL for-4.9 21/48] crypto: xts - Add ECB dependency

From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher the XTS mode is based on ECB, so the mode must select ECB otherwise it can fail to initialize. Signed-off-by: Milan

[GIT PULL for-4.9 23/48] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by

[GIT PULL for-4.9 23/48] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code

[GIT PULL for-4.9 13/48] iio: adc: xilinx: Fix error handling

From: Christophe JAILLET [ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ] Reorder error handling labels in order to match the way resources have been allocated. Signed-off-by: Christophe JAILLET Acked-by: Lars-Peter

[GIT PULL for-4.9 13/48] iio: adc: xilinx: Fix error handling

From: Christophe JAILLET [ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ] Reorder error handling labels in order to match the way resources have been allocated. Signed-off-by: Christophe JAILLET Acked-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron Signed-off-by: Sasha

[GIT PULL for-4.9 28/48] net: mvpp2: release reference to txq_cpu[] entry after unmapping

From: Thomas Petazzoni [ Upstream commit 36fb7435b6ac4d288a2d4deea8934f9456ab46b6 ] The mvpp2_txq_bufs_free() function is called upon TX completion to DMA unmap TX buffers, and free the corresponding SKBs. It gets the references to the SKB to free and the

[GIT PULL for-4.9 28/48] net: mvpp2: release reference to txq_cpu[] entry after unmapping

From: Thomas Petazzoni [ Upstream commit 36fb7435b6ac4d288a2d4deea8934f9456ab46b6 ] The mvpp2_txq_bufs_free() function is called upon TX completion to DMA unmap TX buffers, and free the corresponding SKBs. It gets the references to the SKB to free and the DMA buffer to unmap from a per-CPU

[GIT PULL for-4.9 25/48] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

From: Dan Carpenter [ Upstream commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b ] We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC handler") Signed-off-by: Dan Carpenter

[GIT PULL for-4.9 25/48] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

From: Dan Carpenter [ Upstream commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b ] We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC handler") Signed-off-by: Dan Carpenter Reviewed-by: Hannes Reinecke Signed-off-by: Martin K. Petersen

[GIT PULL for-4.9 24/48] slub: do not merge cache if slub_debug contains a never-merge flag

From: Grygorii Maistrenko [ Upstream commit c6e28895a4372992961888ffaadc9efc643b5bfe ] In case CONFIG_SLUB_DEBUG_ON=n, find_mergeable() gets debug features from commandline but never checks if there are features from the SLAB_NEVER_MERGE set. As a result selected by

[GIT PULL for-4.9 24/48] slub: do not merge cache if slub_debug contains a never-merge flag

From: Grygorii Maistrenko [ Upstream commit c6e28895a4372992961888ffaadc9efc643b5bfe ] In case CONFIG_SLUB_DEBUG_ON=n, find_mergeable() gets debug features from commandline but never checks if there are features from the SLAB_NEVER_MERGE set. As a result selected by slub_debug caches are

[GIT PULL for-4.9 26/48] ASoC: mediatek: add I2C dependency for CS42XX8

From: Arnd Bergmann [ Upstream commit 72cedf599fcebfd6cd2550274d7855838068d28c ] We should not select drivers that depend on I2C when that is disabled, as it results in a build error: warning: (SND_SOC_MT2701_CS42448) selects SND_SOC_CS42XX8_I2C which has unmet direct

[GIT PULL for-4.9 26/48] ASoC: mediatek: add I2C dependency for CS42XX8

From: Arnd Bergmann [ Upstream commit 72cedf599fcebfd6cd2550274d7855838068d28c ] We should not select drivers that depend on I2C when that is disabled, as it results in a build error: warning: (SND_SOC_MT2701_CS42448) selects SND_SOC_CS42XX8_I2C which has unmet direct dependencies (SOUND &&

[GIT PULL for-4.9 19/48] sparc64: Migrate hvcons irq to panicked cpu

From: Vijay Kumar [ Upstream commit 7dd4fcf5b70694dc961eb6b954673e4fc9730dbd ] On panic, all other CPUs are stopped except the one which had hit panic. To keep console alive, we need to migrate hvcons irq to panicked CPU. Signed-off-by: Vijay Kumar

[GIT PULL for-4.9 27/48] drm/amdgpu: refuse to reserve io mem for split VRAM buffers

From: Nicolai Hähnle [ Upstream commit 4694335dad7357e9b3d7822ab13049014d74d8b0 ] When the fast blit path fails while attempting to move a buffer from RAM to VRAM, we fall back to a CPU-based memcpy that cannot handle split VRAM buffers. Instead of crashing, simply fail

[GIT PULL for-4.9 19/48] sparc64: Migrate hvcons irq to panicked cpu

From: Vijay Kumar [ Upstream commit 7dd4fcf5b70694dc961eb6b954673e4fc9730dbd ] On panic, all other CPUs are stopped except the one which had hit panic. To keep console alive, we need to migrate hvcons irq to panicked CPU. Signed-off-by: Vijay Kumar Signed-off-by: David S. Miller

[GIT PULL for-4.9 27/48] drm/amdgpu: refuse to reserve io mem for split VRAM buffers

From: Nicolai Hähnle [ Upstream commit 4694335dad7357e9b3d7822ab13049014d74d8b0 ] When the fast blit path fails while attempting to move a buffer from RAM to VRAM, we fall back to a CPU-based memcpy that cannot handle split VRAM buffers. Instead of crashing, simply fail the buffer move.

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