[PATCH v2 6/7] spi: spi-ep93xx: remove private data 'current_msg'

From: H Hartley Sweeten The currently in-flight message can be found from the spi master. Use that instead and remove the private data pointer. Signed-off-by: H Hartley Sweeten Reviewed-by: Andy Shevchenko --- drivers/spi/spi-ep93xx.c | 16 +--- 1 file changed, 5 insertions(+),

[PATCH v2 3/7] spi: spi-ep93xx: add spi master prepare_transfer_hardware()

From: H Hartley Sweeten This driver currently enables the hardware at the start of every message and disabled it when the message is complete. Make it a bit smarter by adding the prepare_transfer_hardware() and unprepare_transfer_hardware() callbacks so that the core can enable/disable the

[PATCH v2 0/7] spi: spi-ep93xx: cleanup and update driver to modern API

Cleanup and update this driver to use the default master transfer queueing mechanism provided by the core. I've been carrying these changes locally to use as a basis for other SPI work. Mark Brown pointed out that he's simply missed seeing it, Andy Shevchenko had some minor comment's which I've

[PATCH v2 7/7] spi: spi-ep93xx: use the default master transfer queueing mechanism

From: H Hartley Sweeten Update this driver to the default implementation of transfer_one_message(). Signed-off-by: H Hartley Sweeten Reviewed-by: Andy Shevchenko --- drivers/spi/spi-ep93xx.c | 322

[PATCH v2 0/7] spi: spi-ep93xx: cleanup and update driver to modern API

Cleanup and update this driver to use the default master transfer queueing mechanism provided by the core. I've been carrying these changes locally to use as a basis for other SPI work. Mark Brown pointed out that he's simply missed seeing it, Andy Shevchenko had some minor comment's which I've

[PATCH v2 7/7] spi: spi-ep93xx: use the default master transfer queueing mechanism

From: H Hartley Sweeten Update this driver to the default implementation of transfer_one_message(). Signed-off-by: H Hartley Sweeten Reviewed-by: Andy Shevchenko --- drivers/spi/spi-ep93xx.c | 322 --- 1 file changed, 108 insertions(+), 214

[PATCH 1/2] wireless: move prism54 out to staging

prism54 is deprecated in favor of the p54pci device driver. Although only *one soul* had reported issues with it long ago Linux most Linux distributions these days just disable the device driver given the conflicts with the PCI IDs of p54pci and the *very* unlikely situation of folks really need

[PATCH 1/2] wireless: move prism54 out to staging

prism54 is deprecated in favor of the p54pci device driver. Although only *one soul* had reported issues with it long ago Linux most Linux distributions these days just disable the device driver given the conflicts with the PCI IDs of p54pci and the *very* unlikely situation of folks really need

[PATCH 2/2] MAINTAINERS: update email address for mcgrof for few straggling drivers

This will ensure I get emails on my work and personal email address. Signed-off-by: Luis R. Rodriguez --- MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 97cf436e6750..49ae596584e7 100644 --- a/MAINTAINERS

[PATCH 2/2] MAINTAINERS: update email address for mcgrof for few straggling drivers

This will ensure I get emails on my work and personal email address. Signed-off-by: Luis R. Rodriguez --- MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 97cf436e6750..49ae596584e7 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

[PATCH 0/2] wireless: move prism54 to staging

Kalle, Greg, This moves the prism54 diver to staging. The reason for this are stated on the driver's own commit log. Let me know what tree you'd prefer this to go through. Luis R. Rodriguez (2): wireless: move prism54 out to staging MAINTAINERS: update email address for mcgrof for few

[PATCH 0/2] wireless: move prism54 to staging

Kalle, Greg, This moves the prism54 diver to staging. The reason for this are stated on the driver's own commit log. Let me know what tree you'd prefer this to go through. Luis R. Rodriguez (2): wireless: move prism54 out to staging MAINTAINERS: update email address for mcgrof for few

Re: [PATCH] mm: fix list corruptions on shmem shrinklist

On Thu, 3 Aug 2017 16:25:46 -0700 Linus Torvalds wrote: > On Thu, Aug 3, 2017 at 4:11 PM, Andrew Morton > wrote: > > > > Where is this INIT_LIST_HEAD()? > > I think it's this one: > > list_del_init(>shrinklist); > > in

