[PATCH 3.2 003/147] staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 105967ad68d2eb1a041bc041f9cf96af2a653b65 upstream. gcc-7 points out an older regression: drivers/staging/iio/resolver/ad2s1210.c: In function 'ad2s1210_read_raw':

[PATCH 3.2 135/147] mct_u232: Fix use of uninitialized pointer in mct_u323_startup()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings My backport of commit 4e9a0b05257f "USB: mct_u232: add sanity checking in probe" incorrectly added a dev_err() call using port->dev before 'port' was initialised. Use the

[PATCH 3.2 145/147] staging: vt6655: fix overly large stack usage

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann We get a warning for the large stack usage in some configurations: drivers/staging/vt6655/device_main.c: In function 'device_ioctl':

[PATCH 3.2 145/147] staging: vt6655: fix overly large stack usage

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann We get a warning for the large stack usage in some configurations: drivers/staging/vt6655/device_main.c: In function 'device_ioctl': drivers/staging/vt6655/device_main.c:2974:1:

[PATCH v3 0/2] PM / QoS: Device resume latency framework fix

On Friday, November 3, 2017 12:42:57 PM CET Rafael J. Wysocki wrote: > On Thursday, November 2, 2017 12:00:27 AM CET Rafael J. Wysocki wrote: > > Hi, > > > > This series is a replacement for commit 0cc2b4e5a020 (PM / QoS: Fix device > > resume latency PM QoS) that had to be reverted due to

[PATCH 3.2 006/147] usb: storage: return on error to avoid a null pointer dereference

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 446230f52a5bef593554510302465eabab45a372 upstream. When us->extra is null the driver is not initialized, however, a later call to

[PATCH v3 0/2] PM / QoS: Device resume latency framework fix

On Friday, November 3, 2017 12:42:57 PM CET Rafael J. Wysocki wrote: > On Thursday, November 2, 2017 12:00:27 AM CET Rafael J. Wysocki wrote: > > Hi, > > > > This series is a replacement for commit 0cc2b4e5a020 (PM / QoS: Fix device > > resume latency PM QoS) that had to be reverted due to

[PATCH 3.2 006/147] usb: storage: return on error to avoid a null pointer dereference

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 446230f52a5bef593554510302465eabab45a372 upstream. When us->extra is null the driver is not initialized, however, a later call to osd200_scsi_to_ata is made that

[PATCH 3.2 013/147] IB/cxgb3: Fix error codes in iwch_alloc_mr()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 9064d6055c14f700aa13f7c72fd3e63d12bee643 upstream. We accidentally don't set the error code on some error paths. It means return ERR_PTR(0)

[PATCH 3.2 013/147] IB/cxgb3: Fix error codes in iwch_alloc_mr()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 9064d6055c14f700aa13f7c72fd3e63d12bee643 upstream. We accidentally don't set the error code on some error paths. It means return ERR_PTR(0) which is NULL and results in a

[PATCH 3.2 137/147] [media] mxl111sf: remove an unused variable

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 3fd7e4341e04f80e2605f56bbd8cb1e8b027901a upstream. We don't use this any more after 3be5bb71fb "[media] mxl111sf: fix error on stream stop in

[PATCH 3.2 139/147] [media] rc: Fix input deadlock and transmit error in redrat3 driver

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Andrew Vincer commit dbea1880368071dfa97d5e6aa4a368e7d0146a85 upstream. Fixed submit urb logic so hardware doesn't hang trying to transmit signal data Removed

[PATCH 3.2 126/147] staging: comedi: vmk80xx: fix compiler warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 13f7952f8f13fb1bbd18b85988e3a5bbbed00879 upstream. gcc complains about some potentially uninitalized variables here, yet it can not

[PATCH 3.2 137/147] [media] mxl111sf: remove an unused variable

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 3fd7e4341e04f80e2605f56bbd8cb1e8b027901a upstream. We don't use this any more after 3be5bb71fb "[media] mxl111sf: fix error on stream stop in

[PATCH 3.2 139/147] [media] rc: Fix input deadlock and transmit error in redrat3 driver

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Andrew Vincer commit dbea1880368071dfa97d5e6aa4a368e7d0146a85 upstream. Fixed submit urb logic so hardware doesn't hang trying to transmit signal data Removed unneeded enable/disable detector

