[RESEND PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name

It's not correct to encode the subsystem in the I2C device name, so drop the -mfd suffix. To maintain bisect-ability, change driver and platform code / DTS users in the same patch. Suggested-by: Lee Jones Signed-off-by: Javier Martinez Canillas

[RESEND PATCH v6 7/8] mfd: tps6105x: Add OF device ID table

The driver doesn't have a struct of_device_id table but supported devices are registered via Device Trees. This is working on the assumption that a I2C device registered via OF will always match a legacy I2C device ID and that the MODALIAS reported will always be of the form i2c:. But this could

[RESEND PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name

It's not correct to encode the subsystem in the I2C device name, so drop the -mfd suffix. To maintain bisect-ability, change driver and platform code / DTS users in the same patch. Suggested-by: Lee Jones Signed-off-by: Javier Martinez Canillas Acked-by: Rob Herring Acked-by: Aaro Koskinen

[RESEND PATCH v6 7/8] mfd: tps6105x: Add OF device ID table

The driver doesn't have a struct of_device_id table but supported devices are registered via Device Trees. This is working on the assumption that a I2C device registered via OF will always match a legacy I2C device ID and that the MODALIAS reported will always be of the form i2c:. But this could

[RESEND PATCH v6 1/8] dt-bindings: mfd: Add retu/tahvo ASIC chips bindings

There are Device Tree source files defining a device node for the retu/tahvo I2C chip, but there isn't a DT binding document for it. Signed-off-by: Javier Martinez Canillas Acked-by: Rob Herring Acked-by: Aaro Koskinen Acked-by: Tony

[RESEND PATCH v6 6/8] dt-bindings: mfd: Add TI tps6105x chip bindings

There are Device Tree source files defining a device node for the tps61050/61052 I2C chip but there isn't a binding document for it. Signed-off-by: Javier Martinez Canillas Acked-by: Rob Herring Acked-by: Tony Lindgren --- Changes in

[RESEND PATCH v6 1/8] dt-bindings: mfd: Add retu/tahvo ASIC chips bindings

There are Device Tree source files defining a device node for the retu/tahvo I2C chip, but there isn't a DT binding document for it. Signed-off-by: Javier Martinez Canillas Acked-by: Rob Herring Acked-by: Aaro Koskinen Acked-by: Tony Lindgren Acked-by: Lee Jones --- Changes in v6: -

[RESEND PATCH v6 6/8] dt-bindings: mfd: Add TI tps6105x chip bindings

There are Device Tree source files defining a device node for the tps61050/61052 I2C chip but there isn't a binding document for it. Signed-off-by: Javier Martinez Canillas Acked-by: Rob Herring Acked-by: Tony Lindgren --- Changes in v6: None Changes in v5: - Add Rob Herring's Acked-by tag.

[RFC v2 1/2] swait: add idle variants which don't contribute to load average

There are cases where folks are using an interruptible swait when using kthreads. This is rather confusing given you'd expect interruptible waits to be -- interruptible, but kthreads are not interruptible ! The reason for such practice though is to avoid having these kthreads contribute to the

[RFC v2 1/2] swait: add idle variants which don't contribute to load average

There are cases where folks are using an interruptible swait when using kthreads. This is rather confusing given you'd expect interruptible waits to be -- interruptible, but kthreads are not interruptible ! The reason for such practice though is to avoid having these kthreads contribute to the

Re: [PATCH 4/4] i2c: rcar: check for DMA-capable buffers

On Thu, Jun 15, 2017 at 12:30 PM, Wolfram Sang wrote: > Handling this is special for this driver. Because the hardware needs to > initialize the next message in interrupt context, we cannot use the > i2c_check_msg_for_dma() directly. This helper only works

Re: [PATCH 4/4] i2c: rcar: check for DMA-capable buffers

On Thu, Jun 15, 2017 at 12:30 PM, Wolfram Sang wrote: > Handling this is special for this driver. Because the hardware needs to > initialize the next message in interrupt context, we cannot use the > i2c_check_msg_for_dma() directly. This helper only works reliably in > process context. So, we

[RFC v2 2/2] rcu: use idle versions of swait to make idle-hack clear

These RCU waits were set to use interruptible waits to avoid the kthreads contributing to system load average, even though they are not interruptible as they are spawned from a kthread. Use the new TASK_IDLE swaits which makes it clear our goal, and removes confusion about these paths possibly

[RFC v2 0/2] swait: add idle to make idle-hacks on kthreads explicit

While reviewing RCU's interruptible swaits I noticed signals were actually not expected. Paul explained that the reason signals are not expected is we use kthreads, which don't get signals, furthermore the code avoided the uninterruptible swaits as otherwise it would contribute to the system load

[RFC v2 2/2] rcu: use idle versions of swait to make idle-hack clear

These RCU waits were set to use interruptible waits to avoid the kthreads contributing to system load average, even though they are not interruptible as they are spawned from a kthread. Use the new TASK_IDLE swaits which makes it clear our goal, and removes confusion about these paths possibly

[RFC v2 0/2] swait: add idle to make idle-hacks on kthreads explicit

While reviewing RCU's interruptible swaits I noticed signals were actually not expected. Paul explained that the reason signals are not expected is we use kthreads, which don't get signals, furthermore the code avoided the uninterruptible swaits as otherwise it would contribute to the system load

Re: [PATCH] Doc: net: dsa: b53: update location of referenced dsa.txt

Please re-post this with the netdev mailing list CC:'d, thank you.

Re: [PATCH] Doc: net: dsa: b53: update location of referenced dsa.txt

Please re-post this with the netdev mailing list CC:'d, thank you.

Re: [PATCH 3/4] watchdog: Split up config options

On Fri, Jun 16, 2017 at 01:59:00AM +1000, Nicholas Piggin wrote: > On Thu, 15 Jun 2017 11:51:22 -0400 > Don Zickus wrote: > > > On Thu, Jun 15, 2017 at 01:04:01PM +1000, Nicholas Piggin wrote: > > > > +#ifdef CONFIG_HARDLOCKUP_DETECTOR > > > > /* boot commands */ > > > >

Re: [PATCH 3/4] watchdog: Split up config options

On Fri, Jun 16, 2017 at 01:59:00AM +1000, Nicholas Piggin wrote: > On Thu, 15 Jun 2017 11:51:22 -0400 > Don Zickus wrote: > > > On Thu, Jun 15, 2017 at 01:04:01PM +1000, Nicholas Piggin wrote: > > > > +#ifdef CONFIG_HARDLOCKUP_DETECTOR > > > > /* boot commands */ > > > > /* > > > >*

Re: [PATCH 0/4] i2c: document DMA handling and add helpers for it

On Thu, Jun 15, 2017 at 08:30:35PM +0200, Wolfram Sang wrote: > So, after revisiting old mail threads and taking part in a similar discussion > on the USB list, here is what I cooked up to document and ease DMA handling > for > I2C within Linux. Please have a look at the documentation introduced

Re: [PATCH 0/4] i2c: document DMA handling and add helpers for it

On Thu, Jun 15, 2017 at 08:30:35PM +0200, Wolfram Sang wrote: > So, after revisiting old mail threads and taking part in a similar discussion > on the USB list, here is what I cooked up to document and ease DMA handling > for > I2C within Linux. Please have a look at the documentation introduced

Re: [PATCH] sparc/time: make of_device_ids const

From: Arvind Yadav Date: Thu, 15 Jun 2017 16:30:20 +0530 > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > Signed-off-by: Arvind

Re: [PATCH] sparc/time: make of_device_ids const

From: Arvind Yadav Date: Thu, 15 Jun 2017 16:30:20 +0530 > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav Applied.

[PATCH 4.4 05/46] Call echo service immediately after socket reconnect

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit b8c600120fc87d53642476f48c8055b38d6e14c7 upstream. Commit 4fcd1813e640 ("Fix reconnect to not defer smb3 session reconnect long after socket

[PATCH 4.4 05/46] Call echo service immediately after socket reconnect

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit b8c600120fc87d53642476f48c8055b38d6e14c7 upstream. Commit 4fcd1813e640 ("Fix reconnect to not defer smb3 session reconnect long after socket reconnect") changes the

[PATCH 4.4 01/46] s390/vmem: fix identity mapping

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit c34a69059d7876e0793eb410deedfb08ccb22b02 upstream. The identity mapping is suboptimal for the last 2GB frame. The mapping will be established

[PATCH 4.4 01/46] s390/vmem: fix identity mapping

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit c34a69059d7876e0793eb410deedfb08ccb22b02 upstream. The identity mapping is suboptimal for the last 2GB frame. The mapping will be established with a mix of 4KB and 1MB

[PATCH 4.4 03/46] ARM: dts: imx6dl: Fix the VDD_ARM_CAP voltage for 396MHz operation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Fabio Estevam commit 46350b71a09ccf3573649e03db55d4b61d5da231 upstream. Table 8 from MX6DL datasheet (IMX6SDLCEC Rev. 5, 06/2015):

[PATCH 4.4 03/46] ARM: dts: imx6dl: Fix the VDD_ARM_CAP voltage for 396MHz operation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Fabio Estevam commit 46350b71a09ccf3573649e03db55d4b61d5da231 upstream. Table 8 from MX6DL datasheet (IMX6SDLCEC Rev. 5, 06/2015):

[PATCH 4.4 00/46] 4.4.73-stable review

This is the start of the stable review cycle for the 4.4.73 release. There are 46 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 Sat Jun 17 17:51:59 UTC 2017. Anything

[PATCH 4.4 00/46] 4.4.73-stable review

This is the start of the stable review cycle for the 4.4.73 release. There are 46 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 Sat Jun 17 17:51:59 UTC 2017. Anything

[PATCH 4.4 15/46] i2c: piix4: Fix request_region size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda [ Upstream commit f43128c75202f29ee71aa83e6c320a911137c189 ] Since '701dc207bf55 ("i2c: piix4: Avoid race conditions with IMC")' we are using the

[PATCH 2/2] perf coresight: Remove superfluous check before use

cs_etm_evsel is guaranteed to be set at this point in the function. Signed-off-by: Kim Phillips --- tools/perf/arch/arm/util/cs-etm.c | 25 - 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/tools/perf/arch/arm/util/cs-etm.c

[PATCH 4.4 15/46] i2c: piix4: Fix request_region size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda [ Upstream commit f43128c75202f29ee71aa83e6c320a911137c189 ] Since '701dc207bf55 ("i2c: piix4: Avoid race conditions with IMC")' we are using the SMBSLVCNT register at offset

[PATCH 2/2] perf coresight: Remove superfluous check before use

cs_etm_evsel is guaranteed to be set at this point in the function. Signed-off-by: Kim Phillips --- tools/perf/arch/arm/util/cs-etm.c | 25 - 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/tools/perf/arch/arm/util/cs-etm.c

Re: [PATCH v7 10/26] x86/insn-eval: Add utility functions to get segment selector

On Tue, 2017-05-30 at 12:35 +0200, Borislav Petkov wrote: > On Fri, May 05, 2017 at 11:17:08AM -0700, Ricardo Neri wrote: > > When computing a linear address and segmentation is used, we need to know > > the base address of the segment involved in the computation. In most of > > the cases, the

Re: [PATCH v7 10/26] x86/insn-eval: Add utility functions to get segment selector

On Tue, 2017-05-30 at 12:35 +0200, Borislav Petkov wrote: > On Fri, May 05, 2017 at 11:17:08AM -0700, Ricardo Neri wrote: > > When computing a linear address and segmentation is used, we need to know > > the base address of the segment involved in the computation. In most of > > the cases, the

[PATCH 4.4 18/46] jump label: pass kbuild_cflags when checking for asm goto support

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Lin [ Upstream commit 35f860f9ba6aac56cc38e8b18916d833a83f1157 ] Some versions of ARM GCC compiler such as Android toolchain throws in a '-fpic' flag by default.

[PATCH 4.4 18/46] jump label: pass kbuild_cflags when checking for asm goto support

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Lin [ Upstream commit 35f860f9ba6aac56cc38e8b18916d833a83f1157 ] Some versions of ARM GCC compiler such as Android toolchain throws in a '-fpic' flag by default. This causes the

[PATCH 4.4 20/46] log2: make order_base_2() behave correctly on const input value zero

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 29905b52fad0854351f57bab867647e4982285bf upstream. The function order_base_2() is defined (according to the comment block) as returning zero on

[PATCH 4.4 20/46] log2: make order_base_2() behave correctly on const input value zero

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 29905b52fad0854351f57bab867647e4982285bf upstream. The function order_base_2() is defined (according to the comment block) as returning zero on input zero, but

[PATCH 4.4 24/46] FS-Cache: Initialise stores_lock in netfs cookie

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 62deb8187d116581c88c69a2dd9b5c16588545d4 ] Initialise the stores_lock in fscache netfs cookies. Technically, it shouldn't be necessary,

[PATCH 4.4 24/46] FS-Cache: Initialise stores_lock in netfs cookie

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 62deb8187d116581c88c69a2dd9b5c16588545d4 ] Initialise the stores_lock in fscache netfs cookies. Technically, it shouldn't be necessary, since the netfs cookie

[PATCH 4.4 36/46] nfs: Fix "Dont increment lock sequence ID after NFS4ERR_MOVED"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever [ Upstream commit 406dab8450ec76eca88a1af2fc15d18a2b36ca49 ] Lock sequence IDs are bumped in decode_lock by calling nfs_increment_seqid().

[PATCH 4.4 36/46] nfs: Fix "Dont increment lock sequence ID after NFS4ERR_MOVED"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever [ Upstream commit 406dab8450ec76eca88a1af2fc15d18a2b36ca49 ] Lock sequence IDs are bumped in decode_lock by calling nfs_increment_seqid(). nfs_increment_sequid() does not use the

[PATCH 4.4 23/46] fscache: Clear outstanding writes when disabling a cookie

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 6bdded59c8933940ac7e5b416448276ac89d1144 ] fscache_disable_cookie() needs to clear the outstanding writes on the cookie it's disabling