Re: [PATCH] mm: fix list corruptions on shmem shrinklist

On Thu, 3 Aug 2017 16:25:46 -0700 Linus Torvalds wrote: > On Thu, Aug 3, 2017 at 4:11 PM, Andrew Morton > wrote: > > > > Where is this INIT_LIST_HEAD()? > > I think it's this one: > > list_del_init(>shrinklist); > > in shmem_unused_huge_shrink(). OK. > > I'm not sure I'm

Re: wake_wide mechanism clarification

Hi Michael, Thanks for your reply. On Wed, Aug 2, 2017 at 1:26 AM, Michael Wang wrote: > Hi, Joel > > On 07/29/2017 10:13 AM, Joel Fernandes wrote: >> +Michael Wang on his current email address (old one bounced). (my >> reply was to Mike Galbraith but I also meant to

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

On 08/03/17 at 08:24pm, Chao Fan wrote: > It's almost another "mem=". Then why not using 'mem=' directly? > > On Thu, Aug 03, 2017 at 08:17:21PM +0800, Dou Liyang wrote: > >movable_node is a boot-time switch to make hot-pluggable memory > >NUMA nodes to be movable. This option is based on an

Re: wake_wide mechanism clarification

Hi Michael, Thanks for your reply. On Wed, Aug 2, 2017 at 1:26 AM, Michael Wang wrote: > Hi, Joel > > On 07/29/2017 10:13 AM, Joel Fernandes wrote: >> +Michael Wang on his current email address (old one bounced). (my >> reply was to Mike Galbraith but I also meant to CC Michael Wang for >> the

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

On 08/03/17 at 08:24pm, Chao Fan wrote: > It's almost another "mem=". Then why not using 'mem=' directly? > > On Thu, Aug 03, 2017 at 08:17:21PM +0800, Dou Liyang wrote: > >movable_node is a boot-time switch to make hot-pluggable memory > >NUMA nodes to be movable. This option is based on an

Dear user

Dear user Your mailbox has exceeded the storage limit of 20GB set by the administrator, you are currently running at 20.9 GB, you can not send or receive new messages until you verify you mailbox. Re-validate your account by mail, please fill and Send the data below to verify and

Dear user

Dear user Your mailbox has exceeded the storage limit of 20GB set by the administrator, you are currently running at 20.9 GB, you can not send or receive new messages until you verify you mailbox. Re-validate your account by mail, please fill and Send the data below to verify and

Re: [PATCH 1/3] dt-bindings: pinctrl: mt2712: add binding document

On Mon, Jul 31, 2017 at 04:22:11PM +0800, Zhiyong Tao wrote: > The commit adds mt2712 compatible node in binding document. > > Signed-off-by: Zhiyong Tao > --- > .../devicetree/bindings/pinctrl/pinctrl-mt65xx.txt |1 + > 1 file changed, 1 insertion(+) Acked-by:

Re: [PATCH 1/3] dt-bindings: pinctrl: mt2712: add binding document

On Mon, Jul 31, 2017 at 04:22:11PM +0800, Zhiyong Tao wrote: > The commit adds mt2712 compatible node in binding document. > > Signed-off-by: Zhiyong Tao > --- > .../devicetree/bindings/pinctrl/pinctrl-mt65xx.txt |1 + > 1 file changed, 1 insertion(+) Acked-by: Rob Herring

Re: [PATCH v6 6/7] dt-bindings: pci: qcom: Add support for IPQ8074

On Mon, Jul 31, 2017 at 12:04:16PM +0530, Varadarajan Narayanan wrote: > Add support for the IPQ8074 PCIe controller. IPQ8074 supports Gen 1/2, one > lane, two PCIe root complex with support for MSI and legacy interrupts, and > it conforms to PCI Express Base 2.1 specification. > >

Re: [PATCH v6 6/7] dt-bindings: pci: qcom: Add support for IPQ8074

On Mon, Jul 31, 2017 at 12:04:16PM +0530, Varadarajan Narayanan wrote: > Add support for the IPQ8074 PCIe controller. IPQ8074 supports Gen 1/2, one > lane, two PCIe root complex with support for MSI and legacy interrupts, and > it conforms to PCI Express Base 2.1 specification. > >

Re: [PATCH v6 2/7] dt-bindings: phy: qmp: Add support for QMP phy in IPQ8074

On Mon, Jul 31, 2017 at 12:04:12PM +0530, Varadarajan Narayanan wrote: > IPQ8074 uses QMP phy controller that provides support to PCIe and > USB. Adding dt binding information for the same. > > Reviewed-by: Vivek Gautam > Signed-off-by: Varadarajan Narayanan

Re: [PATCH v6 2/7] dt-bindings: phy: qmp: Add support for QMP phy in IPQ8074

On Mon, Jul 31, 2017 at 12:04:12PM +0530, Varadarajan Narayanan wrote: > IPQ8074 uses QMP phy controller that provides support to PCIe and > USB. Adding dt binding information for the same. > > Reviewed-by: Vivek Gautam > Signed-off-by: Varadarajan Narayanan > --- >

Re: [PATCH] ASoC: rockchip: add bindings for i2s

On Mon, Jul 31, 2017 at 09:47:51AM +0800, Sugar Zhang wrote: > This patch add bindings for rk3036/rk3228/rk3328/rk3366 i2s. > > Signed-off-by: Sugar Zhang > --- > > Documentation/devicetree/bindings/sound/rockchip-i2s.txt | 4 > 1 file changed, 4 insertions(+)

Re: [PATCH] ASoC: rockchip: add bindings for i2s

On Mon, Jul 31, 2017 at 09:47:51AM +0800, Sugar Zhang wrote: > This patch add bindings for rk3036/rk3228/rk3328/rk3366 i2s. > > Signed-off-by: Sugar Zhang > --- > > Documentation/devicetree/bindings/sound/rockchip-i2s.txt | 4 > 1 file changed, 4 insertions(+) Acked-by: Rob Herring

Re: [PATCH v2 1/5] of/platform: Generalize /reserved-memory handling

On Thu 03 Aug 10:40 PDT 2017, Rob Herring wrote: > On Wed, Aug 2, 2017 at 9:57 PM, Bjorn Andersson > wrote: > > diff --git a/drivers/of/platform.c b/drivers/of/platform.c [..] > > + rmem_nodes = of_find_node_by_path("/reserved-memory"); > > +

Re: [PATCH v2 1/5] of/platform: Generalize /reserved-memory handling

On Thu 03 Aug 10:40 PDT 2017, Rob Herring wrote: > On Wed, Aug 2, 2017 at 9:57 PM, Bjorn Andersson > wrote: > > diff --git a/drivers/of/platform.c b/drivers/of/platform.c [..] > > + rmem_nodes = of_find_node_by_path("/reserved-memory"); > > +

Re: [PATCH] of: Update Moxa vendor prefix description

On Sun, Jul 30, 2017 at 09:45:04AM +0800, SZ Lin wrote: > Update vendor description to be the full name of the corporate entity > with this prefix > > reference: > [1]: http://tmsearch.uspto.gov/bin/showfield?f=doc=4806:26uh56.2.5 > > Signed-off-by: SZ Lin > --- >

Re: [PATCH] of: Update Moxa vendor prefix description

On Sun, Jul 30, 2017 at 09:45:04AM +0800, SZ Lin wrote: > Update vendor description to be the full name of the corporate entity > with this prefix > > reference: > [1]: http://tmsearch.uspto.gov/bin/showfield?f=doc=4806:26uh56.2.5 > > Signed-off-by: SZ Lin > --- >

Re: [Question]: try to fix contention between expire_timers and try_to_del_timer_sync

Hi Qiao, On 2017-08-01 00:37, qiaozhou wrote: On 2017年07月31日 19:20, qiaozhou wrote: = Also apply Vikram's patch and have a test. cpu2: a53, 832MHz, cpu7: a73, 1.75Hz Without cpu_relax bodging patch

Re: [Question]: try to fix contention between expire_timers and try_to_del_timer_sync

Hi Qiao, On 2017-08-01 00:37, qiaozhou wrote: On 2017年07月31日 19:20, qiaozhou wrote: = Also apply Vikram's patch and have a test. cpu2: a53, 832MHz, cpu7: a73, 1.75Hz Without cpu_relax bodging patch

Re: [PATCH v2 2/5] of: reserved_mem: Accessor for acquiring reserved_mem

On Thu 03 Aug 10:45 PDT 2017, Rob Herring wrote: > On Wed, Aug 2, 2017 at 9:57 PM, Bjorn Andersson > wrote: > > In some cases drivers referencing a reserved-memory region might want to > > remap the entire region, but when defining the reserved-memory by "size" > >

Re: [PATCH v2 2/5] of: reserved_mem: Accessor for acquiring reserved_mem

On Thu 03 Aug 10:45 PDT 2017, Rob Herring wrote: > On Wed, Aug 2, 2017 at 9:57 PM, Bjorn Andersson > wrote: > > In some cases drivers referencing a reserved-memory region might want to > > remap the entire region, but when defining the reserved-memory by "size" > > the client driver has no means

[PATCH 4.12 04/31] ALSA: hda - Add mute led support for HP ProBook 440 G4

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit ba92b1142879731f8030f4710e5f0a953aad upstream. Mic mute led does not work on HP ProBook 440 G4. We can use CXT_FIXUP_MUTE_LED_GPIO fixup

[PATCH 4.12 04/31] ALSA: hda - Add mute led support for HP ProBook 440 G4

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit ba92b1142879731f8030f4710e5f0a953aad upstream. Mic mute led does not work on HP ProBook 440 G4. We can use CXT_FIXUP_MUTE_LED_GPIO fixup to support it. BugLink:

Re: [PATCH 3/5] net: stmmac: Add Adaptrum Anarion GMAC glue layer

On Fri, Jul 28, 2017 at 03:07:03PM -0700, Alexandru Gagniuc wrote: > Before the GMAC on the Anarion chip can be used, the PHY interface > selection must be configured with the DWMAC block in reset. > > This layer covers a block containing only two registers. Although it > is possible to model

Re: [PATCH 3/5] net: stmmac: Add Adaptrum Anarion GMAC glue layer

On Fri, Jul 28, 2017 at 03:07:03PM -0700, Alexandru Gagniuc wrote: > Before the GMAC on the Anarion chip can be used, the PHY interface > selection must be configured with the DWMAC block in reset. > > This layer covers a block containing only two registers. Although it > is possible to model

Re: [PATCH] mm: fix list corruptions on shmem shrinklist

On Thu, Aug 3, 2017 at 4:11 PM, Andrew Morton wrote: > > Where is this INIT_LIST_HEAD()? I think it's this one: list_del_init(>shrinklist); in shmem_unused_huge_shrink(). > I'm not sure I'm understanding this. AFAICT all the list operations to > which you

Re: [PATCH] mm: fix list corruptions on shmem shrinklist

On Thu, Aug 3, 2017 at 4:11 PM, Andrew Morton wrote: > > Where is this INIT_LIST_HEAD()? I think it's this one: list_del_init(>shrinklist); in shmem_unused_huge_shrink(). > I'm not sure I'm understanding this. AFAICT all the list operations to > which you refer are synchronized under

[PATCH 4.12 05/31] parisc: Prevent TLB speculation on flushed pages on CPUs that only support equivalent aliases

4.12-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit ae7a609c34b6fb12328c553b5f9aab26ae74a28e upstream. Helge noticed that we flush the TLB page in flush_cache_page but not in flush_cache_range or

[PATCH 4.12 00/31] 4.12.5-stable review

This is the start of the stable review cycle for the 4.12.5 release. There are 31 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 Aug 5 23:17:23 UTC 2017. Anything

[PATCH 4.12 05/31] parisc: Prevent TLB speculation on flushed pages on CPUs that only support equivalent aliases

4.12-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit ae7a609c34b6fb12328c553b5f9aab26ae74a28e upstream. Helge noticed that we flush the TLB page in flush_cache_page but not in flush_cache_range or flush_cache_mm. For a

[PATCH 4.12 00/31] 4.12.5-stable review

This is the start of the stable review cycle for the 4.12.5 release. There are 31 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 Aug 5 23:17:23 UTC 2017. Anything

Re: [PATCH 1/5] of: Add vendor prefix for Adaptrum, Inc.

On Sat, Jul 29, 2017 at 04:48:28PM +0200, Andreas Färber wrote: > Hi Alexandru, > > Am 29.07.2017 um 00:07 schrieb Alexandru Gagniuc: > > Signed-off-by: Alexandru Gagniuc > > --- > > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > > 1 file changed, 1

Re: [PATCH 1/5] of: Add vendor prefix for Adaptrum, Inc.

On Sat, Jul 29, 2017 at 04:48:28PM +0200, Andreas Färber wrote: > Hi Alexandru, > > Am 29.07.2017 um 00:07 schrieb Alexandru Gagniuc: > > Signed-off-by: Alexandru Gagniuc > > --- > > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > > 1 file changed, 1 insertion(+) > > Not sure

Re: [Question]: try to fix contention between expire_timers and try_to_del_timer_sync

Hi Will, On 2017-07-31 06:13, Will Deacon wrote: Hi Vikram, On Fri, Jul 28, 2017 at 12:09:38PM -0700, Vikram Mulukutla wrote: On 2017-07-28 02:28, Will Deacon wrote: >On Thu, Jul 27, 2017 at 06:10:34PM -0700, Vikram Mulukutla wrote: > This does seem to help. Here's some data after 5 runs

Re: [Question]: try to fix contention between expire_timers and try_to_del_timer_sync

Hi Will, On 2017-07-31 06:13, Will Deacon wrote: Hi Vikram, On Fri, Jul 28, 2017 at 12:09:38PM -0700, Vikram Mulukutla wrote: On 2017-07-28 02:28, Will Deacon wrote: >On Thu, Jul 27, 2017 at 06:10:34PM -0700, Vikram Mulukutla wrote: > This does seem to help. Here's some data after 5 runs

[PATCH 4.12 06/31] parisc: Extend disabled preemption in copy_user_page

4.12-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 56008c04ebc099940021b714da2d7779117cf6a7 upstream. It's always bothered me that we only disable preemption in copy_user_page around the call to

[PATCH 4.12 01/31] jfs: Dont clear SGID when inheriting ACLs

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 9bcf66c72d726322441ec82962994e69157613e4 upstream. When new directory 'DIR1' is created in a directory 'DIR0' with SGID bit set, DIR1 is expected to have SGID

[PATCH 4.12 06/31] parisc: Extend disabled preemption in copy_user_page

4.12-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 56008c04ebc099940021b714da2d7779117cf6a7 upstream. It's always bothered me that we only disable preemption in copy_user_page around the call to flush_dcache_page_asm.

[PATCH 4.12 01/31] jfs: Dont clear SGID when inheriting ACLs

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 9bcf66c72d726322441ec82962994e69157613e4 upstream. When new directory 'DIR1' is created in a directory 'DIR0' with SGID bit set, DIR1 is expected to have SGID bit set (and

[PATCH 4.12 08/31] powerpc/pseries: Fix of_node_put() underflow during reconfig remove

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Vivier commit 4fd1bd443e80b12f0a01a45fb9a793206b41cb72 upstream. As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put() underflow during DLPAR remove"),

[PATCH 4.12 08/31] powerpc/pseries: Fix of_node_put() underflow during reconfig remove

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Vivier commit 4fd1bd443e80b12f0a01a45fb9a793206b41cb72 upstream. As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put() underflow during DLPAR remove"), the call to

[PATCH 4.12 07/31] parisc: Suspend lockup detectors before system halt

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 56188832a50f09998cb570ba3771a1d25c193c0e upstream. Some machines can't power off the machine, so disable the lockup detectors to avoid this watchdog BUG to

[PATCH 4.12 07/31] parisc: Suspend lockup detectors before system halt

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 56188832a50f09998cb570ba3771a1d25c193c0e upstream. Some machines can't power off the machine, so disable the lockup detectors to avoid this watchdog BUG to show up every

[PATCH 4.12 19/31] dm integrity: test for corrupted disk format during table load

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit bc86a41e96c5b6f07453c405e036d95acc673389 upstream. If the dm-integrity superblock was corrupted in such a way that the journal_sections field was

[PATCH 4.12 19/31] dm integrity: test for corrupted disk format during table load

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit bc86a41e96c5b6f07453c405e036d95acc673389 upstream. If the dm-integrity superblock was corrupted in such a way that the journal_sections field was zero, the integrity

Re: [PATCH] PCI: Add const to bin_attribute structures

On Wed, Aug 02, 2017 at 08:57:27PM +0530, Bhumika Goyal wrote: > Add const to bin_attribute structures as they are only passed to the > functions sysfs_{remove/create}_bin_file. The corresponding arguments > are of type const, so declare the structures to be const. > > Signed-off-by: Bhumika

Re: [PATCH] PCI: Add const to bin_attribute structures

On Wed, Aug 02, 2017 at 08:57:27PM +0530, Bhumika Goyal wrote: > Add const to bin_attribute structures as they are only passed to the > functions sysfs_{remove/create}_bin_file. The corresponding arguments > are of type const, so declare the structures to be const. > > Signed-off-by: Bhumika

[PATCH 4.12 03/31] ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Dadap commit 74ec118152ea494a25ebb677cbc83a75c982ac5f upstream. Add codec IDs for several recently released, pending, and historical NVIDIA GPU audio controllers to

[PATCH 4.12 03/31] ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Dadap commit 74ec118152ea494a25ebb677cbc83a75c982ac5f upstream. Add codec IDs for several recently released, pending, and historical NVIDIA GPU audio controllers to the patch table, to

Re: [PATCH 3/5] net: stmmac: Add Adaptrum Anarion GMAC glue layer

On Mon, Jul 31, 2017 at 08:11:00AM -0700, Alex wrote: > Hi David, > > On 07/28/2017 07:01 PM, David Miller wrote: > > From: Alexandru Gagniuc > > Date: Fri, 28 Jul 2017 15:07:03 -0700 > > > > > Before the GMAC on the Anarion chip can be used, the PHY interface > > >

Re: [PATCH 3/5] net: stmmac: Add Adaptrum Anarion GMAC glue layer

On Mon, Jul 31, 2017 at 08:11:00AM -0700, Alex wrote: > Hi David, > > On 07/28/2017 07:01 PM, David Miller wrote: > > From: Alexandru Gagniuc > > Date: Fri, 28 Jul 2017 15:07:03 -0700 > > > > > Before the GMAC on the Anarion chip can be used, the PHY interface > > > selection must be configured

Re: [PATCH 0/5] constify hotplug pci_device_id

On Thu, Aug 03, 2017 at 05:57:49PM -0500, Bjorn Helgaas wrote: > On Thu, Aug 03, 2017 at 10:39:11PM +0530, Arvind Yadav wrote: > > pci_device_id are not supposed to change at runtime. All functions > > working with pci_device_id provided by work with > > const pci_device_id. So mark the non-const

Re: [PATCH 0/5] constify hotplug pci_device_id

On Thu, Aug 03, 2017 at 05:57:49PM -0500, Bjorn Helgaas wrote: > On Thu, Aug 03, 2017 at 10:39:11PM +0530, Arvind Yadav wrote: > > pci_device_id are not supposed to change at runtime. All functions > > working with pci_device_id provided by work with > > const pci_device_id. So mark the non-const

[PATCH 4.12 24/31] drm/vmwgfx: Limit max desktop dimensions to 8Kx8K

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 7b009e76797c82178d7a03ae0eaad5951d975277 upstream. This was originally chosen to be an arbitrarily large number. However, some user mode may actually try

[PATCH 4.12 24/31] drm/vmwgfx: Limit max desktop dimensions to 8Kx8K

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 7b009e76797c82178d7a03ae0eaad5951d975277 upstream. This was originally chosen to be an arbitrarily large number. However, some user mode may actually try to set a 16Kx16K

[PATCH 4.12 26/31] drm/nouveau/bar/gf100: fix access to upper half of BAR2

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f upstream. Bit 30 being set causes the upper half of BAR2 to stay in physical mode, mapped over the end of VRAM,

[PATCH 4.12 26/31] drm/nouveau/bar/gf100: fix access to upper half of BAR2

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f upstream. Bit 30 being set causes the upper half of BAR2 to stay in physical mode, mapped over the end of VRAM, even when the rest

[PATCH 4.12 22/31] md/raid5: add thread_group worker async_tx_issue_pending_all

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Ofer Heifetz commit 7e96d559634b73a8158ee99a7abece2eacec2668 upstream. Since thread_group worker and raid5d kthread are not in sync, if worker writes stripe before raid5d

[PATCH 4.12 22/31] md/raid5: add thread_group worker async_tx_issue_pending_all

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Ofer Heifetz commit 7e96d559634b73a8158ee99a7abece2eacec2668 upstream. Since thread_group worker and raid5d kthread are not in sync, if worker writes stripe before raid5d then requests will

[PATCH 4.12 11/31] NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Coddington commit b7dbcc0e433f0f61acb89ed9861ec996be4f2b38 upstream. nfs4_retry_setlk() sets the task's state to TASK_INTERRUPTIBLE within the same region

[PATCH 4.12 11/31] NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Coddington commit b7dbcc0e433f0f61acb89ed9861ec996be4f2b38 upstream. nfs4_retry_setlk() sets the task's state to TASK_INTERRUPTIBLE within the same region protected by the

[PATCH 4.12 28/31] isdn/i4l: fix buffer overflow

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Annie Cherkaev commit 9f5af546e6acc30f075828cb58c7f09665033967 upstream. This fixes a potential buffer overflow in isdn_net.c caused by an unbounded strcpy. [ ISDN

[PATCH 4.12 28/31] isdn/i4l: fix buffer overflow

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Annie Cherkaev commit 9f5af546e6acc30f075828cb58c7f09665033967 upstream. This fixes a potential buffer overflow in isdn_net.c caused by an unbounded strcpy. [ ISDN seems to be effectively

[PATCH 4.12 12/31] scripts/dtc: dtx_diff - update include dts paths to match build

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Frank Rowand commit b4b201d88b7c9b3c6acdd03f9adec0c9857548ce upstream. Update the cpp include flags for compiling device tree dts files to match the changes made to the

[PATCH 4.12 13/31] crypto: brcm - Fix SHA3-512 algorithm failure

4.12-stable review patch. If anyone has any objections, please let me know. -- From: raveendra padasalagi commit a7e6e5d8b221e57fed9fda6ec81153fda773c073 upstream. In Broadcom SPU driver, due to missing break statement in spu2_hash_xlate()

[PATCH 4.12 12/31] scripts/dtc: dtx_diff - update include dts paths to match build

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Frank Rowand commit b4b201d88b7c9b3c6acdd03f9adec0c9857548ce upstream. Update the cpp include flags for compiling device tree dts files to match the changes made to the kernel build process

[PATCH 4.12 13/31] crypto: brcm - Fix SHA3-512 algorithm failure

4.12-stable review patch. If anyone has any objections, please let me know. -- From: raveendra padasalagi commit a7e6e5d8b221e57fed9fda6ec81153fda773c073 upstream. In Broadcom SPU driver, due to missing break statement in spu2_hash_xlate() while mapping SPU2 equivalent

[PATCH 4.12 15/31] crypto: authencesn - Fix digest_null crash

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 41cdf7a45389e01991ee31e3301ed83cb3e3f7dc upstream. When authencesn is used together with digest_null a crash will occur on the decrypt path.

[PATCH 4.12 15/31] crypto: authencesn - Fix digest_null crash

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 41cdf7a45389e01991ee31e3301ed83cb3e3f7dc upstream. When authencesn is used together with digest_null a crash will occur on the decrypt path. This is because normally we

[PATCH 4.12 14/31] crypto: brcm - remove BCM_PDC_MBOX dependency in Kconfig

4.12-stable review patch. If anyone has any objections, please let me know. -- From: raveendra padasalagi commit efc856edfd66acc5da34fec92d7feca6fd0f9add upstream. SPU driver is dependent on generic MAILBOX API's to communicate with

[PATCH 4.12 23/31] drm/vmwgfx: Fix gcc-7.1.1 warning

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit fcfffdd8f98ac305285dca568b5065ef86be6458 upstream. The current code does not look correct, and the reason for it is probably lost. Since this now

[PATCH 4.12 14/31] crypto: brcm - remove BCM_PDC_MBOX dependency in Kconfig

4.12-stable review patch. If anyone has any objections, please let me know. -- From: raveendra padasalagi commit efc856edfd66acc5da34fec92d7feca6fd0f9add upstream. SPU driver is dependent on generic MAILBOX API's to communicate with underlying DMA engine driver. So this

[PATCH 4.12 23/31] drm/vmwgfx: Fix gcc-7.1.1 warning

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit fcfffdd8f98ac305285dca568b5065ef86be6458 upstream. The current code does not look correct, and the reason for it is probably lost. Since this now generates a compiler

[PATCH 4.12 18/31] dm integrity: fix inefficient allocation of journal space

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 9dd59727dbc21d33a9add4c5b308a5775cd5a6ef upstream. When using a block size greater than 512 bytes, the dm-integrity target allocates journal space

[PATCH 4.12 18/31] dm integrity: fix inefficient allocation of journal space

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 9dd59727dbc21d33a9add4c5b308a5775cd5a6ef upstream. When using a block size greater than 512 bytes, the dm-integrity target allocates journal space inefficiently. It

[PATCH 4.12 17/31] KVM: PPC: Book3S HV: Fix host crash on changing HPT size

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit ef42719814db06fdfa26cd7566de0b64de173320 upstream. Commit f98a8bf9ee20 ("KVM: PPC: Book3S HV: Allow KVM_PPC_ALLOCATE_HTAB ioctl() to change HPT size",

[PATCH 4.12 17/31] KVM: PPC: Book3S HV: Fix host crash on changing HPT size

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit ef42719814db06fdfa26cd7566de0b64de173320 upstream. Commit f98a8bf9ee20 ("KVM: PPC: Book3S HV: Allow KVM_PPC_ALLOCATE_HTAB ioctl() to change HPT size", 2016-12-20)

[PATCH 4.12 16/31] KVM: PPC: Book3S HV: Enable TM before accessing TM registers

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit e47057151422a67ce08747176fa21cb3b526a2c9 upstream. Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state properly", 2017-06-15)

[PATCH 4.12 16/31] KVM: PPC: Book3S HV: Enable TM before accessing TM registers

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit e47057151422a67ce08747176fa21cb3b526a2c9 upstream. Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state properly", 2017-06-15) added code to read

[PATCH 4.12 20/31] md: remove idx from struct resync_pages

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit 022e510fcbda79183fd2cdc01abb01b4be80d03f upstream. bio_add_page() won't fail for resync bio, and the page index for each bio is same, so remove it. More

[PATCH 4.12 09/31] mmc: sunxi: Keep default timing phase settings for new timing mode

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 26cb2be4c7c42644ccd147c786edb9006300ee56 upstream. The register for the "new timing mode" also has bit fields for setting output and sample timing phases.

[PATCH 4.12 20/31] md: remove idx from struct resync_pages

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit 022e510fcbda79183fd2cdc01abb01b4be80d03f upstream. bio_add_page() won't fail for resync bio, and the page index for each bio is same, so remove it. More importantly the 'idx'

[PATCH 4.12 09/31] mmc: sunxi: Keep default timing phase settings for new timing mode

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 26cb2be4c7c42644ccd147c786edb9006300ee56 upstream. The register for the "new timing mode" also has bit fields for setting output and sample timing phases. According to

[PATCH 4.12 29/31] ipmi/watchdog: fix watchdog timeout set on reboot

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Valentin Vidic commit 860f01e96981a68553f3ca49f574ff14fe955e72 upstream. systemd by default starts watchdog on reboot and sets the timer to

[PATCH 4.12 29/31] ipmi/watchdog: fix watchdog timeout set on reboot

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Valentin Vidic commit 860f01e96981a68553f3ca49f574ff14fe955e72 upstream. systemd by default starts watchdog on reboot and sets the timer to ShutdownWatchdogSec=10min. Reboot handler in

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