[PATCH 3.2 126/147] staging: comedi: vmk80xx: fix compiler warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 13f7952f8f13fb1bbd18b85988e3a5bbbed00879 upstream. gcc complains about some potentially uninitalized variables here, yet it can not happen, due to an enumerated type

Re: [v4,1/6] dt-bindings: pmbus: Add Maxim MAX31785 documentation

On Fri, Nov 03, 2017 at 03:53:01PM +1100, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery > Acked-by: Rob Herring Applied to hwmon-next. Thanks, Guenter > --- > .../devicetree/bindings/hwmon/max31785.txt | 22 > ++ > 1 file

[PATCH 3.2 146/147] Staging: wlan-ng: fix sparse warning in prism2fw.c

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: A Raghavendra Rao commit 41cb65c4854e14f12b1cbb8215e509d8ad4d0c88 upstream. Fix the following sparse warning : In file included from

Re: [v4,1/6] dt-bindings: pmbus: Add Maxim MAX31785 documentation

On Fri, Nov 03, 2017 at 03:53:01PM +1100, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery > Acked-by: Rob Herring Applied to hwmon-next. Thanks, Guenter > --- > .../devicetree/bindings/hwmon/max31785.txt | 22 > ++ > 1 file changed, 22 insertions(+) >

[PATCH 3.2 146/147] Staging: wlan-ng: fix sparse warning in prism2fw.c

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: A Raghavendra Rao commit 41cb65c4854e14f12b1cbb8215e509d8ad4d0c88 upstream. Fix the following sparse warning : In file included from drivers/staging/wlan-ng/prism2usb.c:5:0:

[PATCH 3.2 005/147] USB: cdc-acm: add device-id for quirky printer

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit fe855789d605590e57f9cd968d85ecce46f5c3fd upstream. Add device-id entry for DATECS FP-2000 fiscal printer needing the NO_UNION_NORMAL quirk. Reported-by:

[PATCH 3.2 005/147] USB: cdc-acm: add device-id for quirky printer

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit fe855789d605590e57f9cd968d85ecce46f5c3fd upstream. Add device-id entry for DATECS FP-2000 fiscal printer needing the NO_UNION_NORMAL quirk. Reported-by: Anton Avramov

[PATCH 3.2 134/147] staging: reduce stack usage in prism2fw.c

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap commit c90e3e80b9751335cc98934ae32188fa7de6bccd upstream. Fix frame size (stack usage) warning by allocating and freeing pointers to the data.

[PATCH 3.2 134/147] staging: reduce stack usage in prism2fw.c

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap commit c90e3e80b9751335cc98934ae32188fa7de6bccd upstream. Fix frame size (stack usage) warning by allocating and freeing pointers to the data.

[PATCH 3.2 012/147] cxgb4: Fix error codes in c4iw_create_cq()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 6ebedacbb44602d4dec3348dee5ec31dd9b09521 upstream. If one of these kmalloc() calls fails then we return ERR_PTR(0) which is NULL. It results in

[PATCH 3.2 133/147] staging/slicoss: Fix operation may be undefined warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Huewe commit 6d1b80fd886937ad4d6169ffa78cb0075eebce53 upstream. gcc complains about an undefined operation: slicoss.c:1417:19: warning: operation on 'rspq->pageindex'

[PATCH 3.2 012/147] cxgb4: Fix error codes in c4iw_create_cq()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 6ebedacbb44602d4dec3348dee5ec31dd9b09521 upstream. If one of these kmalloc() calls fails then we return ERR_PTR(0) which is NULL. It results in a NULL dereference in the

[PATCH 3.2 133/147] staging/slicoss: Fix operation may be undefined warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Huewe commit 6d1b80fd886937ad4d6169ffa78cb0075eebce53 upstream. gcc complains about an undefined operation: slicoss.c:1417:19: warning: operation on 'rspq->pageindex' may be undefined

[PATCH 3.2 131/147] staging:iio:gyro:adis16080: remove sparse warnings

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Leed Aguilar commit 4d9505af7743828464d066795c6e1311c7884db4 upstream. Removed the following sparse warning: In function 'adis16080_read_raw': warning: 'ut' may be used

[PATCH 3.2 131/147] staging:iio:gyro:adis16080: remove sparse warnings

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Leed Aguilar commit 4d9505af7743828464d066795c6e1311c7884db4 upstream. Removed the following sparse warning: In function 'adis16080_read_raw': warning: 'ut' may be used uninitialized in this

