[PATCH 4.4 087/146] drm: atmel-hlcdc: actually disable scaling when no scaling is required

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit 1b7e38b92b0bbd363369f5160f13f4d26140972d upstream. The driver is only enabling scaling, but never disabling it, thus, if you enable

[PATCH 4.4 087/146] drm: atmel-hlcdc: actually disable scaling when no scaling is required

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit 1b7e38b92b0bbd363369f5160f13f4d26140972d upstream. The driver is only enabling scaling, but never disabling it, thus, if you enable the scaling feature once it stays

[PATCH 4.4 093/146] drm/vmwgfx: Fix error paths when mapping framebuffer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 58541f7a6458e17ab417321b284f0090f530aa91 upstream. Rather than returning immediately, make sure to unlock the mutexes first. Signed-off-by: Sinclair Yeh

[PATCH 4.4 088/146] drm/ttm: Make ttm_bo_mem_compat available

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 94477bff390aa4612d2332c8abafaae0a13d6923 upstream. There are cases where it is desired to see if a proposed placement is compatible with a buffer object

[PATCH 4.4 080/146] drm/nouveau/disp/sor/gf119: select correct sor when poking training pattern

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 217215041b9285af2193a755b56a8f3ed408bfe2 upstream. Fixes a regression caused by a stupid thinko from "disp/sor/gf119: both links use the same training

[PATCH 4.4 092/146] drm/vmwgfx: Delay pinning fbdev framebuffer until after mode set

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit d5f1a291e32309324a8c481ed84b5c118d1360ea upstream. For the Screen Object display unit, we need to reserve a guest-invisible region equal to the size of the

[PATCH 4.4 072/146] drm/amdkfd: unbind only existing processes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Oded Gabbay commit 121b78e679ee3ffab780115e260b2775d0cc1f73 upstream. When unbinding a process from a device (initiated by amd_iommu_v2), the driver needs to make sure

[PATCH 4.4 089/146] drm/vmwgfx: Add an option to change assumed FB bpp

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 04319d89fbec72dfd60738003c3813b97c1d5f5a upstream. Offer an option for advanced users who want larger modes at 16bpp. This becomes necessary after the

[PATCH 4.4 093/146] drm/vmwgfx: Fix error paths when mapping framebuffer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 58541f7a6458e17ab417321b284f0090f530aa91 upstream. Rather than returning immediately, make sure to unlock the mutexes first. Signed-off-by: Sinclair Yeh Reviewed-by:

[PATCH 4.4 088/146] drm/ttm: Make ttm_bo_mem_compat available

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 94477bff390aa4612d2332c8abafaae0a13d6923 upstream. There are cases where it is desired to see if a proposed placement is compatible with a buffer object before calling

[PATCH 4.4 080/146] drm/nouveau/disp/sor/gf119: select correct sor when poking training pattern

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 217215041b9285af2193a755b56a8f3ed408bfe2 upstream. Fixes a regression caused by a stupid thinko from "disp/sor/gf119: both links use the same training register".

[PATCH 4.4 092/146] drm/vmwgfx: Delay pinning fbdev framebuffer until after mode set

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit d5f1a291e32309324a8c481ed84b5c118d1360ea upstream. For the Screen Object display unit, we need to reserve a guest-invisible region equal to the size of the framebuffer for

[PATCH 4.4 072/146] drm/amdkfd: unbind only existing processes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Oded Gabbay commit 121b78e679ee3ffab780115e260b2775d0cc1f73 upstream. When unbinding a process from a device (initiated by amd_iommu_v2), the driver needs to make sure that process still

[PATCH 4.4 089/146] drm/vmwgfx: Add an option to change assumed FB bpp

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 04319d89fbec72dfd60738003c3813b97c1d5f5a upstream. Offer an option for advanced users who want larger modes at 16bpp. This becomes necessary after the fix: "Work around

[PATCH 4.4 061/146] drm/mgag200: Black screen fix for G200e rev 4

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathieu Larouche commit d3922b69617b62bb2509936b68301f837229d9f0 upstream. - Fixed black screen for some resolutions of G200e rev4 - Fixed testm & testn which had

