[PATCH 4.4 071/163] drm/radeon: fix vertical bars appear on monitor (v2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Prosyak commit 5d5b7803c49bbb01bdf4c6e95e8314d0515b9484 upstream. When crtc/timing is disabled on boot the dig block should be stopped in order ignore timing

[PATCH 4.4 073/163] drm/nouveau/gr/gf100: select a stream master to fixup tfb offset queries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 28dca90533750c7e31e8641c3df426bad9c12941 upstream. Signed-off-by: Ben Skeggs Signed-off-by: Greg Kroah-Hartman

[PATCH 4.4 009/163] ARM: OMAP2+: hwmod: Fix updating of sysconfig register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 3ca4a238106dedc285193ee47f494a6584b6fd2f upstream. Commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on idle when necessary") talks about

[PATCH 4.4 005/163] KVM: arm/arm64: Handle forward time correction gracefully

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 1c5631c73fc2261a5df64a72c155cb53dcdc0c45 upstream. On a host that runs NTP, corrections can have a direct impact on the background timer that we

Re: [PATCH v7 1/7] regulator: fixed: add support for ACPI interface

Hi, On 05/02/2016 07:00 PM, Mark Brown wrote: > On Fri, Apr 29, 2016 at 02:26:32PM +0800, Lu Baolu wrote: > >> +gpiod = gpiod_get(dev, "vbus_en", GPIOD_ASIS); >> +if (IS_ERR(gpiod)) >> +return PTR_ERR(gpiod); > This is clearly an inappropriate name for the signal in generic

[PATCH 4.4 075/163] drm/dp/mst: Restore primary hub guid on resume

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lyude commit 9dc0487d96a0396367a1451b31873482080b527f upstream. Some hubs are forgetful, and end up forgetting whatever GUID we set previously after we do a suspend/resume

[PATCH 4.4 080/163] drm/amdkfd: uninitialized variable in dbgdev_wave_control_set_registers()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 93fce954427effee89e44a976299b15dd75b4bbc upstream. At the end of the function we expect "status" to be zero, but it's either -EINVAL or uninitialized. Fixes: 788bf83db301

[PATCH 4.4 077/163] pwm: brcmstb: Fix check of devm_ioremap_resource() return code

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit c5857e3f94ab2719dfac649a146cb5dd6f21fcf3 upstream. The change fixes potential oops while accessing iomem on invalid address if devm_ioremap_resource() fails due to

[PATCH 4.4 071/163] drm/radeon: fix vertical bars appear on monitor (v2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Prosyak commit 5d5b7803c49bbb01bdf4c6e95e8314d0515b9484 upstream. When crtc/timing is disabled on boot the dig block should be stopped in order ignore timing from crtc, reset the

[PATCH 4.4 073/163] drm/nouveau/gr/gf100: select a stream master to fixup tfb offset queries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 28dca90533750c7e31e8641c3df426bad9c12941 upstream. Signed-off-by: Ben Skeggs Signed-off-by: Greg Kroah-Hartman --- drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c |2

[PATCH 4.4 009/163] ARM: OMAP2+: hwmod: Fix updating of sysconfig register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 3ca4a238106dedc285193ee47f494a6584b6fd2f upstream. Commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on idle when necessary") talks about verification of

[PATCH 4.4 005/163] KVM: arm/arm64: Handle forward time correction gracefully

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 1c5631c73fc2261a5df64a72c155cb53dcdc0c45 upstream. On a host that runs NTP, corrections can have a direct impact on the background timer that we program on the behalf of a

Re: [PATCH v7 1/7] regulator: fixed: add support for ACPI interface

Hi, On 05/02/2016 07:00 PM, Mark Brown wrote: > On Fri, Apr 29, 2016 at 02:26:32PM +0800, Lu Baolu wrote: > >> +gpiod = gpiod_get(dev, "vbus_en", GPIOD_ASIS); >> +if (IS_ERR(gpiod)) >> +return PTR_ERR(gpiod); > This is clearly an inappropriate name for the signal in generic

[PATCH 4.4 075/163] drm/dp/mst: Restore primary hub guid on resume

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lyude commit 9dc0487d96a0396367a1451b31873482080b527f upstream. Some hubs are forgetful, and end up forgetting whatever GUID we set previously after we do a suspend/resume cycle. This can lead

Re: [PATCH v4 11/12] zsmalloc: page migration support

On Tue, May 03, 2016 at 09:43:59AM +0900, Minchan Kim wrote: > Good morning, Chulmin > > On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: > > Hello, Minchan! > > > > On 2016년 04월 27일 16:48, Minchan Kim wrote: > > >This patch introduces run-time migration feature for zspage. > > > > >

[PATCH 4.4 076/163] drm/dp/mst: Get validated port ref in drm_dp_update_payload_part1()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: cp...@redhat.com commit 263efde31f97c498e1ebad30e4d2906609d7ad6b upstream. We can thank KASAN for finding this, otherwise I probably would have spent hours on it. This fixes

[PATCH 4.4 015/163] usb: hcd: out of bounds access in for_each_companion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Robert Dobrowolski commit e86103a75705c7c530768f4ffaba74cf382910f2 upstream. On BXT platform Host Controller and Device Controller figure as same PCI device

[PATCH 4.4 076/163] drm/dp/mst: Get validated port ref in drm_dp_update_payload_part1()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: cp...@redhat.com commit 263efde31f97c498e1ebad30e4d2906609d7ad6b upstream. We can thank KASAN for finding this, otherwise I probably would have spent hours on it. This fixes a somewhat harder

[PATCH 4.4 015/163] usb: hcd: out of bounds access in for_each_companion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Robert Dobrowolski commit e86103a75705c7c530768f4ffaba74cf382910f2 upstream. On BXT platform Host Controller and Device Controller figure as same PCI device but with different device function.

Re: [PATCH v4 11/12] zsmalloc: page migration support

On Tue, May 03, 2016 at 09:43:59AM +0900, Minchan Kim wrote: > Good morning, Chulmin > > On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: > > Hello, Minchan! > > > > On 2016년 04월 27일 16:48, Minchan Kim wrote: > > >This patch introduces run-time migration feature for zspage. > > > > >

[PATCH 4.4 084/163] i2c: cpm: Fix build break due to incompatible pointer types

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 609d5a1b2b35bb62b4b3750396e55453160c2a17 upstream. Since commit ea8daa7b9784 ("kbuild: Add option to turn incompatible pointer check into error"),

[PATCH 4.4 084/163] i2c: cpm: Fix build break due to incompatible pointer types

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 609d5a1b2b35bb62b4b3750396e55453160c2a17 upstream. Since commit ea8daa7b9784 ("kbuild: Add option to turn incompatible pointer check into error"), assignments from an

[PATCH 4.4 046/163] iwlwifi: mvm: fix memory leak in paging

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matti Gottlieb commit 7fdf9663261cc77a516396fec82cee8a8ea07e76 upstream. Currently paging download buffer is freed during the the unloading of the opmode which

[PATCH 4.4 083/163] perf intel-pt: Fix segfault tracing transactions

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 1342e0b7a6c1a060c593037fbac9f4b717f1cb3b upstream. Tracing a workload that uses transactions gave a seg fault as follows: perf record -e

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/data.c between commit: 6bfc49197eba ("f2fs: issue cache flush on direct IO") from the f2fs tree and commit: c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO") from the vfs tree. I fixed

[PATCH 4.4 043/163] cpufreq: intel_pstate: Fix processing for turbo activation ratio

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada commit 1becf03545a0859ceaaf9e8c2d9861882a71cb01 upstream. When the config TDP level is not nominal (level = 0), the MSR values for

[PATCH 4.4 081/163] drm/i915: Fixup the free space logic in ring_prepare

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Akash Goel commit d43f3ebf12f59c57782ec652da65ef61c2662b40 upstream. Currently for the case where there is enough space at the end of Ring buffer for accommodating only

[PATCH 4.4 045/163] iwlwifi: pcie: lower the debug level for RSA semaphore access

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 9fc515bc9e735c10cd327f05c20f5ef69474188d upstream. IWL_INFO is not an error but still printed by default. "can't access the RSA semaphore

[PATCH 4.4 086/163] toshiba_acpi: Fix regression caused by hotkey enabling value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Azael Avalos commit a30b8f81d9d6fe24eab8a023794548b048f08e3c upstream. Commit 52cbae0127ad ("toshiba_acpi: Change default Hotkey enabling value") changed the hotkeys

Re: [PATCH 2/2] zram: user per-cpu compression streams

On Mon, May 02, 2016 at 06:21:57PM +0900, Sergey Senozhatsky wrote: > On (05/02/16 17:28), Minchan Kim wrote: > [..] > > > aha... I misunderstood you. I thought you talked about the test results > > > in particular, not about zram stats in general. hm, given that we don't > > > close the door for

[PATCH 4.4 085/163] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream. The exynos5 I2C controller driver always prepares and enables a clock before using it

[PATCH 4.4 043/163] cpufreq: intel_pstate: Fix processing for turbo activation ratio

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada commit 1becf03545a0859ceaaf9e8c2d9861882a71cb01 upstream. When the config TDP level is not nominal (level = 0), the MSR values for reading level 1 and level 2 ratios

[PATCH 4.4 081/163] drm/i915: Fixup the free space logic in ring_prepare

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Akash Goel commit d43f3ebf12f59c57782ec652da65ef61c2662b40 upstream. Currently for the case where there is enough space at the end of Ring buffer for accommodating only the base request, the

[PATCH 4.4 045/163] iwlwifi: pcie: lower the debug level for RSA semaphore access

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 9fc515bc9e735c10cd327f05c20f5ef69474188d upstream. IWL_INFO is not an error but still printed by default. "can't access the RSA semaphore it is write protected" seems

[PATCH 4.4 086/163] toshiba_acpi: Fix regression caused by hotkey enabling value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Azael Avalos commit a30b8f81d9d6fe24eab8a023794548b048f08e3c upstream. Commit 52cbae0127ad ("toshiba_acpi: Change default Hotkey enabling value") changed the hotkeys enabling value, as it was

Re: [PATCH 2/2] zram: user per-cpu compression streams

On Mon, May 02, 2016 at 06:21:57PM +0900, Sergey Senozhatsky wrote: > On (05/02/16 17:28), Minchan Kim wrote: > [..] > > > aha... I misunderstood you. I thought you talked about the test results > > > in particular, not about zram stats in general. hm, given that we don't > > > close the door for

[PATCH 4.4 085/163] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream. The exynos5 I2C controller driver always prepares and enables a clock before using it and then disables

[PATCH 4.4 083/163] perf intel-pt: Fix segfault tracing transactions

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 1342e0b7a6c1a060c593037fbac9f4b717f1cb3b upstream. Tracing a workload that uses transactions gave a seg fault as follows: perf record -e intel_pt// workload perf

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/data.c between commit: 6bfc49197eba ("f2fs: issue cache flush on direct IO") from the f2fs tree and commit: c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO") from the vfs tree. I fixed

[PATCH 4.4 046/163] iwlwifi: mvm: fix memory leak in paging

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matti Gottlieb commit 7fdf9663261cc77a516396fec82cee8a8ea07e76 upstream. Currently paging download buffer is freed during the the unloading of the opmode which happens when the driver is

Re: [PATCH v4 11/12] zsmalloc: page migration support

On 2016년 05월 03일 09:43, Minchan Kim wrote: Good morning, Chulmin On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: Hello, Minchan! On 2016년 04월 27일 16:48, Minchan Kim wrote: This patch introduces run-time migration feature for zspage. For migration, VM uses page.lru field so it

[PATCH 4.4 044/163] s390/pci: add extra padding to function measurement block

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa upstream. Newer machines might use a different (larger) format for function measurement blocks. To

Re: [PATCH v4 11/12] zsmalloc: page migration support

On 2016년 05월 03일 09:43, Minchan Kim wrote: Good morning, Chulmin On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: Hello, Minchan! On 2016년 04월 27일 16:48, Minchan Kim wrote: This patch introduces run-time migration feature for zspage. For migration, VM uses page.lru field so it

[PATCH 4.4 044/163] s390/pci: add extra padding to function measurement block

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa upstream. Newer machines might use a different (larger) format for function measurement blocks. To ensure that we comply with the

[PATCH 4.4 089/163] ASoC: ssm4567: Reset device before regcache_sync()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 712a8038cc24dba668afe82f0413714ca87184e0 upstream. When the ssm4567 is powered up the driver calles regcache_sync() to restore the register map

[PATCH 4.4 089/163] ASoC: ssm4567: Reset device before regcache_sync()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 712a8038cc24dba668afe82f0413714ca87184e0 upstream. When the ssm4567 is powered up the driver calles regcache_sync() to restore the register map content.

[PATCH 4.4 107/163] mm/hwpoison: fix wrong num_poisoned_pages accounting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Minchan Kim commit d7e69488bd04de165667f6bc741c1c0ec6042ab9 upstream. Currently, migration code increses num_poisoned_pages on *failed* migration page as well as

[PATCH 4.4 107/163] mm/hwpoison: fix wrong num_poisoned_pages accounting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Minchan Kim commit d7e69488bd04de165667f6bc741c1c0ec6042ab9 upstream. Currently, migration code increses num_poisoned_pages on *failed* migration page as well as successfully migrated one at

[PATCH 4.4 109/163] USB: usbip: fix potential out-of-bounds write

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ignat Korchagin commit b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb upstream. Fix potential out-of-bounds write to urb->transfer_buffer usbip handles network

[PATCH 4.4 109/163] USB: usbip: fix potential out-of-bounds write

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ignat Korchagin commit b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb upstream. Fix potential out-of-bounds write to urb->transfer_buffer usbip handles network communication directly in the kernel.

[PATCH 4.4 112/163] Revert "regulator: core: Fix nested locking of supplies"

4.4-stable review patch. If anyone has any objections, please let me know. -- This reverts commit b1999fa6e8145305a6c8bda30ea20783717708e6 which was commit 70a7fb80e85ae7f78f8e90cec3fbd862ea6a4d4b upstream. It causes run-time breakage in the 4.4-stable tree and more patches are

[PATCH 4.4 112/163] Revert "regulator: core: Fix nested locking of supplies"

4.4-stable review patch. If anyone has any objections, please let me know. -- This reverts commit b1999fa6e8145305a6c8bda30ea20783717708e6 which was commit 70a7fb80e85ae7f78f8e90cec3fbd862ea6a4d4b upstream. It causes run-time breakage in the 4.4-stable tree and more patches are

[PATCH 4.4 111/163] [media] videobuf2-v4l2: Verify planes array in buffer dequeueing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sakari Ailus commit 2c1f6951a8a82e6de0d82b1158b5e493fc6c54ab upstream. When a buffer is being dequeued using VIDIOC_DQBUF IOCTL, the exact buffer which will be

[PATCH 4.4 111/163] [media] videobuf2-v4l2: Verify planes array in buffer dequeueing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sakari Ailus commit 2c1f6951a8a82e6de0d82b1158b5e493fc6c54ab upstream. When a buffer is being dequeued using VIDIOC_DQBUF IOCTL, the exact buffer which will be dequeued is not known until the

[PATCH 4.4 110/163] [media] videobuf2-core: Check user space planes array in dqbuf

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sakari Ailus commit e7e0c3e26587749b62d17b9dd0532874186c77f7 upstream. The number of planes in videobuf2 is specific to a buffer. In order to verify that the

[PATCH 4.4 110/163] [media] videobuf2-core: Check user space planes array in dqbuf

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sakari Ailus commit e7e0c3e26587749b62d17b9dd0532874186c77f7 upstream. The number of planes in videobuf2 is specific to a buffer. In order to verify that the planes array provided by the user

[PATCH 4.4 113/163] regulator: core: fix regulator_lock_supply regression

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit bb41897e38c53458a88b271f2fbcd905ee1f9584 upstream. As noticed by Geert Uytterhoeven, my patch to avoid a harmless build warning in regulator_lock_supply()

[PATCH 4.4 113/163] regulator: core: fix regulator_lock_supply regression

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit bb41897e38c53458a88b271f2fbcd905ee1f9584 upstream. As noticed by Geert Uytterhoeven, my patch to avoid a harmless build warning in regulator_lock_supply() was total crap

[PATCH 4.4 114/163] regulator: core: Ensure we lock all regulators

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 49a6bb7a1c0963f260e4b0dcc2c0e56ec65a28b2 upstream. The latest workaround for the lockdep interface's not using the second argument of mutex_lock_nested()

[PATCH 4.4 114/163] regulator: core: Ensure we lock all regulators

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 49a6bb7a1c0963f260e4b0dcc2c0e56ec65a28b2 upstream. The latest workaround for the lockdep interface's not using the second argument of mutex_lock_nested() changed the loop

[PATCH 4.4 117/163] spi/rockchip: Make sure spi clk is on in rockchip_spi_set_cs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Huibin Hong commit b920cc3191d7612f26f36ee494e05b5ffd9044c0 upstream. Rockchip_spi_set_cs could be called by spi_setup, but spi_setup may be called by device driver

[PATCH 4.4 116/163] locking/mcs: Fix mcs_spin_lock() ordering

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 920c720aa5aa3900a7f1689228fdfc2580a91e7e upstream. Similar to commit b4b29f94856a ("locking/osq: Fix ordering of node initialisation in osq_lock")

[PATCH 4.4 117/163] spi/rockchip: Make sure spi clk is on in rockchip_spi_set_cs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Huibin Hong commit b920cc3191d7612f26f36ee494e05b5ffd9044c0 upstream. Rockchip_spi_set_cs could be called by spi_setup, but spi_setup may be called by device driver after runtime suspend. Then

[PATCH 4.4 116/163] locking/mcs: Fix mcs_spin_lock() ordering

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 920c720aa5aa3900a7f1689228fdfc2580a91e7e upstream. Similar to commit b4b29f94856a ("locking/osq: Fix ordering of node initialisation in osq_lock") the use of

[PATCH 4.4 108/163] cgroup: make sure a parent css isnt freed before its children

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4 upstream. There are three subsystem callbacks in css shutdown path - css_offline(), css_released() and css_free().

[PATCH 4.4 108/163] cgroup: make sure a parent css isnt freed before its children

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4 upstream. There are three subsystem callbacks in css shutdown path - css_offline(), css_released() and css_free(). Except for

[PATCH 4.4 120/163] regulator: s5m8767: fix get_register() error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit e07ff9434167981c993a26d2edbbcb8e13801dbb upstream. The s5m8767_pmic_probe() function calls s5m8767_get_register() to read data without checking the return

[PATCH 4.4 090/163] ASoC: dapm: Make sure we have a card when displaying component widgets

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 47325078f2a3e543150e7df967e45756b2fff7ec upstream. The dummy component is reused for all cards so we special case and don't bind it to any of them. This

[PATCH 4.4 120/163] regulator: s5m8767: fix get_register() error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit e07ff9434167981c993a26d2edbbcb8e13801dbb upstream. The s5m8767_pmic_probe() function calls s5m8767_get_register() to read data without checking the return code, which

[PATCH 4.4 090/163] ASoC: dapm: Make sure we have a card when displaying component widgets

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 47325078f2a3e543150e7df967e45756b2fff7ec upstream. The dummy component is reused for all cards so we special case and don't bind it to any of them. This means that code like

[PATCH 4.4 128/163] PM / Domains: Fix removal of a subdomain

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit beda5fc1ff9b527059290a97b672d2ee0eb7b92f upstream. Commit 30e7a65b3fdb (PM / Domains: Ensure subdomain is not in use before removing) added a test to

[PATCH 4.4 131/163] rtc: ds1685: passing bogus values to irq_restore

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 8c09b9fdecab1f4a289f07b46e2ad174b6641928 upstream. We call spin_lock_irqrestore with "flags" set to zero instead of to the value from

[PATCH 4.4 128/163] PM / Domains: Fix removal of a subdomain

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit beda5fc1ff9b527059290a97b672d2ee0eb7b92f upstream. Commit 30e7a65b3fdb (PM / Domains: Ensure subdomain is not in use before removing) added a test to ensure that a subdomain

[PATCH 4.4 131/163] rtc: ds1685: passing bogus values to irq_restore

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 8c09b9fdecab1f4a289f07b46e2ad174b6641928 upstream. We call spin_lock_irqrestore with "flags" set to zero instead of to the value from spin_lock_irqsave(). Fixes:

[PATCH 4.4 118/163] irqchip/sunxi-nmi: Fix error check of of_io_request_and_map()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit cfe199afefe6201e998ddc07102fc1fdb55f196c upstream. The of_io_request_and_map() returns a valid pointer in iomem region or ERR_PTR(), check for NULL

[PATCH 4.4 119/163] irqchip/mxs: Fix error check of of_io_request_and_map()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit edf8fcdc6b254236be005851af35ea5e826e7e09 upstream. The of_io_request_and_map() returns a valid pointer in iomem region or ERR_PTR(), check for NULL

[PATCH 4.4 118/163] irqchip/sunxi-nmi: Fix error check of of_io_request_and_map()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit cfe199afefe6201e998ddc07102fc1fdb55f196c upstream. The of_io_request_and_map() returns a valid pointer in iomem region or ERR_PTR(), check for NULL always fails and

[PATCH 4.4 119/163] irqchip/mxs: Fix error check of of_io_request_and_map()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit edf8fcdc6b254236be005851af35ea5e826e7e09 upstream. The of_io_request_and_map() returns a valid pointer in iomem region or ERR_PTR(), check for NULL always fails and

[PATCH 4.4 134/163] drivers/misc/ad525x_dpot: AD5274 fix RDAC read back errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Hennerich commit f3df53e4d70b5736368a8fe8aa1bb70c1cb1f577 upstream. Fix RDAC read back errors caused by a typo. Value must shift by 2. Fixes:

[PATCH 4.4 134/163] drivers/misc/ad525x_dpot: AD5274 fix RDAC read back errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Hennerich commit f3df53e4d70b5736368a8fe8aa1bb70c1cb1f577 upstream. Fix RDAC read back errors caused by a typo. Value must shift by 2. Fixes: a4bd394956f2

[PATCH 4.4 129/163] rtc: hym8563: fix invalid year calculation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Kochetkov commit d5861262210067fc01b2fb4f7af2fd85a3453f15 upstream. Year field must be in BCD format, according to hym8563 datasheet. Due to the bug year 2016

[PATCH 4.4 127/163] PM / OPP: Initialize u_volt_min/max to a valid value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit c88c395f4a6485f23f81e385c79945d68bcd5c5d upstream. We kept u_volt_min/max initialized to 0, when only the target voltage is present in DT, instead

[PATCH 4.4 133/163] rtc: max77686: Properly handle regmap_irq_get_virq() error code

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit fb166ba1d7f0a662f7332f4ff660a0d6f4d76915 upstream. The regmap_irq_get_virq() can return 0 or -EINVAL in error conditions but driver checked

[PATCH 4.4 129/163] rtc: hym8563: fix invalid year calculation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Kochetkov commit d5861262210067fc01b2fb4f7af2fd85a3453f15 upstream. Year field must be in BCD format, according to hym8563 datasheet. Due to the bug year 2016 became 2010. Fixes:

[PATCH 4.4 127/163] PM / OPP: Initialize u_volt_min/max to a valid value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit c88c395f4a6485f23f81e385c79945d68bcd5c5d upstream. We kept u_volt_min/max initialized to 0, when only the target voltage is present in DT, instead of the target/min/max

[PATCH 4.4 133/163] rtc: max77686: Properly handle regmap_irq_get_virq() error code

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit fb166ba1d7f0a662f7332f4ff660a0d6f4d76915 upstream. The regmap_irq_get_virq() can return 0 or -EINVAL in error conditions but driver checked only for value of 0.

[PATCH 4.4 094/163] cxl: Keep IRQ mappings on context teardown

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit d6776bba44d9752f6cdf640046070e71ee4bba7b upstream. Keep IRQ mappings on context teardown. This won't leak IRQs as if we allocate the mapping again,

[PATCH 4.4 093/163] [media] v4l2-dv-timings.h: fix polarity for 4k formats

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 3020ca711871fdaf0c15c8bab677a6bc302e28fe upstream. The VSync polarity was negative instead of positive for the 4k CEA formats. I probably

[PATCH 4.4 132/163] rtc: rx8025: remove rv8803 id

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni commit aaa3cee5deffa28415a6e1852c5afae0f5d210e2 upstream. The rv8803 has its own driver that should be used. Remove its id from the

[PATCH 4.4 094/163] cxl: Keep IRQ mappings on context teardown

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit d6776bba44d9752f6cdf640046070e71ee4bba7b upstream. Keep IRQ mappings on context teardown. This won't leak IRQs as if we allocate the mapping again, the generic code

[PATCH 4.4 093/163] [media] v4l2-dv-timings.h: fix polarity for 4k formats

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 3020ca711871fdaf0c15c8bab677a6bc302e28fe upstream. The VSync polarity was negative instead of positive for the 4k CEA formats. I probably copy-and-pasted these from the DMT

[PATCH 4.4 132/163] rtc: rx8025: remove rv8803 id

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni commit aaa3cee5deffa28415a6e1852c5afae0f5d210e2 upstream. The rv8803 has its own driver that should be used. Remove its id from the rx8025 driver. Fixes:

[PATCH 4.4 124/163] lib/mpi: Endianness fix

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michal Marek commit 3ee0cb5fb5eea2110db1b5cb7f67029b7be8a376 upstream. The limbs are integers in the host endianness, so we can't simply iterate over the individual bytes. The

[PATCH 4.4 095/163] IB/mlx5: Expose correct max_sge_rd limit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sagi Grimberg commit 986ef95ecdd3eb6fa29433e68faa94c7624083be upstream. mlx5 devices (Connect-IB, ConnectX-4, ConnectX-4-LX) has a limitation where rdma read work queue

[PATCH 4.4 124/163] lib/mpi: Endianness fix

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michal Marek commit 3ee0cb5fb5eea2110db1b5cb7f67029b7be8a376 upstream. The limbs are integers in the host endianness, so we can't simply iterate over the individual bytes. The current code

[PATCH 4.4 095/163] IB/mlx5: Expose correct max_sge_rd limit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sagi Grimberg commit 986ef95ecdd3eb6fa29433e68faa94c7624083be upstream. mlx5 devices (Connect-IB, ConnectX-4, ConnectX-4-LX) has a limitation where rdma read work queue entries cannot exceed

[PATCH 4.4 096/163] IB/security: Restrict use of the write() interface

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 upstream. The drivers/infiniband stack uses write() as a replacement for bi-directional

[PATCH 4.4 136/163] spi: rockchip: modify DMA max burst to 1

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Addy Ke commit 80abf8880cc6e1594c11b7c417f22dde60e25312 upstream. Generic dma controller on Rockchips' platform cannot support DMAFLUSHP instruction which make dma to

[PATCH 4.4 096/163] IB/security: Restrict use of the write() interface

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 upstream. The drivers/infiniband stack uses write() as a replacement for bi-directional ioctl(). This is not safe. There are

[PATCH 4.4 136/163] spi: rockchip: modify DMA max burst to 1

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Addy Ke commit 80abf8880cc6e1594c11b7c417f22dde60e25312 upstream. Generic dma controller on Rockchips' platform cannot support DMAFLUSHP instruction which make dma to flush the req of

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