[PATCH 3.2 128/147] Staging: iio/accel: Changed return type of lis3l02dq_read_event_config() to int

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Andreas Ruprecht commit 28998e005bb669b60de0e432d6f142267f5c1403 upstream. The lis3l02dq_read_event_config() function returned an ssize_t up to now, which lead to a

[PATCH 3.2 132/147] sfc: Merge efx_mcdi_mac_check_fault() and efx_mcdi_get_mac_faults()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 1daf417029ddc10b7854430c1e1118df791d0eaf upstream. The latter is only called by the former, which is a very short wrapper. Further, gcc 4.5 may

[PATCH 3.2 128/147] Staging: iio/accel: Changed return type of lis3l02dq_read_event_config() to int

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Andreas Ruprecht commit 28998e005bb669b60de0e432d6f142267f5c1403 upstream. The lis3l02dq_read_event_config() function returned an ssize_t up to now, which lead to a compiler warning in line

[PATCH 3.2 132/147] sfc: Merge efx_mcdi_mac_check_fault() and efx_mcdi_get_mac_faults()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 1daf417029ddc10b7854430c1e1118df791d0eaf upstream. The latter is only called by the former, which is a very short wrapper. Further, gcc 4.5 may currently wrongly warn

[PATCH 3.2 125/147] aic94xx: Skip reading user settings if flash is not found

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 36dd5acd196574d41de3e81d8264df475bbb7123 upstream. If no user settings are found it's pointless trying to read them from flash. So skip that step. This

[PATCH 3.2 141/147] scsi: advansys: remove #warning message

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann The advansys driver was converted to the proper DMA API in linux-4.2, but the 3.18-stable kernel still warns about this: drivers/scsi/advansys.c:71:2: warning:

[PATCH 3.2 125/147] aic94xx: Skip reading user settings if flash is not found

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 36dd5acd196574d41de3e81d8264df475bbb7123 upstream. If no user settings are found it's pointless trying to read them from flash. So skip that step. This also fixes a

[PATCH 3.2 141/147] scsi: advansys: remove #warning message

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann The advansys driver was converted to the proper DMA API in linux-4.2, but the 3.18-stable kernel still warns about this: drivers/scsi/advansys.c:71:2: warning: #warning this

[PATCH 3.2 116/147] [media] xc4000: Fix a few warnings

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 0d0d76e5bcd70439b0e736a99539d7eef4f87baf upstream. drivers/media/tuners/xc4000.c: In function ‘check_firmware’:

[PATCH 3.2 116/147] [media] xc4000: Fix a few warnings

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 0d0d76e5bcd70439b0e736a99539d7eef4f87baf upstream. drivers/media/tuners/xc4000.c: In function ‘check_firmware’: drivers/media/tuners/xc4000.c:1048:45: warning:

[PATCH 3.2 123/147] platform/x86: samsung-laptop: Initialize loca variable

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 0d2c95354a3b63256e92d9fb865c08902d2c9b0b upstream. The variable is used uninitialized which might come into unexpected behaviour on

[PATCH 3.2 123/147] platform/x86: samsung-laptop: Initialize loca variable

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 0d2c95354a3b63256e92d9fb865c08902d2c9b0b upstream. The variable is used uninitialized which might come into unexpected behaviour on some Samsung laptops. Initialize it

Re: [PATCH v9 0/5] Add support for ThunderX2 pmu events using json files

Hi Arnaldo, On Tue, Oct 17, 2017 at 12:02:17AM +0530, Ganapatrao Kulkarni wrote: > Extending json/jevent framework for parsing arm64 event files. > Adding jevents for ThunderX2 implementation defined PMU events. > > v9: >- Rebased to [3] and resolved conficts in PATCH 1/5 and reworked PATCH

[PATCH 3.2 008/147] usb: renesas_usbhs: fix usbhsc_resume() for !USBHSF_RUNTIME_PWCTRL

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 59a0879a0e17b2e43ecdc5e3299da85b8410d7ce upstream. This patch fixes an issue that some registers may be not initialized after resume