[PATCH 4.4 059/146] iommu/vt-d: Enable QI on all IOMMUs before setting root entry

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel commit a4c34ff1c029e90e7d5f8dd8d29b0a93b31c3cb2 upstream. This seems to be required on some X58 chipsets on systems with more than one IOMMU. QI does not work

[PATCH 4.4 061/146] drm/mgag200: Black screen fix for G200e rev 4

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathieu Larouche commit d3922b69617b62bb2509936b68301f837229d9f0 upstream. - Fixed black screen for some resolutions of G200e rev4 - Fixed testm & testn which had predetermined value.

[PATCH 4.4 059/146] iommu/vt-d: Enable QI on all IOMMUs before setting root entry

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel commit a4c34ff1c029e90e7d5f8dd8d29b0a93b31c3cb2 upstream. This seems to be required on some X58 chipsets on systems with more than one IOMMU. QI does not work until it is enabled

[PATCH 4.4 091/146] drm/vmwgfx: Check pin count before attempting to move a buffer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 4ed7e2242b637bc4af0416e4aa9f945db30fb44a upstream. In certain scenarios, e.g. when fbdev is enabled, we can get into a situation where a

[PATCH 4.4 095/146] perf/x86: Fix undefined shift on 32-bit kernels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 6d6f2833bfbf296101f9f085e10488aef2601ba5 upstream. Jim reported: UBSAN: Undefined behaviour in arch/x86/events/intel/core.c:3708:12

[PATCH 4.4 091/146] drm/vmwgfx: Check pin count before attempting to move a buffer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 4ed7e2242b637bc4af0416e4aa9f945db30fb44a upstream. In certain scenarios, e.g. when fbdev is enabled, we can get into a situation where a vmw_framebuffer_pin() is called on

[PATCH 4.4 095/146] perf/x86: Fix undefined shift on 32-bit kernels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 6d6f2833bfbf296101f9f085e10488aef2601ba5 upstream. Jim reported: UBSAN: Undefined behaviour in arch/x86/events/intel/core.c:3708:12 shift exponent 35 is

[PATCH 4.4 098/146] iio:st_pressure: fix sampling gains (bring inline with ABI)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gregor Boirie commit d43a41152f8e9e4c0d19850884d1fada076dee10 upstream. Temperature channels report scaled samples in Celsius although expected as milli degree

[PATCH 4.6 012/203] IB/rdmavt: Correct qp_priv_alloc() return value test

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit c755f4afa66ad3ed98870bd3254f37c47fb2c800 upstream. The current drivers return errors from this calldown wrapped in an ERR_PTR(). The rdmavt

[PATCH 4.4 098/146] iio:st_pressure: fix sampling gains (bring inline with ABI)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gregor Boirie commit d43a41152f8e9e4c0d19850884d1fada076dee10 upstream. Temperature channels report scaled samples in Celsius although expected as milli degree Celsius in

[PATCH 4.6 012/203] IB/rdmavt: Correct qp_priv_alloc() return value test

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit c755f4afa66ad3ed98870bd3254f37c47fb2c800 upstream. The current drivers return errors from this calldown wrapped in an ERR_PTR(). The rdmavt code incorrectly tests for

Re: [PATCH v3] PM / OPP: optimize dev_pm_opp_set_rate() performance a bit

On 25-07-16, 14:11, Jisheng Zhang wrote: > In dev_pm_opp_set_rate(), _find_opp_table() is called 4 times: once by > _get_opp_clk(), once by dev_pm_opp_set_rate() itself, and twice by > dev_pm_opp_find_freq_ceil(). If there are several opp_tables in the > system, three times of opp table finding is

Re: [PATCH v3] PM / OPP: optimize dev_pm_opp_set_rate() performance a bit

On 25-07-16, 14:11, Jisheng Zhang wrote: > In dev_pm_opp_set_rate(), _find_opp_table() is called 4 times: once by > _get_opp_clk(), once by dev_pm_opp_set_rate() itself, and twice by > dev_pm_opp_find_freq_ceil(). If there are several opp_tables in the > system, three times of opp table finding is

[PATCH 4.4 107/146] iio: accel: kxsd9: fix the usage of spi_w8r8()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 0c1f91b98552da49d9d8eed32b3132a58d2f4598 upstream. These two spi_w8r8() calls return a value with is used by the code following the error check.

