[ANNOUNCE] 4.4.30-rt41

Dear RT Folks, I'm pleased to announce the 4.4.30-rt41 stable release. This release is just an update to the new stable 4.4.30 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 4.4.30-rt41

Dear RT Folks, I'm pleased to announce the 4.4.30-rt41 stable release. This release is just an update to the new stable 4.4.30 version and no RT specific changes have been made. You can get this release via the git tree at:

[PATCH] pinctrl: vt8500: make bool drivers explicitly non-modular

None of the Kconfigs for any of these drivers are tristate, meaning that they currently are not being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading the drivers there is no doubt they are builtin-only. All drivers get the exact same

[PATCH] pinctrl: vt8500: make bool drivers explicitly non-modular

None of the Kconfigs for any of these drivers are tristate, meaning that they currently are not being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading the drivers there is no doubt they are builtin-only. All drivers get the exact same

RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Wed, Nov 9 2016, 04:36 PM, Simon Guinot wrote: > On Wed, Nov 09, 2016 at 04:20:00PM +0200, Amir Levy wrote: > > This driver enables Thunderbolt Networking on non-Apple platforms > > running Linux. > > > > Thunderbolt Networking provides peer-to-peer connections to transfer > > files between

RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Wed, Nov 9 2016, 04:36 PM, Simon Guinot wrote: > On Wed, Nov 09, 2016 at 04:20:00PM +0200, Amir Levy wrote: > > This driver enables Thunderbolt Networking on non-Apple platforms > > running Linux. > > > > Thunderbolt Networking provides peer-to-peer connections to transfer > > files between

[PATCH v4] USB hub_probe: rework ugly goto-into-compound-statement

Rework smelling code (goto inside compound statement). Perhaps this is legacy. Anyway such code is not appropriate for Linux kernel. Changes since v3: fix typo Changes since v2: extract the code to static function Changes since v1: fix spaces instead of tab, add missing 'Signed-off-by'

[PATCH v4] USB hub_probe: rework ugly goto-into-compound-statement

Rework smelling code (goto inside compound statement). Perhaps this is legacy. Anyway such code is not appropriate for Linux kernel. Changes since v3: fix typo Changes since v2: extract the code to static function Changes since v1: fix spaces instead of tab, add missing 'Signed-off-by'

Re: [PATCH v7 07/16] drivers: acpi: implement acpi_dma_configure

On 09/11/16 14:19, Lorenzo Pieralisi wrote: > On DT based systems, the of_dma_configure() API implements DMA > configuration for a given device. On ACPI systems an API equivalent to > of_dma_configure() is missing which implies that it is currently not > possible to set-up DMA operations for

Re: [PATCH v7 07/16] drivers: acpi: implement acpi_dma_configure

On 09/11/16 14:19, Lorenzo Pieralisi wrote: > On DT based systems, the of_dma_configure() API implements DMA > configuration for a given device. On ACPI systems an API equivalent to > of_dma_configure() is missing which implies that it is currently not > possible to set-up DMA operations for

[PATCH] x86/cpuid: Deal with broken firmware once more

Both ACPI and MP specifications require that the APIC id in the respective tables must be the same as the APIC id in CPUID. The kernel retrieves the physical package id from the APIC id during the ACPI/MP table scan and builds the physical to logical package map. There exist Virtualbox and Xen

[PATCH] x86/cpuid: Deal with broken firmware once more

Both ACPI and MP specifications require that the APIC id in the respective tables must be the same as the APIC id in CPUID. The kernel retrieves the physical package id from the APIC id during the ACPI/MP table scan and builds the physical to logical package map. There exist Virtualbox and Xen

Re: [PATCH 22/25] x86/mcheck: Do the init in one place

On Wed, Nov 09, 2016 at 03:22:21PM +0100, Sebastian Andrzej Siewior wrote: > I want to get rid of non-symmetrical part and the arch hook which should > be part of the hp notifier itself. I wouldn't be too much afraid about > the when point in time when the notifier runs: It is the *first* >

Re: [PATCH 22/25] x86/mcheck: Do the init in one place