[PATCH 3.2 008/147] usb: renesas_usbhs: fix usbhsc_resume() for !USBHSF_RUNTIME_PWCTRL

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 59a0879a0e17b2e43ecdc5e3299da85b8410d7ce upstream. This patch fixes an issue that some registers may be not initialized after resume if the USBHSF_RUNTIME_PWCTRL is

Re: [PATCH v9 0/5] Add support for ThunderX2 pmu events using json files

Hi Arnaldo, On Tue, Oct 17, 2017 at 12:02:17AM +0530, Ganapatrao Kulkarni wrote: > Extending json/jevent framework for parsing arm64 event files. > Adding jevents for ThunderX2 implementation defined PMU events. > > v9: >- Rebased to [3] and resolved conficts in PATCH 1/5 and reworked PATCH

Re: [RFC PATCH v10 for 4.15 01/14] Restartable sequences system call

On Mon, Nov 06, 2017 at 03:56:31PM -0500, Mathieu Desnoyers wrote: [...] > + > +/* > + * struct rseq is aligned on 4 * 8 bytes to ensure it is always > + * contained within a single cache-line. > + * > + * A single struct rseq per thread is allowed. > + */ > +struct rseq { > + /* > + *

Re: [RFC PATCH v10 for 4.15 01/14] Restartable sequences system call

On Mon, Nov 06, 2017 at 03:56:31PM -0500, Mathieu Desnoyers wrote: [...] > + > +/* > + * struct rseq is aligned on 4 * 8 bytes to ensure it is always > + * contained within a single cache-line. > + * > + * A single struct rseq per thread is allowed. > + */ > +struct rseq { > + /* > + *

Re: [PATCH v9 00/51] powerpc, mm: Memory Protection Keys

On Mon, Nov 06, 2017 at 10:28:41PM +0100, Florian Weimer wrote: > * Ram Pai: > > > Testing: > > --- > > This patch series has passed all the protection key > > tests available in the selftest directory.The > > tests are updated to work on both x86 and powerpc. > > The selftests have passed on

[PATCH 3.2 124/147] drivers/rtc/rtc-m41t80.c: remove disabled alarm functionality

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Bolle commit 48e9766726ebb8f5d98823fe6b32dff570bc04d8 upstream. Commit c3b79770e51a ("rtc: m41t80: Workaround broken alarm functionality") disabled m41t80's alarm

[PATCH 3.2 124/147] drivers/rtc/rtc-m41t80.c: remove disabled alarm functionality

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Bolle commit 48e9766726ebb8f5d98823fe6b32dff570bc04d8 upstream. Commit c3b79770e51a ("rtc: m41t80: Workaround broken alarm functionality") disabled m41t80's alarm functions. But since

Re: [PATCH v9 00/51] powerpc, mm: Memory Protection Keys

On Mon, Nov 06, 2017 at 10:28:41PM +0100, Florian Weimer wrote: > * Ram Pai: > > > Testing: > > --- > > This patch series has passed all the protection key > > tests available in the selftest directory.The > > tests are updated to work on both x86 and powerpc. > > The selftests have passed on

[PATCH 3.2 120/147] mtd: map: Fix compilation warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 3e9ce49e0ef95e22790a74720f0068696b2477c9 upstream. This patch is an attempt to fix following compilation warning. In file included from

[PATCH 3.2 120/147] mtd: map: Fix compilation warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 3e9ce49e0ef95e22790a74720f0068696b2477c9 upstream. This patch is an attempt to fix following compilation warning. In file included from

[PATCH 3.2 119/147] [media] tda18212: silence compiler warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Antti Palosaari commit e666a44fa313cb9329c0381ad02fc6ee1e21cb31 upstream. Trivial fix. Signed-off-by: Antti Palosaari Signed-off-by: Mauro Carvalho Chehab

[PATCH 3.2 119/147] [media] tda18212: silence compiler warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Antti Palosaari commit e666a44fa313cb9329c0381ad02fc6ee1e21cb31 upstream. Trivial fix. Signed-off-by: Antti Palosaari Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Ben Hutchings ---

[PATCH 3.2 130/147] [SCSI] mpt2sas: fix for unused variable 'event_data' warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: "Reddy, Sreekanth" commit c3a634bf78242177fba9c85deb709e7b63ed0ef1 upstream. If CONFIG_SCSI_MPT2SAS_LOGGING is undefined, then these warnings are emitted

[PATCH 3.2 130/147] [SCSI] mpt2sas: fix for unused variable 'event_data' warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: "Reddy, Sreekanth" commit c3a634bf78242177fba9c85deb709e7b63ed0ef1 upstream. If CONFIG_SCSI_MPT2SAS_LOGGING is undefined, then these warnings are emitted drivers/scsi/mpt2sas/mpt2sas_scsih.c:

Re: [RFC PATCH for 4.15 10/14] cpu_opv: Wire up powerpc system call

On Tue, 7 Nov 2017 00:47:17 + (UTC) Mathieu Desnoyers wrote: > - On Nov 6, 2017, at 7:37 PM, Nicholas Piggin npig...@gmail.com wrote: > > > On Mon, 6 Nov 2017 15:56:40 -0500 > > Mathieu Desnoyers wrote: > > > >> diff

Re: [RFC PATCH for 4.15 10/14] cpu_opv: Wire up powerpc system call

On Tue, 7 Nov 2017 00:47:17 + (UTC) Mathieu Desnoyers wrote: > - On Nov 6, 2017, at 7:37 PM, Nicholas Piggin npig...@gmail.com wrote: > > > On Mon, 6 Nov 2017 15:56:40 -0500 > > Mathieu Desnoyers wrote: > > > >> diff --git a/arch/powerpc/include/uapi/asm/unistd.h > >>

[PATCH 3.2 107/147] ALSA: snd-usb-caiaq: initialize card pointer

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Daniel Mack commit da185443c12f5ef7416af50293833a5654854186 upstream. Fixes the following warning: CC [M] sound/usb/caiaq/device.o sound/usb/caiaq/device.c: In function

[PATCH 3.2 106/147] edac: i7300_edac: Fix 'may be used uninitialized' warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings gcc 4.7 warns that nr_pages may be used uninitialized in i7300_init_csrows(). In fact, the case where it's not initialised is an error that will result in

[PATCH 3.2 113/147] IB/mlx4: Fix compiler warning about uninitialized 'vlan' variable

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Bolle commit 57d88cffc83a2120266bbe9e72cbba5bd5f33675 upstream. Building qp.o triggers this gcc warning: drivers/infiniband/hw/mlx4/qp.c: In function

[PATCH 3.2 107/147] ALSA: snd-usb-caiaq: initialize card pointer

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Daniel Mack commit da185443c12f5ef7416af50293833a5654854186 upstream. Fixes the following warning: CC [M] sound/usb/caiaq/device.o sound/usb/caiaq/device.c: In function ‘snd_probe’:

[PATCH 3.2 106/147] edac: i7300_edac: Fix 'may be used uninitialized' warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings gcc 4.7 warns that nr_pages may be used uninitialized in i7300_init_csrows(). In fact, the case where it's not initialised is an error that will result in returning early without

[PATCH 3.2 113/147] IB/mlx4: Fix compiler warning about uninitialized 'vlan' variable

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Bolle commit 57d88cffc83a2120266bbe9e72cbba5bd5f33675 upstream. Building qp.o triggers this gcc warning: drivers/infiniband/hw/mlx4/qp.c: In function ‘mlx4_ib_post_send’:

[PATCH 3.2 121/147] vmw_balloon: fix for a -Wuninitialized warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Danny Kukawka commit 3e5ba466d515eb3fb1e0e975a3d8e499126ae2b5 upstream. Fix for a -Wuninitialized compiler warning. Changed return value of vmballoon_send_lock_page()

[PATCH 3.2 121/147] vmw_balloon: fix for a -Wuninitialized warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Danny Kukawka commit 3e5ba466d515eb3fb1e0e975a3d8e499126ae2b5 upstream. Fix for a -Wuninitialized compiler warning. Changed return value of vmballoon_send_lock_page() from bool to int to be

[PATCH 3.16 213/294] iio: adc: fix building on 64-bit

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann On the 3.16 kernel, we get a harmless warning: drivers/iio/adc/exynos_adc.c: In function 'exynos_adc_get_version': drivers/iio/adc/exynos_adc.c:112:9: error: cast

[PATCH 3.16 213/294] iio: adc: fix building on 64-bit

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann On the 3.16 kernel, we get a harmless warning: drivers/iio/adc/exynos_adc.c: In function 'exynos_adc_get_version': drivers/iio/adc/exynos_adc.c:112:9: error: cast from pointer

[PATCH 3.2 118/147] [media] tda18218: silence compiler warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Antti Palosaari commit e0e52d4e9f5bce7ea887027c127473eb654a5a04 upstream. Trivial fix. Signed-off-by: Antti Palosaari Signed-off-by: Mauro Carvalho Chehab

[PATCH 3.16 216/294] mfd: arizona: Rid data size incompatibility warn when building for 64bit

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Lee Jones commit 942786e6e647cef94cf96dcd836d343be55fc452 upstream. Extinguishes: ../drivers/mfd/arizona-core.c: In function ‘arizona_of_get_type’:

[PATCH 3.2 118/147] [media] tda18218: silence compiler warning

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Antti Palosaari commit e0e52d4e9f5bce7ea887027c127473eb654a5a04 upstream. Trivial fix. Signed-off-by: Antti Palosaari Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Ben Hutchings ---

[PATCH 3.16 216/294] mfd: arizona: Rid data size incompatibility warn when building for 64bit

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Lee Jones commit 942786e6e647cef94cf96dcd836d343be55fc452 upstream. Extinguishes: ../drivers/mfd/arizona-core.c: In function ‘arizona_of_get_type’: ../drivers/mfd/arizona-core.c:505:10:

[PATCH 3.16 001/294] fuse: initialize the flock flag in fuse_file on allocation

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mateusz Jurczyk commit 68227c03cba84a24faf8a7277d2b1a03c8959c2c upstream. Before the patch, the flock flag could remain uninitialized for the lifespan of the fuse_file

[PATCH 3.16 001/294] fuse: initialize the flock flag in fuse_file on allocation

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mateusz Jurczyk commit 68227c03cba84a24faf8a7277d2b1a03c8959c2c upstream. Before the patch, the flock flag could remain uninitialized for the lifespan of the fuse_file allocation. Unless set

Re: [PATCH] selftests: futex: fix compilation error

On 2017年11月07日 07:48, Shuah Khan wrote: On 11/06/2017 04:45 PM, Shuah Khan wrote: On 11/05/2017 09:03 PM, Lei Yang wrote: I run into below error when building futext /bin/sh: -c: line 5: syntax error: unexpected end of file the closing ";" and "\" are necessary. My OS is "Ubuntu 14.04.5

[PATCH 3.16 008/294] staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 105967ad68d2eb1a041bc041f9cf96af2a653b65 upstream. gcc-7 points out an older regression: drivers/staging/iio/resolver/ad2s1210.c: In function

Re: [PATCH] selftests: futex: fix compilation error

On 2017年11月07日 07:48, Shuah Khan wrote: On 11/06/2017 04:45 PM, Shuah Khan wrote: On 11/05/2017 09:03 PM, Lei Yang wrote: I run into below error when building futext /bin/sh: -c: line 5: syntax error: unexpected end of file the closing ";" and "\" are necessary. My OS is "Ubuntu 14.04.5

[PATCH 3.16 008/294] staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 105967ad68d2eb1a041bc041f9cf96af2a653b65 upstream. gcc-7 points out an older regression: drivers/staging/iio/resolver/ad2s1210.c: In function 'ad2s1210_read_raw':

[PATCH 3.16 215/294] power/reset: xgene-reset: Fix prototype of xgene_restart()

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit d3ed534cca703b2aaeee9277a5b8063ae6eab1d1 upstream. The xgene-reset driver uses xgene_restart() as arm_pm_restart() but that function should take an enum

[PATCH 3.16 212/294] gfs2: remove IS_ERR_VALUE abuse

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann Picked from commit 287980e49ffc0f6d911601e7e352a812ed27768e ("remove lots of IS_ERR_VALUE abuses") upstream. The original fix that was backported to 3.18 already

[PATCH 3.16 215/294] power/reset: xgene-reset: Fix prototype of xgene_restart()

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit d3ed534cca703b2aaeee9277a5b8063ae6eab1d1 upstream. The xgene-reset driver uses xgene_restart() as arm_pm_restart() but that function should take an enum reset_type as the

[PATCH 3.16 212/294] gfs2: remove IS_ERR_VALUE abuse

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann Picked from commit 287980e49ffc0f6d911601e7e352a812ed27768e ("remove lots of IS_ERR_VALUE abuses") upstream. The original fix that was backported to 3.18 already addressed the

[PATCH 3.16 000/294] 3.16.50-rc1 review

This is the start of the stable review cycle for the 3.16.50 release. There are 294 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Fri Nov 08 18:00:00 UTC 2017. Anything

[PATCH 3.16 217/294] Input: joystick - use get_cycles on ARMv8

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit a6b48699ae50ccce700506ced863ba1f5ce2af11 upstream. As with ARM the ARMv8 architecture provides a cycle counter which can be used to provide a high

[PATCH 3.16 000/294] 3.16.50-rc1 review

This is the start of the stable review cycle for the 3.16.50 release. There are 294 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Fri Nov 08 18:00:00 UTC 2017. Anything

[PATCH 3.16 217/294] Input: joystick - use get_cycles on ARMv8

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit a6b48699ae50ccce700506ced863ba1f5ce2af11 upstream. As with ARM the ARMv8 architecture provides a cycle counter which can be used to provide a high resolution time for the

[PATCH 3.16 221/294] ASoC: imx-audmux: Use uintptr_t for port numbers

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit e5f89768e9bc1f441d18e2299518a2907e5017c9 upstream. Since we pass the port number through file private data for debugfs we cast it to and from a pointer

[PATCH 3.16 221/294] ASoC: imx-audmux: Use uintptr_t for port numbers

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit e5f89768e9bc1f441d18e2299518a2907e5017c9 upstream. Since we pass the port number through file private data for debugfs we cast it to and from a pointer so use uintptr_t in

Re: [PATCH] selftests: futex: fix compilation error

On 2017年11月07日 07:45, Shuah Khan wrote: On 11/05/2017 09:03 PM, Lei Yang wrote: I run into below error when building futext /bin/sh: -c: line 5: syntax error: unexpected end of file the closing ";" and "\" are necessary. My OS is "Ubuntu 14.04.5 LTS" Signed-off-by: Lei Yang

Re: [PATCH] selftests: futex: fix compilation error

On 2017年11月07日 07:45, Shuah Khan wrote: On 11/05/2017 09:03 PM, Lei Yang wrote: I run into below error when building futext /bin/sh: -c: line 5: syntax error: unexpected end of file the closing ";" and "\" are necessary. My OS is "Ubuntu 14.04.5 LTS" Signed-off-by: Lei Yang ---

[PATCH 3.16 208/294] Input: gscps2 - fix MODULE_DEVICE_TABLE invocation

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 6c8afa88adce613c23f27e719f805cc2a6441b07 upstream. The patch "module: fix types of device tables aliases" newly requires that invocations of

[PATCH 3.16 208/294] Input: gscps2 - fix MODULE_DEVICE_TABLE invocation

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 6c8afa88adce613c23f27e719f805cc2a6441b07 upstream. The patch "module: fix types of device tables aliases" newly requires that invocations of

[PATCH 3.16 203/294] Disable "frame-address" warning

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann From: Linus Torvalds commit 124a3d88fa20e1869fc229d7d8c740cc81944264 upstream. Newer versions of gcc warn about the use of

[PATCH 3.16 203/294] Disable "frame-address" warning

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann From: Linus Torvalds commit 124a3d88fa20e1869fc229d7d8c740cc81944264 upstream. Newer versions of gcc warn about the use of __builtin_return_address() with a non-zero argument

[PATCH 3.16 219/294] gpio: drop retval check enforcing from gpiochip_remove()

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 14c8a620ba436511b1347c592633befa49535176 upstream. As we start to decomission the return value from gpiochip_remove() the compilers emit

[PATCH 3.16 219/294] gpio: drop retval check enforcing from gpiochip_remove()

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 14c8a620ba436511b1347c592633befa49535176 upstream. As we start to decomission the return value from gpiochip_remove() the compilers emit warnings due to the function

[PATCH 3.16 228/294] spi/pl022: Explicitly truncate large bitmask

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit d555ea05f9d8ebf567eaa6b4e4cb5776aacf2940 upstream. When building on 64 bit architectures the use of bitwise negation generates constants larger than 32

[PATCH 3.16 228/294] spi/pl022: Explicitly truncate large bitmask

3.16.50-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit d555ea05f9d8ebf567eaa6b4e4cb5776aacf2940 upstream. When building on 64 bit architectures the use of bitwise negation generates constants larger than 32 bits which won't fit

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