[PATCH 4.4 055/146] HID: multitouch: enable palm rejection for Windows Precision Touchpad

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Allen Hung commit 6dd2e27a103d716921cc4a1a96a9adc0a8e3ab57 upstream. The usage Confidence is mandary to Windows Precision Touchpad devices. If it is examined in

[PATCH 4.4 107/146] iio: accel: kxsd9: fix the usage of spi_w8r8()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 0c1f91b98552da49d9d8eed32b3132a58d2f4598 upstream. These two spi_w8r8() calls return a value with is used by the code following the error check. The dubious use was caused

[PATCH 4.4 055/146] HID: multitouch: enable palm rejection for Windows Precision Touchpad

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Allen Hung commit 6dd2e27a103d716921cc4a1a96a9adc0a8e3ab57 upstream. The usage Confidence is mandary to Windows Precision Touchpad devices. If it is examined in input_mapping on a WIndows

[PATCH 4.6 002/203] mac80211: fix fast_tx header alignment

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 6fe04128f158c5ad27e7504bfdf1b12e63331bc9 upstream. The header field is defined as u8[] but also accessed as struct ieee80211_hdr. Enforce an alignment of 2

[PATCH 4.6 018/203] usb: dwc2: fix regression on big-endian PowerPC/ARM systems

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 23e3439296a55affce3ef0ab78f1c2e03aec8767 upstream. A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq MIPS system unfortunately broke

[PATCH 4.6 002/203] mac80211: fix fast_tx header alignment

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 6fe04128f158c5ad27e7504bfdf1b12e63331bc9 upstream. The header field is defined as u8[] but also accessed as struct ieee80211_hdr. Enforce an alignment of 2 to prevent

[PATCH 4.6 018/203] usb: dwc2: fix regression on big-endian PowerPC/ARM systems

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 23e3439296a55affce3ef0ab78f1c2e03aec8767 upstream. A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq MIPS system unfortunately broke big-endian operation

[PATCH 4.6 015/203] powerpc/pseries: Fix PCI config address for DDW

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Gavin Shan commit 8a934efe94347eee843aeea65bdec8077a79e259 upstream. In commit 8445a87f7092 "powerpc/iommu: Remove the dependency on EEH struct in DDW mechanism",

[PATCH 4.6 017/203] powerpc/tm: Always reclaim in start_thread() for exec() class syscalls

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Cyril Bur commit 8e96a87c5431c256feb65bcfc5aec92d9f7839b6 upstream. Userspace can quite legitimately perform an exec() syscall with a suspended transaction. exec() does not

[PATCH 4.6 015/203] powerpc/pseries: Fix PCI config address for DDW

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Gavin Shan commit 8a934efe94347eee843aeea65bdec8077a79e259 upstream. In commit 8445a87f7092 "powerpc/iommu: Remove the dependency on EEH struct in DDW mechanism", the PE address was replaced

[PATCH 4.6 017/203] powerpc/tm: Always reclaim in start_thread() for exec() class syscalls

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Cyril Bur commit 8e96a87c5431c256feb65bcfc5aec92d9f7839b6 upstream. Userspace can quite legitimately perform an exec() syscall with a suspended transaction. exec() does not return to the old