On Wed, Nov 09, 2016 at 03:22:21PM +0100, Sebastian Andrzej Siewior wrote: > I want to get rid of non-symmetrical part and the arch hook which should > be part of the hp notifier itself. I wouldn't be too much afraid about > the when point in time when the notifier runs: It is the *first* >

Re: [PATCH] drbd: Fix kernel_sendmsg() usage

On Tue, Nov 08, 2016 at 09:52:04AM -0700, Jens Axboe wrote: > > > This should go into 4.9, > > > and into all stable branches since and including v4.0, > > > which is the first to contain the exposing change. > > > > > > It is correct for all stable branches older than that as well > > > (which

Re: [PATCH] drbd: Fix kernel_sendmsg() usage

On Tue, Nov 08, 2016 at 09:52:04AM -0700, Jens Axboe wrote: > > > This should go into 4.9, > > > and into all stable branches since and including v4.0, > > > which is the first to contain the exposing change. > > > > > > It is correct for all stable branches older than that as well > > > (which

Re: [PATCH] pinctrl: single: check for any error when getting rows

* Axel Haslam [161109 07:19]: > pinctrl_count_index_with_args returns -ENOENT not > -EINVAL. The return check would pass, and we would > try to kzalloc with a negative error size throwing > a warning. > > Instead of checking for -EINVAL specifically, lets > check for any

Re: [PATCH] pinctrl: single: check for any error when getting rows

* Axel Haslam [161109 07:19]: > pinctrl_count_index_with_args returns -ENOENT not > -EINVAL. The return check would pass, and we would > try to kzalloc with a negative error size throwing > a warning. > > Instead of checking for -EINVAL specifically, lets > check for any error and avoid negative

Re: [PATCH v2 0/2] pinctrl: single: fixes for davinci

* Axel Haslam [161109 07:54]: > After recent pinctl patches we see a warning when booting davinci > due to a bad memory allocation: > > [ cut here ] > WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:3511 > __alloc_pages_nodemask+0x16c/0xb18 > Modules

Re: [PATCH v2 0/2] pinctrl: single: fixes for davinci

* Axel Haslam [161109 07:54]: > After recent pinctl patches we see a warning when booting davinci > due to a bad memory allocation: > > [ cut here ] > WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:3511 > __alloc_pages_nodemask+0x16c/0xb18 > Modules linked in: > CPU: 0 PID: 1

Re: [RFC v3 1/6] Track the active utilisation

On Tue, 8 Nov 2016 20:02:29 + Juri Lelli wrote: [...] > > > So, it actually matters for next patch, > > > not here. But, maybe we want to do things clean from start? > > You mean, because patch 2/6 adds > > + if (hrtimer_active(>dl.inactive_timer)) { > > +

Re: [RFC v3 1/6] Track the active utilisation

On Tue, 8 Nov 2016 20:02:29 + Juri Lelli wrote: [...] > > > So, it actually matters for next patch, > > > not here. But, maybe we want to do things clean from start? > > You mean, because patch 2/6 adds > > + if (hrtimer_active(>dl.inactive_timer)) { > > +

Re: [PATCH 4/6 v7] sched: propagate load during synchronous attach/detach

On 9 November 2016 at 16:03, Peter Zijlstra wrote: > On Tue, Nov 08, 2016 at 10:53:45AM +0100, Vincent Guittot wrote: >> When a task moves from/to a cfs_rq, we set a flag which is then used to >> propagate the change at parent level (sched_entity and cfs_rq) during >> next

Re: [PATCH 4/6 v7] sched: propagate load during synchronous attach/detach

On 9 November 2016 at 16:03, Peter Zijlstra wrote: > On Tue, Nov 08, 2016 at 10:53:45AM +0100, Vincent Guittot wrote: >> When a task moves from/to a cfs_rq, we set a flag which is then used to >> propagate the change at parent level (sched_entity and cfs_rq) during >> next update. If the cfs_rq

Re: [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue

On Wed, 2016-11-09 at 15:08 +, Trond Myklebust wrote: > On Wed, 2016-11-09 at 08:18 -0500, Jeff Layton wrote: > > > > On Tue, 2016-11-08 at 20:27 -0500, J. Bruce Fields wrote: > > > > > > > > > On Tue, Nov 08, 2016 at 05:52:21PM -0500, Tejun Heo wrote: > > > > > > > > > > > > > > > >

Re: [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue

On Wed, 2016-11-09 at 15:08 +, Trond Myklebust wrote: > On Wed, 2016-11-09 at 08:18 -0500, Jeff Layton wrote: > > > > On Tue, 2016-11-08 at 20:27 -0500, J. Bruce Fields wrote: > > > > > > > > > On Tue, Nov 08, 2016 at 05:52:21PM -0500, Tejun Heo wrote: > > > > > > > > > > > > > > > >

Re: [GIT PULL] kvm/page_track changes for i915 KVMGT

On 09/11/2016 16:15, Daniel Vetter wrote: > On Wed, Nov 09, 2016 at 03:25:19PM +0100, Paolo Bonzini wrote: >> Daniel, >> >> The following changes since commit d9092f52d7e61dd1557f2db2400ddb430e85937e: >> >> kvm: x86: Check memopp before dereference (CVE-2016-8630) (2016-11-02 >> 21:31:53

Re: [GIT PULL] kvm/page_track changes for i915 KVMGT

On 09/11/2016 16:15, Daniel Vetter wrote: > On Wed, Nov 09, 2016 at 03:25:19PM +0100, Paolo Bonzini wrote: >> Daniel, >> >> The following changes since commit d9092f52d7e61dd1557f2db2400ddb430e85937e: >> >> kvm: x86: Check memopp before dereference (CVE-2016-8630) (2016-11-02 >> 21:31:53

Re: [GIT PULL] kvm/page_track changes for i915 KVMGT

On Wed, Nov 09, 2016 at 03:25:19PM +0100, Paolo Bonzini wrote: > Daniel, > > The following changes since commit d9092f52d7e61dd1557f2db2400ddb430e85937e: > > kvm: x86: Check memopp before dereference (CVE-2016-8630) (2016-11-02 > 21:31:53 +0100) > > are available in the git repository at: >

Re: [GIT PULL] kvm/page_track changes for i915 KVMGT

On Wed, Nov 09, 2016 at 03:25:19PM +0100, Paolo Bonzini wrote: > Daniel, > > The following changes since commit d9092f52d7e61dd1557f2db2400ddb430e85937e: > > kvm: x86: Check memopp before dereference (CVE-2016-8630) (2016-11-02 > 21:31:53 +0100) > > are available in the git repository at: >

Re: support for partial irq affinity assignment V3

On Wed, Nov 09, 2016 at 08:51:35AM +0100, Thomas Gleixner wrote: > It's available from > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-block > > for you to pull into the block tree so you can apply the block changes. I don't actually need them in the block tree, but in

Re: [PATCH v4 8/8] iio: envelope-detector: ADC driver based on a DAC and a comparator

On Wed, 9 Nov 2016, Peter Rosin wrote: > On 2016-11-08 22:47, Thomas Gleixner wrote: > > I don't think you need extra race handling with that, but I might be wrong > > as usual. > > There's obviously no way to determine which of the timeout or the > interrupt that happens first without some race

Re: support for partial irq affinity assignment V3

On Wed, 9 Nov 2016, Christoph Hellwig wrote: > On Wed, Nov 09, 2016 at 08:51:35AM +0100, Thomas Gleixner wrote: > > It's available from > > > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-block > > > > for you to pull into the block tree so you can apply the block

Re: support for partial irq affinity assignment V3

On Wed, Nov 09, 2016 at 08:51:35AM +0100, Thomas Gleixner wrote: > It's available from > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-block > > for you to pull into the block tree so you can apply the block changes. I don't actually need them in the block tree, but in

Re: [PATCH v4 8/8] iio: envelope-detector: ADC driver based on a DAC and a comparator

On Wed, 9 Nov 2016, Peter Rosin wrote: > On 2016-11-08 22:47, Thomas Gleixner wrote: > > I don't think you need extra race handling with that, but I might be wrong > > as usual. > > There's obviously no way to determine which of the timeout or the > interrupt that happens first without some race

Re: support for partial irq affinity assignment V3

On Wed, 9 Nov 2016, Christoph Hellwig wrote: > On Wed, Nov 09, 2016 at 08:51:35AM +0100, Thomas Gleixner wrote: > > It's available from > > > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-block > > > > for you to pull into the block tree so you can apply the block

Re: [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue

On Wed, 2016-11-09 at 08:18 -0500, Jeff Layton wrote: > On Tue, 2016-11-08 at 20:27 -0500, J. Bruce Fields wrote: > > > > On Tue, Nov 08, 2016 at 05:52:21PM -0500, Tejun Heo wrote: > > > > > > > > > Hello, Bruce. > > > > > > On Tue, Nov 08, 2016 at 04:39:11PM -0500, J. Bruce Fields wrote: > >

Applied "spi: s3c64xx: Allow driver to build if COMPILE_TEST is enabled" to the spi tree

The patch spi: s3c64xx: Allow driver to build if COMPILE_TEST is enabled has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Re: [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue

On Wed, 2016-11-09 at 08:18 -0500, Jeff Layton wrote: > On Tue, 2016-11-08 at 20:27 -0500, J. Bruce Fields wrote: > > > > On Tue, Nov 08, 2016 at 05:52:21PM -0500, Tejun Heo wrote: > > > > > > > > > Hello, Bruce. > > > > > > On Tue, Nov 08, 2016 at 04:39:11PM -0500, J. Bruce Fields wrote: > >

Applied "spi: s3c64xx: Allow driver to build if COMPILE_TEST is enabled" to the spi tree

The patch spi: s3c64xx: Allow driver to build if COMPILE_TEST is enabled has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: sun4i-codec: Add support for A31 ADC capture path" to the asoc tree

The patch ASoC: sun4i-codec: Add support for A31 ADC capture path has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: [PATCH 1/2] skd: fix msix error handling

Thanks Arnd, this looks fine: Reviewed-by: Christoph Hellwig

Re: [PATCH v4 2/2] iommu/exynos: Add proper runtime pm support

Hi Luis, On 2016-11-08 23:14, Luis R. Rodriguez wrote: On Mon, Oct 10, 2016 at 03:32:06PM +0200, Marek Szyprowski wrote: Hi Luis On 2016-10-06 19:37, Luis R. Rodriguez wrote: On Thu, Sep 29, 2016 at 10:12:31AM +0200, Marek Szyprowski wrote: This patch uses recently introduced device links

Re: [PATCH 1/2] skd: fix msix error handling

Thanks Arnd, this looks fine: Reviewed-by: Christoph Hellwig

Re: [PATCH v4 2/2] iommu/exynos: Add proper runtime pm support

Hi Luis, On 2016-11-08 23:14, Luis R. Rodriguez wrote: On Mon, Oct 10, 2016 at 03:32:06PM +0200, Marek Szyprowski wrote: Hi Luis On 2016-10-06 19:37, Luis R. Rodriguez wrote: On Thu, Sep 29, 2016 at 10:12:31AM +0200, Marek Szyprowski wrote: This patch uses recently introduced device links

Applied "ASoC: sun4i-codec: Add support for A31 ADC capture path" to the asoc tree

The patch ASoC: sun4i-codec: Add support for A31 ADC capture path has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: [PATCH] wireless: fix bogus maybe-uninitialized warning

On Wednesday, November 9, 2016 9:10:46 AM CET Johannes Berg wrote: > > > Ideally we prefer that drivers/net/wireless and net/wireless changes > > are > > split into different patches as they get applied to different trees. Ok, good to know. I had split out the drivers/staging changes, but wasn't

Re: [PATCH] wireless: fix bogus maybe-uninitialized warning

On Wednesday, November 9, 2016 9:10:46 AM CET Johannes Berg wrote: > > > Ideally we prefer that drivers/net/wireless and net/wireless changes > > are > > split into different patches as they get applied to different trees. Ok, good to know. I had split out the drivers/staging changes, but wasn't

Applied "ASoC: sunxi: i2s: Implement set_sysclk" to the asoc tree

The patch ASoC: sunxi: i2s: Implement set_sysclk has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [PATCH] mfd: tps65217: Drop call to irq_set_parent()

On Wed, 26 Oct 2016, Guenter Roeck wrote: > On 10/26/2016 05:58 AM, Lee Jones wrote: > > On Wed, 26 Oct 2016, Thomas Gleixner wrote: > > > > > On Wed, 26 Oct 2016, Lee Jones wrote: > > > > On Fri, 14 Oct 2016, Guenter Roeck wrote: > > > > > > > > > The call to irq_set_parent() causes the

Applied "ASoC: sunxi: i2s: Implement set_sysclk" to the asoc tree

The patch ASoC: sunxi: i2s: Implement set_sysclk has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [PATCH] mfd: tps65217: Drop call to irq_set_parent()

On Wed, 26 Oct 2016, Guenter Roeck wrote: > On 10/26/2016 05:58 AM, Lee Jones wrote: > > On Wed, 26 Oct 2016, Thomas Gleixner wrote: > > > > > On Wed, 26 Oct 2016, Lee Jones wrote: > > > > On Fri, 14 Oct 2016, Guenter Roeck wrote: > > > > > > > > > The call to irq_set_parent() causes the

Applied "ASoC: wm8978: Adjust clock indices so that simple card works" to the asoc tree

The patch ASoC: wm8978: Adjust clock indices so that simple card works has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: lpass-platform: initialize dma channel number" to the asoc tree

The patch ASoC: lpass-platform: initialize dma channel number has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: wm8978: Adjust clock indices so that simple card works" to the asoc tree

The patch ASoC: wm8978: Adjust clock indices so that simple card works has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: lpass-platform: initialize dma channel number" to the asoc tree

The patch ASoC: lpass-platform: initialize dma channel number has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: atmel: use managed resource for gpio chip select" to the spi tree

The patch spi: atmel: use managed resource for gpio chip select has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: atmel: use managed resource for gpio chip select" to the spi tree

The patch spi: atmel: use managed resource for gpio chip select has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Re: [PATCH 4/6 v7] sched: propagate load during synchronous attach/detach

On Tue, Nov 08, 2016 at 10:53:45AM +0100, Vincent Guittot wrote: > When a task moves from/to a cfs_rq, we set a flag which is then used to > propagate the change at parent level (sched_entity and cfs_rq) during > next update. If the cfs_rq is throttled, the flag will stay pending until > the

Re: [PATCH 4/6 v7] sched: propagate load during synchronous attach/detach

On Tue, Nov 08, 2016 at 10:53:45AM +0100, Vincent Guittot wrote: > When a task moves from/to a cfs_rq, we set a flag which is then used to > propagate the change at parent level (sched_entity and cfs_rq) during > next update. If the cfs_rq is throttled, the flag will stay pending until > the

Re: [PATCH 4.8 022/138] thermal/powerclamp: correct cpu support check

On Wed, 9 Nov 2016 11:45:05 +0100 Greg Kroah-Hartman wrote: > 4.8-stable review patch. If anyone has any objections, please let me > know. > I just realized that this patch would prevent module auto loading since we don't have device id table. I will send out this

Re: [PATCH 4.8 022/138] thermal/powerclamp: correct cpu support check

On Wed, 9 Nov 2016 11:45:05 +0100 Greg Kroah-Hartman wrote: > 4.8-stable review patch. If anyone has any objections, please let me > know. > I just realized that this patch would prevent module auto loading since we don't have device id table. I will send out this patch in a minute. So we

[PATCH] thermal/powerclamp: add back module device table

Commit 3105f234e0aba43e44e277c20f9b32ee8add43d4 replaced module cpu id table with a cpu feature check, which is logically correct. But we need the module device table to allow module auto loading. --- drivers/thermal/intel_powerclamp.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-)

[PATCH] thermal/powerclamp: add back module device table

Commit 3105f234e0aba43e44e277c20f9b32ee8add43d4 replaced module cpu id table with a cpu feature check, which is logically correct. But we need the module device table to allow module auto loading. --- drivers/thermal/intel_powerclamp.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-)

Applied "spi: rspi: avoid uninitialized variable access" to the spi tree

The patch spi: rspi: avoid uninitialized variable access has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: rspi: avoid uninitialized variable access" to the spi tree

The patch spi: rspi: avoid uninitialized variable access has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH v4 8/8] iio: envelope-detector: ADC driver based on a DAC and a comparator

On 2016-11-08 22:47, Thomas Gleixner wrote: > On Tue, 8 Nov 2016, Peter Rosin wrote: >> So, to sum up, in order for this to work with threaded oneshot >> interrupts, I still need to either keep the enable/sync/enable-dance >> or tweak the irq core to handle my case better. The only gain would >>

Re: [PATCH v4 8/8] iio: envelope-detector: ADC driver based on a DAC and a comparator

On 2016-11-08 22:47, Thomas Gleixner wrote: > On Tue, 8 Nov 2016, Peter Rosin wrote: >> So, to sum up, in order for this to work with threaded oneshot >> interrupts, I still need to either keep the enable/sync/enable-dance >> or tweak the irq core to handle my case better. The only gain would >>

Applied "ASoC: sun4i-codec: Add support for optional reset control to quirks" to the asoc tree

The patch ASoC: sun4i-codec: Add support for optional reset control to quirks has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "ASoC: sun4i-codec: Add support for optional reset control to quirks" to the asoc tree

The patch ASoC: sun4i-codec: Add support for optional reset control to quirks has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "ASoC: fsl: fix fsl_spdif.c build errors" to the asoc tree

The patch ASoC: fsl: fix fsl_spdif.c build errors has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "ASoC: fsl: fix fsl_spdif.c build errors" to the asoc tree

The patch ASoC: fsl: fix fsl_spdif.c build errors has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple regulators per device

On Wed, Oct 26, 2016 at 12:02:56PM +0530, Viresh Kumar wrote: > + Entries for multiple regulators shall be provided in the same field > separated > + by angular brackets <>. The OPP binding doesn't provide any provisions to > + relate the values to their power supplies or the order in which

Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple regulators per device

On Wed, Oct 26, 2016 at 12:02:56PM +0530, Viresh Kumar wrote: > + Entries for multiple regulators shall be provided in the same field > separated > + by angular brackets <>. The OPP binding doesn't provide any provisions to > + relate the values to their power supplies or the order in which

[PATCH v2 2/2] pinctrl: single: search for the bits property when parsing bits

The pcs_parse_bits_in_pinctrl_entry function should search for the "pinctrl-single,bits" and not "pinctrl-single,pins" Signed-off-by: Axel Haslam --- drivers/pinctrl/pinctrl-single.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 2/2] pinctrl: single: search for the bits property when parsing bits

The pcs_parse_bits_in_pinctrl_entry function should search for the "pinctrl-single,bits" and not "pinctrl-single,pins" Signed-off-by: Axel Haslam --- drivers/pinctrl/pinctrl-single.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinctrl-single.c

[PATCH v2 0/2] pinctrl: single: fixes for davinci

After recent pinctl patches we see a warning when booting davinci due to a bad memory allocation: [ cut here ] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:3511 __alloc_pages_nodemask+0x16c/0xb18 Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted

[PATCH v2 0/2] pinctrl: single: fixes for davinci

After recent pinctl patches we see a warning when booting davinci due to a bad memory allocation: [ cut here ] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:3511 __alloc_pages_nodemask+0x16c/0xb18 Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted

[PATCH v2 1/2] pinctrl: single: check for any error when getting rows

pinctrl_count_index_with_args returns -ENOENT not -EINVAL. The return check would pass, and we would try to kzalloc with a negative error size throwing a warning. Instead of checking for -EINVAL specifically, lets check for any error and avoid negative size allocations. Signed-off-by: Axel

[PATCH v2 1/2] pinctrl: single: check for any error when getting rows

pinctrl_count_index_with_args returns -ENOENT not -EINVAL. The return check would pass, and we would try to kzalloc with a negative error size throwing a warning. Instead of checking for -EINVAL specifically, lets check for any error and avoid negative size allocations. Signed-off-by: Axel

RE: [PATCH V5 2/3] ARM64 LPC: Add missing range exception for special ISA

> -Original Message- > From: One Thousand Gnomes [mailto:gno...@lxorguk.ukuu.org.uk] > Sent: 09 November 2016 13:55 > To: Arnd Bergmann > Cc: Mark Rutland; Yuanzhichang; catalin.mari...@arm.com; > will.dea...@arm.com; robh...@kernel.org; bhelg...@google.com; > o...@lixom.net;

RE: [PATCH V5 2/3] ARM64 LPC: Add missing range exception for special ISA

> -Original Message- > From: One Thousand Gnomes [mailto:gno...@lxorguk.ukuu.org.uk] > Sent: 09 November 2016 13:55 > To: Arnd Bergmann > Cc: Mark Rutland; Yuanzhichang; catalin.mari...@arm.com; > will.dea...@arm.com; robh...@kernel.org; bhelg...@google.com; > o...@lixom.net;

Re: [PATCH] hwmon: (scpi) Fix module autoload

On 11/07/2016 12:31 PM, Javier Martinez Canillas wrote: If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the

Re: [PATCH] hwmon: (scpi) Fix module autoload

On 11/07/2016 12:31 PM, Javier Martinez Canillas wrote: If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the

Re: [PATCH v2] video: backlight: pwm_bl: Initialize fb_bl_on[x] and use_count during pwm_backlight_probe()

On Tue, 08 Nov 2016, Lukasz Majewski wrote: > Dear All, > > > The commit a55944ca82d2 ("backlight: update bd state & fb_blank > > properties when necessary") has posed some extra restrictions on > > blanking and unblanking frame buffer device. > > > > Unfortunately, pwm_bl driver's probe did

Re: [PATCH v2] video: backlight: pwm_bl: Initialize fb_bl_on[x] and use_count during pwm_backlight_probe()

On Tue, 08 Nov 2016, Lukasz Majewski wrote: > Dear All, > > > The commit a55944ca82d2 ("backlight: update bd state & fb_blank > > properties when necessary") has posed some extra restrictions on > > blanking and unblanking frame buffer device. > > > > Unfortunately, pwm_bl driver's probe did

Re: [watchdog] watchdog: mei_wdt: request stop on reboot to prevent false positive event

On 11/08/2016 07:55 AM, Tomas Winkler wrote: From: Alexander Usyskin Systemd on reboot enables shutdown watchdog that leaves the watchdog device open to ensure that even if power down process get stuck the platform reboots nonetheless. The iamt_wdt is an alarm-only

Re: [watchdog] watchdog: mei_wdt: request stop on reboot to prevent false positive event

On 11/08/2016 07:55 AM, Tomas Winkler wrote: From: Alexander Usyskin Systemd on reboot enables shutdown watchdog that leaves the watchdog device open to ensure that even if power down process get stuck the platform reboots nonetheless. The iamt_wdt is an alarm-only watchdog and can't reboot

Re: [PATCH 3/4] perf hist browser: Fix column indentation on --hierarchy

Em Tue, Nov 08, 2016 at 10:08:32PM +0900, Namhyung Kim escreveu: > When horizontall scrolling is used in hierarchy mode, the the right most > column has unnecessary indentation. Actually it's needed only if some > of left (overhead) columns were shown. I see, here is the fix, thanks, testing it

Re: [PATCH 3/6] net: mdio-mux: Add MDIO mux driver for NSP SoC

> +#define NSP_MDIO_EXT_BUS_START_ADDR 16 > +#define NSP_MDIO_EXT_SELECT_BIT BIT(9) > + > +static int mdio_mux_nsp_switch_fn(int current_child, int desired_child, > + void *priv) > +{ > + struct nsp_mdiomux_desc *md = priv; > +

Re: [PATCH 3/4] perf hist browser: Fix column indentation on --hierarchy

Em Tue, Nov 08, 2016 at 10:08:32PM +0900, Namhyung Kim escreveu: > When horizontall scrolling is used in hierarchy mode, the the right most > column has unnecessary indentation. Actually it's needed only if some > of left (overhead) columns were shown. I see, here is the fix, thanks, testing it

Re: [PATCH 3/6] net: mdio-mux: Add MDIO mux driver for NSP SoC

> +#define NSP_MDIO_EXT_BUS_START_ADDR 16 > +#define NSP_MDIO_EXT_SELECT_BIT BIT(9) > + > +static int mdio_mux_nsp_switch_fn(int current_child, int desired_child, > + void *priv) > +{ > + struct nsp_mdiomux_desc *md = priv; > +

Re: [PATCH] soc: qcom: Add SoC info driver

Hi Bjorn, On Wed, Nov 2, 2016 at 5:28 PM, Bjorn Andersson wrote: > On Wed 26 Oct 07:05 PDT 2016, Arnd Bergmann wrote: >> On Wednesday, October 26, 2016 7:20:42 PM CEST Imran Khan wrote: >> > On 10/26/2016 2:19 AM, Arnd Bergmann wrote: >> > > On Tuesday, October 25,

Re: [PATCH v7 06/16] drivers: iommu: arm-smmu-v3: convert struct device of_node to fwnode usage

On 09/11/16 14:19, Lorenzo Pieralisi wrote: > Current ARM SMMU v3 driver rely on the struct device.of_node pointer for > device look-up and iommu_ops retrieval. > > In preparation for ACPI probing enablement, convert the driver to use > the struct device.fwnode member for device and iommu_ops

Re: [PATCH] soc: qcom: Add SoC info driver

Hi Bjorn, On Wed, Nov 2, 2016 at 5:28 PM, Bjorn Andersson wrote: > On Wed 26 Oct 07:05 PDT 2016, Arnd Bergmann wrote: >> On Wednesday, October 26, 2016 7:20:42 PM CEST Imran Khan wrote: >> > On 10/26/2016 2:19 AM, Arnd Bergmann wrote: >> > > On Tuesday, October 25, 2016 3:23:34 PM CEST Imran

Re: [PATCH v7 06/16] drivers: iommu: arm-smmu-v3: convert struct device of_node to fwnode usage

On 09/11/16 14:19, Lorenzo Pieralisi wrote: > Current ARM SMMU v3 driver rely on the struct device.of_node pointer for > device look-up and iommu_ops retrieval. > > In preparation for ACPI probing enablement, convert the driver to use > the struct device.fwnode member for device and iommu_ops

Re: [PATCH] perf tools pt: Remove obsolete paragraph in intel-pt.c

Em Wed, Nov 09, 2016 at 04:01:12PM +0200, Adrian Hunter escreveu: > On 09/11/16 15:59, Arnaldo Carvalho de Melo wrote: > > Em Wed, Nov 09, 2016 at 10:14:26AM -0300, Arnaldo Carvalho de Melo escreveu: > > +++ b/tools/perf/Documentation/intel-pt.txt > > @@ -546,6 +546,18 @@ mode by using the

Re: [PATCH] perf tools pt: Remove obsolete paragraph in intel-pt.c

Em Wed, Nov 09, 2016 at 04:01:12PM +0200, Adrian Hunter escreveu: > On 09/11/16 15:59, Arnaldo Carvalho de Melo wrote: > > Em Wed, Nov 09, 2016 at 10:14:26AM -0300, Arnaldo Carvalho de Melo escreveu: > > +++ b/tools/perf/Documentation/intel-pt.txt > > @@ -546,6 +546,18 @@ mode by using the

Re: [PATCH v7 05/16] drivers: iommu: arm-smmu: convert struct device of_node to fwnode usage

On 09/11/16 14:19, Lorenzo Pieralisi wrote: > Current ARM SMMU driver rely on the struct device.of_node pointer for > device look-up and iommu_ops retrieval. > > In preparation for ACPI probing enablement, convert the driver to use > the struct device.fwnode member for device and iommu_ops

Re: [PATCH v7 05/16] drivers: iommu: arm-smmu: convert struct device of_node to fwnode usage

On 09/11/16 14:19, Lorenzo Pieralisi wrote: > Current ARM SMMU driver rely on the struct device.of_node pointer for > device look-up and iommu_ops retrieval. > > In preparation for ACPI probing enablement, convert the driver to use > the struct device.fwnode member for device and iommu_ops

<    6   7   8   9   10   11   12   13   14   15   >