[PATCH 4.9 066/108] nfs: Fix "Dont increment lock sequence ID after NFS4ERR_MOVED"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever [ Upstream commit 406dab8450ec76eca88a1af2fc15d18a2b36ca49 ] Lock sequence IDs are bumped in decode_lock by calling nfs_increment_seqid().

[PATCH 4.4 23/46] fscache: Clear outstanding writes when disabling a cookie

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 6bdded59c8933940ac7e5b416448276ac89d1144 ] fscache_disable_cookie() needs to clear the outstanding writes on the cookie it's disabling because they cannot be

[PATCH 4.9 066/108] nfs: Fix "Dont increment lock sequence ID after NFS4ERR_MOVED"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever [ Upstream commit 406dab8450ec76eca88a1af2fc15d18a2b36ca49 ] Lock sequence IDs are bumped in decode_lock by calling nfs_increment_seqid(). nfs_increment_sequid() does not use the

[PATCH 4.4 25/46] ipv6: fix flow labels when the traffic class is non-0

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dimitris Michailidis [ Upstream commit 90427ef5d2a4b9a24079889bf16afdcdaebc4240 ] ip6_make_flowlabel() determines the flow label for IPv6 packets. It's supposed to be

[PATCH 4.4 25/46] ipv6: fix flow labels when the traffic class is non-0

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dimitris Michailidis [ Upstream commit 90427ef5d2a4b9a24079889bf16afdcdaebc4240 ] ip6_make_flowlabel() determines the flow label for IPv6 packets. It's supposed to be passed a flow label,