[PATCH 4.6 016/203] powerpc/pseries: Fix IBM_ARCH_VEC_NRCORES_OFFSET since POWER8NVL was added

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 2c2a63e301fd19ccae673e79de59b30a232ff7f9 upstream. The recent commit 7cc851039d64 ("powerpc/pseries: Add POWER8NVL support to

[PATCH 4.6 013/203] IB/mlx4: Properly initialize GRH TClass and FlowLabel in AHs

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe commit 8c5122e45a10a9262f872b53f151a592e870f905 upstream. When this code was reworked for IBoE support the order of assignments for the

[PATCH 4.6 016/203] powerpc/pseries: Fix IBM_ARCH_VEC_NRCORES_OFFSET since POWER8NVL was added

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 2c2a63e301fd19ccae673e79de59b30a232ff7f9 upstream. The recent commit 7cc851039d64 ("powerpc/pseries: Add POWER8NVL support to ibm,client-architecture-support call")

[PATCH 4.6 013/203] IB/mlx4: Properly initialize GRH TClass and FlowLabel in AHs

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe commit 8c5122e45a10a9262f872b53f151a592e870f905 upstream. When this code was reworked for IBoE support the order of assignments for the sl_tclass_flowlabel got flipped around

[PATCH 4.4 108/146] iio:ad7266: Fix broken regulator error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 6b7f4e25f3309f106a5c7ff42c8231494cf285d3 upstream. All regulator_get() variants return either a pointer to a regulator or an ERR_PTR() so testing for NULL

Re: [PATCH 2/2] i2c-dev: Don't block the adapter from unregistering

Hi Jean, On 25-07-16, 11:39, Jean Delvare wrote: > The problem is that the patch proposed by Viresh has nothing to do with > this. It's not adding notifications, just changing the time frame during > which user-space holds a reference to the i2c (bus) device. The goal as > I understand it is to

[PATCH 4.4 108/146] iio:ad7266: Fix broken regulator error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 6b7f4e25f3309f106a5c7ff42c8231494cf285d3 upstream. All regulator_get() variants return either a pointer to a regulator or an ERR_PTR() so testing for NULL makes no sense and

Re: [PATCH 2/2] i2c-dev: Don't block the adapter from unregistering

Hi Jean, On 25-07-16, 11:39, Jean Delvare wrote: > The problem is that the patch proposed by Viresh has nothing to do with > this. It's not adding notifications, just changing the time frame during > which user-space holds a reference to the i2c (bus) device. The goal as > I understand it is to

[PATCH 4.6 023/203] mnt: Account for MS_RDONLY in fs_fully_visible

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 695e9df010e40f407f4830dc11d53dce957710ba upstream. In rare cases it is possible for s_flags & MS_RDONLY to be set but MNT_READONLY to be clear.

[PATCH 4.6 019/203] USB: EHCI: declare hostpc register as zero-length array

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 7e8b3dfef16375dbfeb1f36a83eb9f27117c51fd upstream. The HOSTPC extension registers found in some EHCI implementations form a variable-length array,

[PATCH 4.6 025/203] of: fix autoloading due to broken modalias with no compatible

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit b3c0a4dab7e35a9b6d69c0415641d2280fdefb2b upstream. Because of an improper dereference, a stray 'C' character was output to the modalias when no

Re: linux-next: manual merge of the tip tree with the sh tree

Hi all, On Sun, 24 Jul 2016 15:13:42 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > arch/sh/include/asm/spinlock.h > > between commit: > > 2da83dfce7df ("sh: add J2 atomics using the cas.l instruction") > > from

[PATCH 4.6 024/203] mnt: If fs_fully_visible fails call put_filesystem.

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 97c1df3e54e811aed484a036a798b4b25d002ecf upstream. Add this trivial missing error handling. Fixes: 1b852bceb0d1 ("mnt: Refactor the logic for

[PATCH 4.6 019/203] USB: EHCI: declare hostpc register as zero-length array

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 7e8b3dfef16375dbfeb1f36a83eb9f27117c51fd upstream. The HOSTPC extension registers found in some EHCI implementations form a variable-length array, with one element for each

[PATCH 4.6 025/203] of: fix autoloading due to broken modalias with no compatible

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit b3c0a4dab7e35a9b6d69c0415641d2280fdefb2b upstream. Because of an improper dereference, a stray 'C' character was output to the modalias when no 'compatible' was specified.

Re: linux-next: manual merge of the tip tree with the sh tree

Hi all, On Sun, 24 Jul 2016 15:13:42 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > arch/sh/include/asm/spinlock.h > > between commit: > > 2da83dfce7df ("sh: add J2 atomics using the cas.l instruction") > > from the sh tree and commit:

[PATCH 4.6 024/203] mnt: If fs_fully_visible fails call put_filesystem.

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 97c1df3e54e811aed484a036a798b4b25d002ecf upstream. Add this trivial missing error handling. Fixes: 1b852bceb0d1 ("mnt: Refactor the logic for mounting sysfs and proc

[PATCH 4.6 023/203] mnt: Account for MS_RDONLY in fs_fully_visible

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit 695e9df010e40f407f4830dc11d53dce957710ba upstream. In rare cases it is possible for s_flags & MS_RDONLY to be set but MNT_READONLY to be clear. This starting

[PATCH 4.6 022/203] mnt: fs_fully_visible test the proper mount for MNT_LOCKED

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit d71ed6c930ac7d8f88f3cef6624a7e826392d61f upstream. MNT_LOCKED implies on a child mount implies the child is locked to the parent. So while

[PATCH 4.6 010/203] IB/core: Fix bit curruption in ib_device_cap_flags structure

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Max Gurtovoy commit 47355b3cd7d3c9c5226bff7c449b9d269fb17fa6 upstream. ib_device_cap_flags 64-bit expansion caused caps overlapping and made consumers read wrong device

[PATCH 4.6 020/203] USB: dont free bandwidth_mutex too early

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit ab2a4bf83902c170d29ba130a8abb5f9d90559e1 upstream. The USB core contains a bug that can show up when a USB-3 host controller is removed. If the

[PATCH 4.6 022/203] mnt: fs_fully_visible test the proper mount for MNT_LOCKED

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Eric W. Biederman commit d71ed6c930ac7d8f88f3cef6624a7e826392d61f upstream. MNT_LOCKED implies on a child mount implies the child is locked to the parent. So while looping through the

[PATCH 4.6 010/203] IB/core: Fix bit curruption in ib_device_cap_flags structure

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Max Gurtovoy commit 47355b3cd7d3c9c5226bff7c449b9d269fb17fa6 upstream. ib_device_cap_flags 64-bit expansion caused caps overlapping and made consumers read wrong device capabilities. For

[PATCH 4.6 020/203] USB: dont free bandwidth_mutex too early

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit ab2a4bf83902c170d29ba130a8abb5f9d90559e1 upstream. The USB core contains a bug that can show up when a USB-3 host controller is removed. If the primary (USB-2) hcd structure

[PATCH 4.6 028/203] locking/ww_mutex: Report recursive ww_mutex locking early

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 0422e83d84ae24b933e4b0d4c1e0f0b4ae8a0a3b upstream. Recursive locking for ww_mutexes was originally conceived as an exception. However, it is

[PATCH 4.6 028/203] locking/ww_mutex: Report recursive ww_mutex locking early

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit 0422e83d84ae24b933e4b0d4c1e0f0b4ae8a0a3b upstream. Recursive locking for ww_mutexes was originally conceived as an exception. However, it is heavily used by the DRM atomic

[PATCH 4.6 031/203] cpuidle: Do not access cpuidle_devices when !CONFIG_CPU_IDLE

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit 9bd616e3dbedfc103f158197c8ad93678849b1ed upstream. The cpuidle_devices per-CPU variable is only defined when CPU_IDLE is enabled. Commit

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/25/2016 01:13 PM, Catalin Marinas wrote: On Fri, Jul 22, 2016 at 11:51:32AM -0400, David Long wrote: On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote: On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long

[PATCH 4.6 026/203] of: irq: fix of_irq_get[_byname]() kernel-doc

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Sergei Shtylyov commit 3993546646baf1dab5f5c4f7d9bb58f2046fd1c1 upstream. The kernel-doc for the of_irq_get[_byname]() is clearly inadequate in describing

[PATCH 4.6 042/203] rtlwifi: Fix scheduling while atomic error from commit 49f86ec21c01

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit de26859dcf363d520cc44e59f6dcaf20ebe0aadf upstream. Commit 49f86ec21c01 ("rtlwifi: Change long delays to sleeps") was correct for most cases;

[PATCH 4.6 043/203] uvc: Forward compat ioctls to their handlers directly

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit a44323e2a8f342848bb77e8e04fcd85fcb91b3b4 upstream. The current code goes through a lot of indirection just to call a known handler. Simplify it: just

[PATCH 4.6 011/203] IB/cm: Fix a recently introduced locking bug

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 943f44d94aa26bfdcaafc40d3701e24eeb58edce upstream. ib_cm_notify() can be called from interrupt context. Hence do not reenable interrupts

[PATCH 4.6 004/203] mac80211_hwsim: Add missing check for HWSIM_ATTR_SIGNAL

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Martin Willi commit 62397da50bb20a6b812c949ef465d7e69fe54bb6 upstream. A wmediumd that does not send this attribute causes a NULL pointer dereference, as the attribute

[PATCH 4.6 031/203] cpuidle: Do not access cpuidle_devices when !CONFIG_CPU_IDLE

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit 9bd616e3dbedfc103f158197c8ad93678849b1ed upstream. The cpuidle_devices per-CPU variable is only defined when CPU_IDLE is enabled. Commit c8cc7d4de7a4 ("sched/idle:

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/25/2016 01:13 PM, Catalin Marinas wrote: On Fri, Jul 22, 2016 at 11:51:32AM -0400, David Long wrote: On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote: On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long

[PATCH 4.6 026/203] of: irq: fix of_irq_get[_byname]() kernel-doc

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Sergei Shtylyov commit 3993546646baf1dab5f5c4f7d9bb58f2046fd1c1 upstream. The kernel-doc for the of_irq_get[_byname]() is clearly inadequate in describing the return values --

[PATCH 4.6 042/203] rtlwifi: Fix scheduling while atomic error from commit 49f86ec21c01

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit de26859dcf363d520cc44e59f6dcaf20ebe0aadf upstream. Commit 49f86ec21c01 ("rtlwifi: Change long delays to sleeps") was correct for most cases; however, driver rtl8192ce calls

[PATCH 4.6 043/203] uvc: Forward compat ioctls to their handlers directly

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit a44323e2a8f342848bb77e8e04fcd85fcb91b3b4 upstream. The current code goes through a lot of indirection just to call a known handler. Simplify it: just call the handlers

[PATCH 4.6 011/203] IB/cm: Fix a recently introduced locking bug

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 943f44d94aa26bfdcaafc40d3701e24eeb58edce upstream. ib_cm_notify() can be called from interrupt context. Hence do not reenable interrupts unconditionally in

[PATCH 4.6 004/203] mac80211_hwsim: Add missing check for HWSIM_ATTR_SIGNAL

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Martin Willi commit 62397da50bb20a6b812c949ef465d7e69fe54bb6 upstream. A wmediumd that does not send this attribute causes a NULL pointer dereference, as the attribute is accessed even if it

[PATCH 4.6 029/203] locking/qspinlock: Fix spin_unlock_wait() some more

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 2c610022711675ee908b903d242f0b90e1db661f upstream. While this prior commit: 54cf809b9512 ("locking,qspinlock: Fix spin_is_locked() and

[PATCH 4.6 027/203] x86/msr: Use the proper trace point conditional for writes

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Dr. David Alan Gilbert commit 08dd8cd06ed95625b9e2fac43c78fcb45b7eaf94 upstream. The msr tracing for writes is incorrectly conditional on the read trace. Fixes:

[PATCH 4.6 003/203] mac80211: mesh: flush mesh paths unconditionally

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Bob Copeland commit fe7a7c57629e8dcbc0e297363a9b2366d67a6dc5 upstream. Currently, the mesh paths associated with a nexthop station are cleaned up in the following code

[PATCH 4.6 029/203] locking/qspinlock: Fix spin_unlock_wait() some more

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 2c610022711675ee908b903d242f0b90e1db661f upstream. While this prior commit: 54cf809b9512 ("locking,qspinlock: Fix spin_is_locked() and spin_unlock_wait()") ... fixes

[PATCH 4.6 027/203] x86/msr: Use the proper trace point conditional for writes

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Dr. David Alan Gilbert commit 08dd8cd06ed95625b9e2fac43c78fcb45b7eaf94 upstream. The msr tracing for writes is incorrectly conditional on the read trace. Fixes: 7f47d8cc039f "x86, tracing,

[PATCH 4.6 003/203] mac80211: mesh: flush mesh paths unconditionally

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Bob Copeland commit fe7a7c57629e8dcbc0e297363a9b2366d67a6dc5 upstream. Currently, the mesh paths associated with a nexthop station are cleaned up in the following code path:

[PATCH] staging: comedi: dt2811: add parentheses to fix logic on s->subdev_flags

From: Colin Ian King We need to add parentheses around ternary operations because currently the expression SDF_READABLE | (it->options[2] == 1) always evaluates to true, meaning s->subdev_flags is always assigned SDF_DIFF. Putting the parentheses around the ternarary

Re: linux-next: manual merge of the xen-tip tree with the block tree

On 07/25/2016 06:19 PM, Stephen Rothwell wrote: > Hi Stefano, > > On Mon, 25 Jul 2016 10:29:11 -0700 (PDT) Stefano Stabellini > wrote: >> The To and CC list for these emails is a bit outdated. I want to make >> sure they reach the right people. Could you please add: >> >>

[PATCH] staging: comedi: dt2811: add parentheses to fix logic on s->subdev_flags

From: Colin Ian King We need to add parentheses around ternary operations because currently the expression SDF_READABLE | (it->options[2] == 1) always evaluates to true, meaning s->subdev_flags is always assigned SDF_DIFF. Putting the parentheses around the ternarary operations results in the

Re: linux-next: manual merge of the xen-tip tree with the block tree

On 07/25/2016 06:19 PM, Stephen Rothwell wrote: > Hi Stefano, > > On Mon, 25 Jul 2016 10:29:11 -0700 (PDT) Stefano Stabellini > wrote: >> The To and CC list for these emails is a bit outdated. I want to make >> sure they reach the right people. Could you please add: >> >>

[PATCH 4.6 041/203] autofs braino fix for do_last()

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit e6ec03a25f12b312b7e0c037fe4a6471c4ee5665 upstream. It's an analogue of commit 7500c38a (fix the braino in "namei: massage lookup_slow() to be usable by

[PATCH 4.6 041/203] autofs braino fix for do_last()

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit e6ec03a25f12b312b7e0c037fe4a6471c4ee5665 upstream. It's an analogue of commit 7500c38a (fix the braino in "namei: massage lookup_slow() to be usable by

[PATCH 4.6 009/203] futex: Calculate the futex key based on a tail page for file-based futexes

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit 077fa7aed17de5022e44bf07dbaf732078b7b5b2 upstream. Mike Galbraith reported that the LTP test case futex_wake04 was broken by commit 65d8fc777f6d ("futex:

[PATCH 4.6 009/203] futex: Calculate the futex key based on a tail page for file-based futexes

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit 077fa7aed17de5022e44bf07dbaf732078b7b5b2 upstream. Mike Galbraith reported that the LTP test case futex_wake04 was broken by commit 65d8fc777f6d ("futex: Remove requirement

[PATCH 4.6 044/203] thermal: cpu_cooling: fix improper order during initialization

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Lukasz Luba commit f840ab18bdf2e415dac21d09fbbbd2873111bd48 upstream. The freq_table array is not populated before calling thermal_of_cooling_register. The code which

Re: [PATCH v3 3/9] media: adv7180: add support for NEWAVMODE

On 25/07/16 23:04, Steve Longerbeam wrote: On 07/25/2016 12:36 PM, Ian Arkver wrote: On 25/07/16 18:55, Steve Longerbeam wrote: On 07/25/2016 05:04 AM, Ian Arkver wrote: On 23/07/16 18:00, Steve Longerbeam wrote: +#define ADV7180_VSYNC_FIELD_CTL_1_NEWAVMODE 0x02 See below re this value.

Re: [PATCH -next] xtensa: Fix build error due to missing include file

On Mon, Jul 25, 2016 at 11:51 PM, Guenter Roeck wrote: > On Mon, Jul 25, 2016 at 11:07:00AM +0300, Max Filippov wrote: >> >>> On Sun, Jul 24, 2016 at 9:00 AM, Guenter Roeck >> >>> wrote: >> >> Heads up: xtensa images build after this patch, but

[PATCH 4.6 040/203] Revert "gpiolib: Split GPIO flags parsing and GPIO configuration"

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 85b03b3033fd4eba82665b3b9902c095a08cc52f upstream. This reverts commit 923b93e451db876d1479d3e4458fce14fec31d1c. Make sure consumers do not overwrite

[PATCH 4.6 008/203] EDAC, sb_edac: Fix rank lookup on Broadwell

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit c7103f650a11328f28b9fa1c95027db331b7774b upstream. Broadwell made a small change to the rank target register moving the target rank ID field up from bits

[PATCH 4.6 000/203] 4.6.5-stable review

This is the start of the stable review cycle for the 4.6.5 release. There are 203 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Jul 27 20:33:38 UTC 2016. Anything

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