[PATCH 4.4 29/46] gianfar: synchronize DMA API usage by free_skb_rx_queue w/ gfar_new_page

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arseny Solokha [ Upstream commit 4af0e5bb95ee3ba5ea4bd7dbb94e1648a5279cc9 ] In spite of switching to paged allocation of Rx buffers, the driver still called

[PATCH 4.4 27/46] drm/nouveau/fence/g84-: protect against concurrent access to semaphore buffers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs [ Upstream commit 96692b097ba76d0c637ae8af47b29c73da33c9d0 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin

[PATCH 4.4 27/46] drm/nouveau/fence/g84-: protect against concurrent access to semaphore buffers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs [ Upstream commit 96692b097ba76d0c637ae8af47b29c73da33c9d0 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.4 29/46] gianfar: synchronize DMA API usage by free_skb_rx_queue w/ gfar_new_page

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arseny Solokha [ Upstream commit 4af0e5bb95ee3ba5ea4bd7dbb94e1648a5279cc9 ] In spite of switching to paged allocation of Rx buffers, the driver still called dma_unmap_single() in the Rx

[PATCH 4.4 26/46] drm/nouveau: prevent userspace from deleting client object

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs [ Upstream commit c966b6279f610a24ac1d42dcbe30e10fa61220b2 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin

[PATCH 4.4 31/46] net: adaptec: starfire: add checks for dma mapping errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov [ Upstream commit d1156b489fa734d1af763d6a07b1637c01bb0aed ] init_ring(), refill_rx_ring() and start_tx() don't check if mapping dma memory succeed.

[PATCH 4.4 26/46] drm/nouveau: prevent userspace from deleting client object

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs [ Upstream commit c966b6279f610a24ac1d42dcbe30e10fa61220b2 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.4 31/46] net: adaptec: starfire: add checks for dma mapping errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov [ Upstream commit d1156b489fa734d1af763d6a07b1637c01bb0aed ] init_ring(), refill_rx_ring() and start_tx() don't check if mapping dma memory succeed. The patch adds the

[PATCH 4.4 33/46] drm/nouveau: Dont enabling polling twice on runtime resume

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul [ Upstream commit cae9ff036eea577856d5b12860b4c79c5e71db4a ] As it turns out, on cards that actually have CRTCs on them we're already calling

[PATCH 4.4 33/46] drm/nouveau: Dont enabling polling twice on runtime resume

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul [ Upstream commit cae9ff036eea577856d5b12860b4c79c5e71db4a ] As it turns out, on cards that actually have CRTCs on them we're already calling drm_kms_helper_poll_enable(drm_dev)

[PATCH 4.4 07/46] net: xilinx_emaclite: fix receive buffer overflow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Anssi Hannula [ Upstream commit cd224553641848dd17800fe559e4ff5d208553e8 ] xilinx_emaclite looks at the received data to try to determine the Ethernet packet length

[PATCH 4.4 34/46] drm/ast: Fixed system hanged if disable P2A

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Y.C. Chen" [ Upstream commit 6c971c09f38704513c426ba6515f22fb3d6c87d5 ] The original ast driver will access some BMC configuration through P2A bridge that can be

[PATCH 4.4 07/46] net: xilinx_emaclite: fix receive buffer overflow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Anssi Hannula [ Upstream commit cd224553641848dd17800fe559e4ff5d208553e8 ] xilinx_emaclite looks at the received data to try to determine the Ethernet packet length but does not properly

[PATCH 4.4 34/46] drm/ast: Fixed system hanged if disable P2A

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Y.C. Chen" [ Upstream commit 6c971c09f38704513c426ba6515f22fb3d6c87d5 ] The original ast driver will access some BMC configuration through P2A bridge that can be disabled since AST2300 and

Re: [PATCH 2/2] Input: pm8941-pwrkey: Introduce reboot mode support

On Thu 15 Jun 09:26 PDT 2017, Sebastian Reichel wrote: > Hi, > > On Mon, Jun 12, 2017 at 04:32:03PM -0700, Bjorn Andersson wrote: [..] > > As such if we split the non-input related handling into another driver > > we would need to make the input driver create a subdevice during probe - > > or

Re: [PATCH 2/2] Input: pm8941-pwrkey: Introduce reboot mode support

On Thu 15 Jun 09:26 PDT 2017, Sebastian Reichel wrote: > Hi, > > On Mon, Jun 12, 2017 at 04:32:03PM -0700, Bjorn Andersson wrote: [..] > > As such if we split the non-input related handling into another driver > > we would need to make the input driver create a subdevice during probe - > > or

[PATCH 4.4 35/46] ravb: unmap descriptors when freeing rings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kazuya Mizuguchi [ Upstream commit a47b70ea86bdeb3091341f5ae3ef580f1a1ad822 ] "swiotlb buffer is full" errors occur after repeated initialisation of a device

[PATCH 4.4 35/46] ravb: unmap descriptors when freeing rings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kazuya Mizuguchi [ Upstream commit a47b70ea86bdeb3091341f5ae3ef580f1a1ad822 ] "swiotlb buffer is full" errors occur after repeated initialisation of a device - f.e. suspend/resume or ip link

[PATCH 4.4 32/46] parisc, parport_gsc: Fixes for printk continuation lines

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller [ Upstream commit 83b5d1e3d3013dbf90645a5d07179d018c8243fa ] Signed-off-by: Helge Deller Signed-off-by: Sasha Levin

[PATCH 4.4 08/46] ipv6: Handle IPv4-mapped src to in6addr_any dst.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Jonathan T. Leighton" [ Upstream commit 052d2369d1b479cdbbe020fdd6d057d3c342db74 ] This patch adds a check on the type of the source address for the case where the

[PATCH 4.4 32/46] parisc, parport_gsc: Fixes for printk continuation lines

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller [ Upstream commit 83b5d1e3d3013dbf90645a5d07179d018c8243fa ] Signed-off-by: Helge Deller Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.4 08/46] ipv6: Handle IPv4-mapped src to in6addr_any dst.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Jonathan T. Leighton" [ Upstream commit 052d2369d1b479cdbbe020fdd6d057d3c342db74 ] This patch adds a check on the type of the source address for the case where the destination address is

[PATCH 4.4 30/46] pinctrl: berlin-bg4ct: fix the value for "sd1a" of pin SCRD0_CRD_PRES

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jisheng Zhang [ Upstream commit e82d02580af45663fad6d3596e4344c606e81e10 ] This should be a typo. Signed-off-by: Jisheng Zhang Signed-off-by: Linus

[PATCH 4.4 30/46] pinctrl: berlin-bg4ct: fix the value for "sd1a" of pin SCRD0_CRD_PRES

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jisheng Zhang [ Upstream commit e82d02580af45663fad6d3596e4344c606e81e10 ] This should be a typo. Signed-off-by: Jisheng Zhang Signed-off-by: Linus Walleij Signed-off-by: Sasha Levin

[PATCH 4.4 12/46] net: hns: Fix the device being used for dma mapping during TX

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kejian Yan [ Upstream commit b85ea006b6bebb692628f11882af41c3e12e1e09 ] This patch fixes the device being used to DMA map skb->data. Erroneous device assignment causes

[PATCH 4.4 12/46] net: hns: Fix the device being used for dma mapping during TX

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kejian Yan [ Upstream commit b85ea006b6bebb692628f11882af41c3e12e1e09 ] This patch fixes the device being used to DMA map skb->data. Erroneous device assignment causes the crash when SMMU is

[PATCH 0/4] i2c: document DMA handling and add helpers for it

So, after revisiting old mail threads and taking part in a similar discussion on the USB list, here is what I cooked up to document and ease DMA handling for I2C within Linux. Please have a look at the documentation introduced in patch 2 for further details. The branch can be found here:

[PATCH 0/4] i2c: document DMA handling and add helpers for it

So, after revisiting old mail threads and taking part in a similar discussion on the USB list, here is what I cooked up to document and ease DMA handling for I2C within Linux. Please have a look at the documentation introduced in patch 2 for further details. The branch can be found here:

Re: [PATCH net-next 0/3] r8152: support new chips

From: Hayes Wang Date: Thu, 15 Jun 2017 14:44:01 +0800 > These patches are used to support new chips. Series applied, thank you.

Re: [PATCH net-next 0/3] r8152: support new chips

From: Hayes Wang Date: Thu, 15 Jun 2017 14:44:01 +0800 > These patches are used to support new chips. Series applied, thank you.

[PATCH 1/4] i2c: add helpers to ease DMA handling

One helper checks if DMA is suitable and optionally creates a bounce buffer, if not. The other function returns the bounce buffer and makes sure the data is properly copied back to the message. Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang

[PATCH 1/4] i2c: add helpers to ease DMA handling

One helper checks if DMA is suitable and optionally creates a bounce buffer, if not. The other function returns the bounce buffer and makes sure the data is properly copied back to the message. Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang --- include/linux/i2c.h | 65

[PATCH 4/4] i2c: rcar: check for DMA-capable buffers

Handling this is special for this driver. Because the hardware needs to initialize the next message in interrupt context, we cannot use the i2c_check_msg_for_dma() directly. This helper only works reliably in process context. So, we need to check during initial preparation of the whole transfer

[PATCH 4/4] i2c: rcar: check for DMA-capable buffers

Handling this is special for this driver. Because the hardware needs to initialize the next message in interrupt context, we cannot use the i2c_check_msg_for_dma() directly. This helper only works reliably in process context. So, we need to check during initial preparation of the whole transfer

[PATCH 2/4] i2c: add docs to clarify DMA handling

Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang --- Documentation/i2c/DMA-considerations | 37 1 file changed, 37 insertions(+) create mode 100644 Documentation/i2c/DMA-considerations diff --git

[PATCH 2/4] i2c: add docs to clarify DMA handling

Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang --- Documentation/i2c/DMA-considerations | 37 1 file changed, 37 insertions(+) create mode 100644 Documentation/i2c/DMA-considerations diff --git a/Documentation/i2c/DMA-considerations

[PATCH 4.4 04/46] staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Malcolm Priestley commit baabd567f87be05330faa5140f72a91960e7405a upstream. The driver attempts to alter memory that is mapped to PCI device. This is because

[PATCH 4.4 04/46] staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Malcolm Priestley commit baabd567f87be05330faa5140f72a91960e7405a upstream. The driver attempts to alter memory that is mapped to PCI device. This is because tx_fwinfo_8190pci points to

[PATCH 4.4 11/46] NET: mkiss: Fix panic

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ralf Baechle [ Upstream commit 7ba1b689038726d34e3244c1ac9e2e18c2ea4787 ] If a USB-to-serial adapter is unplugged, the driver re-initializes, with dev->hard_header_len

[PATCH 3/4] i2c: sh_mobile: use helper to decide if DMA is useful

This ensures that we fall back to PIO if the buffer is too small for DMA being useful. Otherwise, we use DMA. A bounce buffer might be applied if the original message buffer is not DMA safe Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang

[PATCH 4.4 11/46] NET: mkiss: Fix panic

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ralf Baechle [ Upstream commit 7ba1b689038726d34e3244c1ac9e2e18c2ea4787 ] If a USB-to-serial adapter is unplugged, the driver re-initializes, with dev->hard_header_len and dev->addr_len set

[PATCH 3/4] i2c: sh_mobile: use helper to decide if DMA is useful

This ensures that we fall back to PIO if the buffer is too small for DMA being useful. Otherwise, we use DMA. A bounce buffer might be applied if the original message buffer is not DMA safe Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang --- drivers/i2c/busses/i2c-sh_mobile.c | 8

Re: LTS testing with latest kselftests - some failures

Hi Sumit, On 06/15/2017 11:56 AM, Sumit Semwal wrote: > Hello Greg, Shuah, > > While testing 4.4.y and 4.9.y LTS kernels with latest kselftest, we > found a couple more test failures due to test-kernel mismatch: > > 1. firmware tests: - linux 4.5 [1] and 4.10 [2] added a few updates to > tests,

[PATCH 4.4 40/46] sctp: sctp_addr_id2transport should verify the addr before looking up assoc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 6f29a130613191d3c6335169febe002cba00edf5 ] sctp_addr_id2transport is a function for sockopt to look up assoc by address. As the address is

Re: LTS testing with latest kselftests - some failures

Hi Sumit, On 06/15/2017 11:56 AM, Sumit Semwal wrote: > Hello Greg, Shuah, > > While testing 4.4.y and 4.9.y LTS kernels with latest kselftest, we > found a couple more test failures due to test-kernel mismatch: > > 1. firmware tests: - linux 4.5 [1] and 4.10 [2] added a few updates to > tests,

[PATCH 4.4 40/46] sctp: sctp_addr_id2transport should verify the addr before looking up assoc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 6f29a130613191d3c6335169febe002cba00edf5 ] sctp_addr_id2transport is a function for sockopt to look up assoc by address. As the address is from userspace, it can be

[PATCH 4.4 10/46] NET: Fix /proc/net/arp for AX.25

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ralf Baechle [ Upstream commit 4872e57c812dd312bf8193b5933fa60585cda42f ] When sending ARP requests over AX.25 links the hwaddress in the neighbour cache are not getting

[PATCH 4.4 39/46] r8152: avoid start_xmit to schedule napi when napi is disabled

4.4-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit de9bf29dd6e4a8a874cb92f8901aed50a9d0b1d3 ] Stop the tx when the napi is disabled to prevent napi_schedule() is called. Signed-off-by: Hayes

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