Re: [PATCHv4] arm64: Handle el1 synchronous instruction aborts cleanly

On Mon, Aug 08, 2016 at 05:35:34PM -0700, Laura Abbott wrote: > Executing from a non-executable area gives an ugly message: > > lkdtm: Performing direct entry EXEC_RODATA > lkdtm: attempting ok execution at 084c0e08 > lkdtm: attempting bad execution at 08880700 > Bad mode in

Re: [PATCHv4] arm64: Handle el1 synchronous instruction aborts cleanly

On Mon, Aug 08, 2016 at 05:35:34PM -0700, Laura Abbott wrote: > Executing from a non-executable area gives an ugly message: > > lkdtm: Performing direct entry EXEC_RODATA > lkdtm: attempting ok execution at 084c0e08 > lkdtm: attempting bad execution at 08880700 > Bad mode in

Re: [PATCH 09/20] SEAD3: Probe parallel flash via DT

Hello. On 08/09/2016 03:35 PM, Paul Burton wrote: Probe the system parallel flash using device tree rather than platform code, in order to reduce the amount of the latter. Signed-off-by: Paul Burton --- arch/mips/boot/dts/mti/sead3.dts | 17 +

Re: [PATCH 09/20] SEAD3: Probe parallel flash via DT

Hello. On 08/09/2016 03:35 PM, Paul Burton wrote: Probe the system parallel flash using device tree rather than platform code, in order to reduce the amount of the latter. Signed-off-by: Paul Burton --- arch/mips/boot/dts/mti/sead3.dts | 17 +

Re: [RFC PATCH v7 1/7] Restartable sequences system call

- On Aug 7, 2016, at 7:35 PM, Boqun Feng boqun.f...@gmail.com wrote: > On Sun, Aug 07, 2016 at 03:36:24PM +, Mathieu Desnoyers wrote: >> - On Aug 3, 2016, at 11:45 AM, Boqun Feng boqun.f...@gmail.com wrote: >> >> > On Wed, Aug 03, 2016 at 03:19:40PM +0200, Peter Zijlstra wrote: >> >>

Re: [RFC PATCH v7 1/7] Restartable sequences system call

- On Aug 7, 2016, at 7:35 PM, Boqun Feng boqun.f...@gmail.com wrote: > On Sun, Aug 07, 2016 at 03:36:24PM +, Mathieu Desnoyers wrote: >> - On Aug 3, 2016, at 11:45 AM, Boqun Feng boqun.f...@gmail.com wrote: >> >> > On Wed, Aug 03, 2016 at 03:19:40PM +0200, Peter Zijlstra wrote: >> >>

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On 09/08/16 05:25, John Stultz wrote: ... > So actually no. We usually call irqd_set_trigger_type() but something > still doesn't work. > > Interestingly, just adding irq_set_irq_type(virq, type); to the top of > that block (leaving the rest of the code) also works. Interesting. By saving the

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On 09/08/16 05:25, John Stultz wrote: ... > So actually no. We usually call irqd_set_trigger_type() but something > still doesn't work. > > Interestingly, just adding irq_set_irq_type(virq, type); to the top of > that block (leaving the rest of the code) also works. Interesting. By saving the

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar: > On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: > > Mimi Zohar writes: > > > diff --git a/security/integrity/ima/ima.h > > > b/security/integrity/ima/ima.h > > > index b5728da..84e8d36 100644 > > >

Re: Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree

Hi Mark, [auto build test WARNING on regmap/for-next] [also build test WARNING on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Mark-Brown/Applied-regmap-debugfs-Add

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar: > On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: > > Mimi Zohar writes: > > > diff --git a/security/integrity/ima/ima.h > > > b/security/integrity/ima/ima.h > > > index b5728da..84e8d36 100644 > > > ---

Re: Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree

Hi Mark, [auto build test WARNING on regmap/for-next] [also build test WARNING on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Mark-Brown/Applied-regmap-debugfs-Add

Re: [PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code

On Tuesday 09 Aug 2016 16:17:57 Laurent Pinchart wrote: > On Wednesday 08 Jun 2016 18:12:31 Magnus Damm wrote: > > On Wed, Jun 8, 2016 at 5:48 PM, Laurent Pinchart wrote: > >> On Wednesday 08 Jun 2016 09:04:17 Geert Uytterhoeven wrote: > >>> On Wed, Jun 8, 2016 at 2:18 AM, Laurent Pinchart wrote:

Re: [PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code

On Tuesday 09 Aug 2016 16:17:57 Laurent Pinchart wrote: > On Wednesday 08 Jun 2016 18:12:31 Magnus Damm wrote: > > On Wed, Jun 8, 2016 at 5:48 PM, Laurent Pinchart wrote: > >> On Wednesday 08 Jun 2016 09:04:17 Geert Uytterhoeven wrote: > >>> On Wed, Jun 8, 2016 at 2:18 AM, Laurent Pinchart wrote:

Re: [PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code

Hi Magnus, On Wednesday 08 Jun 2016 18:12:31 Magnus Damm wrote: > On Wed, Jun 8, 2016 at 5:48 PM, Laurent Pinchart wrote: > > On Wednesday 08 Jun 2016 09:04:17 Geert Uytterhoeven wrote: > >> On Wed, Jun 8, 2016 at 2:18 AM, Laurent Pinchart wrote: > --- 0031/drivers/iommu/ipmmu-vmsa.c >

Re: [PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code

Hi Magnus, On Wednesday 08 Jun 2016 18:12:31 Magnus Damm wrote: > On Wed, Jun 8, 2016 at 5:48 PM, Laurent Pinchart wrote: > > On Wednesday 08 Jun 2016 09:04:17 Geert Uytterhoeven wrote: > >> On Wed, Jun 8, 2016 at 2:18 AM, Laurent Pinchart wrote: > --- 0031/drivers/iommu/ipmmu-vmsa.c >

Re: [PATCH] cachefiles: Fix attempt to read i_blocks after deleting file

Hi David, [auto build test ERROR on linus/master] [also build test ERROR on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/David-Howells/cachefiles-Fix-attempt-to-read

Re: [PATCH] cachefiles: Fix attempt to read i_blocks after deleting file

Hi David, [auto build test ERROR on linus/master] [also build test ERROR on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/David-Howells/cachefiles-Fix-attempt-to-read

Re: Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree

Hi Mark, [auto build test ERROR on regmap/for-next] [also build test ERROR on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Mark-Brown/Applied-regmap-debugfs-Add

Re: Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree

Hi Mark, [auto build test ERROR on regmap/for-next] [also build test ERROR on v4.8-rc1 next-20160809] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Mark-Brown/Applied-regmap-debugfs-Add

Re: [PATCH] mfd: altera-a10sr: Make altr_a10sr_regmap_config static const

On Fri, 05 Aug 2016, Axel Lin wrote: > It's only used in this driver and never get modified, make it static const. > > Signed-off-by: Axel Lin > --- > drivers/mfd/altera-a10sr.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied, thanks. > diff --git

Re: [PATCH] mfd: altera-a10sr: Make altr_a10sr_regmap_config static const

On Fri, 05 Aug 2016, Axel Lin wrote: > It's only used in this driver and never get modified, make it static const. > > Signed-off-by: Axel Lin > --- > drivers/mfd/altera-a10sr.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied, thanks. > diff --git a/drivers/mfd/altera-a10sr.c

[PATCHv2] perf-stat: avoid skew when reading events

When we don't have a tracee (i.e. we're attaching to a task or CPU), counters can still be running after our workload finishes, and can still be running as we read their values. As we read events one-by-one, there can be arbitrary skew between values of events, even within a group. This means that

[PATCHv2] perf-stat: avoid skew when reading events

When we don't have a tracee (i.e. we're attaching to a task or CPU), counters can still be running after our workload finishes, and can still be running as we read their values. As we read events one-by-one, there can be arbitrary skew between values of events, even within a group. This means that

Re: [RFC PATCH 0/5] Allwinner MMC firmware clocks implementation

> frequencies in an SoC agnostic manner. The actual clock access can be > put in firmware, which is by definition SoC specific and thus can > be easier and much quicker adapted to support a new SoC. Hmm... what do you mean by "firmware"? Stefan "just a by-stander trying to understand"

Re: [RFC PATCH 0/5] Allwinner MMC firmware clocks implementation

> frequencies in an SoC agnostic manner. The actual clock access can be > put in firmware, which is by definition SoC specific and thus can > be easier and much quicker adapted to support a new SoC. Hmm... what do you mean by "firmware"? Stefan "just a by-stander trying to understand"

tty/serial/8250: use mctrl_gpio helpers - Causes problems on ACPI systems

Hi, I noticed that with v4.8-rc1 serial console of some of our Broxton systems does not work properly anymore. I'm able to see output but input does not work. I bisected it down to commit 4ef03d328769eddbfeca1f1c958fdb181a69c341 ("tty/serial/8250: use mctrl_gpio helpers"). The reason why it

tty/serial/8250: use mctrl_gpio helpers - Causes problems on ACPI systems

Hi, I noticed that with v4.8-rc1 serial console of some of our Broxton systems does not work properly anymore. I'm able to see output but input does not work. I bisected it down to commit 4ef03d328769eddbfeca1f1c958fdb181a69c341 ("tty/serial/8250: use mctrl_gpio helpers"). The reason why it

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: > Mimi Zohar writes: > > > diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h > > index b5728da..84e8d36 100644 > > --- a/security/integrity/ima/ima.h > > +++ b/security/integrity/ima/ima.h

Re: [RFC PATCH V5 0/5] ECAM quirks handling for ARM64 platforms

On 08.08.16 15:05:36, Tomasz Nowicki wrote: > Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and > revision (the ones from standard header of MCFG table). > > Static array is used to keep quirk entries. Each entry consists of > mentioned MCFG IDs along with custom pci_ops

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: > Mimi Zohar writes: > > > diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h > > index b5728da..84e8d36 100644 > > --- a/security/integrity/ima/ima.h > > +++ b/security/integrity/ima/ima.h > > @@ -102,6 +102,13 @@

Re: [RFC PATCH V5 0/5] ECAM quirks handling for ARM64 platforms

On 08.08.16 15:05:36, Tomasz Nowicki wrote: > Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and > revision (the ones from standard header of MCFG table). > > Static array is used to keep quirk entries. Each entry consists of > mentioned MCFG IDs along with custom pci_ops

Re: [PATCH 2/3] fs: befs: check flags field to validate the superblock state

On Tue, Aug 09, 2016 at 01:40:25PM +0100, Luis de Bethencourt wrote: > On 09/08/16 13:32, Salah Triki wrote: > > flags field records the superblock state, so check if it is equal to > > BEFS_DIRTY. > > > > Signed-off-by: Salah Triki > > --- > > fs/befs/super.c | 2 +- > >

Re: [PATCH 2/3] fs: befs: check flags field to validate the superblock state

On Tue, Aug 09, 2016 at 01:40:25PM +0100, Luis de Bethencourt wrote: > On 09/08/16 13:32, Salah Triki wrote: > > flags field records the superblock state, so check if it is equal to > > BEFS_DIRTY. > > > > Signed-off-by: Salah Triki > > --- > > fs/befs/super.c | 2 +- > > 1 file changed, 1

Re: [PATCH v2 2/2] ARM: dts: TS-4900: add basic device tree

On Mon, Aug 01, 2016 at 10:04:53AM -0400, Lucile Quirion wrote: > diff --git a/arch/arm/boot/dts/imx6dl-ts4900.dts > b/arch/arm/boot/dts/imx6dl-ts4900.dts > new file mode 100644 > index 000..909fd5c > --- /dev/null > +++ b/arch/arm/boot/dts/imx6dl-ts4900.dts > +/dts-v1/; > +#include

Re: [PATCH] i2c: don't print error when adding adapter fails

On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote: [...] > diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c > index b126dbaa47e370..d9979da11485ae 100644 > --- a/drivers/i2c/busses/i2c-tegra.c > +++ b/drivers/i2c/busses/i2c-tegra.c > @@ -932,10 +932,8 @@

Re: [Resend][PATCH] x86/power/64: Always create temporary identity mapping correctly

On Tue, 9 Aug 2016, Rafael J. Wysocki wrote: > Here's a list of commits from Thomas that are related to memory randomization. > > 210e7a43fa90 mm: SLUB freelist randomization > 7c00fce98c3e mm: reorganize SLAB freelist randomization > 4ff5308744f5 x86/mm: Do not reference phys addr beyond kernel

Re: [PATCH v2 2/2] ARM: dts: TS-4900: add basic device tree

On Mon, Aug 01, 2016 at 10:04:53AM -0400, Lucile Quirion wrote: > diff --git a/arch/arm/boot/dts/imx6dl-ts4900.dts > b/arch/arm/boot/dts/imx6dl-ts4900.dts > new file mode 100644 > index 000..909fd5c > --- /dev/null > +++ b/arch/arm/boot/dts/imx6dl-ts4900.dts > +/dts-v1/; > +#include

Re: [PATCH] i2c: don't print error when adding adapter fails

On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote: [...] > diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c > index b126dbaa47e370..d9979da11485ae 100644 > --- a/drivers/i2c/busses/i2c-tegra.c > +++ b/drivers/i2c/busses/i2c-tegra.c > @@ -932,10 +932,8 @@

Re: [Resend][PATCH] x86/power/64: Always create temporary identity mapping correctly

On Tue, 9 Aug 2016, Rafael J. Wysocki wrote: > Here's a list of commits from Thomas that are related to memory randomization. > > 210e7a43fa90 mm: SLUB freelist randomization > 7c00fce98c3e mm: reorganize SLAB freelist randomization > 4ff5308744f5 x86/mm: Do not reference phys addr beyond kernel

Re: [PATCH] i2c: don't print error when adding adapter fails

On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote: > The core will do this for us now. > > Signed-off-by: Wolfram Sang > --- > drivers/i2c/busses/i2c-amd756.c | 5 + > drivers/i2c/busses/i2c-at91.c | 2 -- >

Re: [PATCH] i2c: don't print error when adding adapter fails

On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote: > The core will do this for us now. > > Signed-off-by: Wolfram Sang > --- > drivers/i2c/busses/i2c-amd756.c | 5 + > drivers/i2c/busses/i2c-at91.c | 2 -- > drivers/i2c/busses/i2c-axxia.c | 8 +--- >

[PATCH] cachefiles: Fix attempt to read i_blocks after deleting file

An NULL-pointer dereference happens in cachefiles_mark_object_inactive() when it tries to read i_blocks so that it can tell the cachefilesd daemon how much space it's making available. The problem is that cachefiles_drop_object() calls cachefiles_mark_object_inactive() after calling

[PATCH] cachefiles: Fix attempt to read i_blocks after deleting file

An NULL-pointer dereference happens in cachefiles_mark_object_inactive() when it tries to read i_blocks so that it can tell the cachefilesd daemon how much space it's making available. The problem is that cachefiles_drop_object() calls cachefiles_mark_object_inactive() after calling

Re: [PATCH] mfd: syscon: Make use of of_iomap

On Sun, 07 Aug 2016, Andrey Smirnov wrote: > Use of_iomap instead of explicitly calling of_address_to_resource() and > ioremap(). > > Signed-off-by: Andrey Smirnov > --- > drivers/mfd/syscon.c | 7 +-- > 1 file changed, 1 insertion(+), 6 deletions(-) Applied,

Re: [PATCH] mfd: syscon: Make use of of_iomap

On Sun, 07 Aug 2016, Andrey Smirnov wrote: > Use of_iomap instead of explicitly calling of_address_to_resource() and > ioremap(). > > Signed-off-by: Andrey Smirnov > --- > drivers/mfd/syscon.c | 7 +-- > 1 file changed, 1 insertion(+), 6 deletions(-) Applied, thanks. > diff --git

Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close

and as the fuzzing continues I started to get these, a bit worrying. [ 6501.254564] Slab corruption (Tainted: GW ): task_struct start=8800c072e000, len=5760 [ 6501.264971] 010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b jkkk [ 6501.273650] Single bit error

Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close

and as the fuzzing continues I started to get these, a bit worrying. [ 6501.254564] Slab corruption (Tainted: GW ): task_struct start=8800c072e000, len=5760 [ 6501.264971] 010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b jkkk [ 6501.273650] Single bit error

Re: [PATCHv2 3/4] pci: Determine actual VPD size on first access

On 10/02/16 08:04, Bjorn Helgaas wrote: > On Wed, Jan 13, 2016 at 12:25:34PM +0100, Hannes Reinecke wrote: >> PCI-2.2 VPD entries have a maximum size of 32k, but might actually >> be smaller than that. To figure out the actual size one has to read >> the VPD area until the 'end marker' is reached.

Re: [PATCHv2 3/4] pci: Determine actual VPD size on first access

On 10/02/16 08:04, Bjorn Helgaas wrote: > On Wed, Jan 13, 2016 at 12:25:34PM +0100, Hannes Reinecke wrote: >> PCI-2.2 VPD entries have a maximum size of 32k, but might actually >> be smaller than that. To figure out the actual size one has to read >> the VPD area until the 'end marker' is reached.

Re: [PATCH] mfd: wm8350-i2c: make sure the i2c regmap functions are compiled

On Fri, 29 Jul 2016, Uwe Kleine-König wrote: > This fixes a compile failure: > > drivers/built-in.o: In function `wm8350_i2c_probe': > core.c:(.text+0x828b0): undefined reference to `__devm_regmap_init_i2c' > Makefile:953: recipe for target 'vmlinux' failed > > Fixes:

Re: [PATCH] mfd: wm8350-i2c: make sure the i2c regmap functions are compiled

On Fri, 29 Jul 2016, Uwe Kleine-König wrote: > This fixes a compile failure: > > drivers/built-in.o: In function `wm8350_i2c_probe': > core.c:(.text+0x828b0): undefined reference to `__devm_regmap_init_i2c' > Makefile:953: recipe for target 'vmlinux' failed > > Fixes:

Re: [PATCH] lockdep: fix warning in case of no_validate lock

On Wed, Jul 13, 2016 at 11:06:36AM +0800, Ming Lei wrote: > Now there are several locks which are marked as > no_validate, so name of the lock class can be > different with the no_validate lock. Hurgh, how did that happen? See checkpatch saying: scripts/checkpatch.pl: "lockdep_no_validate

Re: [PATCH] lockdep: fix warning in case of no_validate lock

On Wed, Jul 13, 2016 at 11:06:36AM +0800, Ming Lei wrote: > Now there are several locks which are marked as > no_validate, so name of the lock class can be > different with the no_validate lock. Hurgh, how did that happen? See checkpatch saying: scripts/checkpatch.pl: "lockdep_no_validate

Re: [PATCH v6 2/4] mfd: lp873x: Add lp873x PMIC support

On Mon, 08 Aug 2016, Keerthy wrote: > The LP873X chip is a power management IC for Portable Navigation Systems > and Tablet Computing devices. It contains the following components: > > - Regulators. > - Configurable General Purpose Output Signals(GPO). > > PMIC interacts with the

Re: [PATCH v6 2/4] mfd: lp873x: Add lp873x PMIC support

On Mon, 08 Aug 2016, Keerthy wrote: > The LP873X chip is a power management IC for Portable Navigation Systems > and Tablet Computing devices. It contains the following components: > > - Regulators. > - Configurable General Purpose Output Signals(GPO). > > PMIC interacts with the

Re: [PATCH v5] spi: spi-ti-qspi: Add DMA support for QSPI mmap read

On Tuesday 09 August 2016 05:03 PM, Mark Brown wrote: > On Tue, Aug 09, 2016 at 04:33:11PM +0530, Vignesh R wrote: > >> +static int ti_qspi_map_buf(struct ti_qspi *qspi, void *buf, >> + unsigned int len, struct sg_table *sgt) >> +{ >> +unsigned int max_seg_size = >> +

Re: [PATCH v5] spi: spi-ti-qspi: Add DMA support for QSPI mmap read

On Tuesday 09 August 2016 05:03 PM, Mark Brown wrote: > On Tue, Aug 09, 2016 at 04:33:11PM +0530, Vignesh R wrote: > >> +static int ti_qspi_map_buf(struct ti_qspi *qspi, void *buf, >> + unsigned int len, struct sg_table *sgt) >> +{ >> +unsigned int max_seg_size = >> +

[PATCH] console: Don't prefer first registered if DT specifies stdout-path

If a device tree specifies a preferred device for kernel console output via the stdout-path or linux,stdout-path chosen node properties or the stdout alias then the kernel ought to honor it & output the kernel console to that device. As it stands, this isn't the case. Whilst we parse the

[PATCH] console: Don't prefer first registered if DT specifies stdout-path

If a device tree specifies a preferred device for kernel console output via the stdout-path or linux,stdout-path chosen node properties or the stdout alias then the kernel ought to honor it & output the kernel console to that device. As it stands, this isn't the case. Whilst we parse the

Re: [PATCH v6 1/4] Documentation: mfd: LP873X: Add information for the mfd driver

On Mon, 08 Aug 2016, Keerthy wrote: > The lp873x series of PMICs have a bunch of regulators and a couple > of GPO(General Purpose Outputs). > Add information for the MFD and regulator drivers. > > Acked-by: Rob Herring > Signed-off-by: Keerthy These should

Re: [PATCH v6 1/4] Documentation: mfd: LP873X: Add information for the mfd driver

On Mon, 08 Aug 2016, Keerthy wrote: > The lp873x series of PMICs have a bunch of regulators and a couple > of GPO(General Purpose Outputs). > Add information for the MFD and regulator drivers. > > Acked-by: Rob Herring > Signed-off-by: Keerthy These should be in chronological order. Rob

Re: [PATCH V2] mfd: da9063: Update author information to remove incorrect e-mail addresses

On Mon, 08 Aug 2016, Steve Twiss wrote: > From: Steve Twiss > > Remove incorrect e-mail addresses from the copyright header and > MODULE_AUTHOR() macro. These e-mail addresses are no longer in use. > > The author names have not been changed, only the e-mail

Re: [PATCH V2] mfd: da9063: Update author information to remove incorrect e-mail addresses

On Mon, 08 Aug 2016, Steve Twiss wrote: > From: Steve Twiss > > Remove incorrect e-mail addresses from the copyright header and > MODULE_AUTHOR() macro. These e-mail addresses are no longer in use. > > The author names have not been changed, only the e-mail addresses have > been deleted from

Re: [PATCH 3/3] fs: befs: fix typo in befs_sb_info

On 09/08/16 13:32, Salah Triki wrote: > Fixing jornal to Journal. > > Signed-off-by: Salah Triki > --- > fs/befs/befs.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/befs/befs.h b/fs/befs/befs.h > index 511d16d..55f3ea2 100644 > ---

Re: [PATCH 3/3] fs: befs: fix typo in befs_sb_info

On 09/08/16 13:32, Salah Triki wrote: > Fixing jornal to Journal. > > Signed-off-by: Salah Triki > --- > fs/befs/befs.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/befs/befs.h b/fs/befs/befs.h > index 511d16d..55f3ea2 100644 > --- a/fs/befs/befs.h > +++

Re: [PATCH 4/9] remoteproc: core: New API to add new resources to the resource table

On Mon, 08 Aug 2016, loic pallardy wrote: > Hi Lee, > > After splitting this patch in 2, it may be good to add a debugfs entry to > display current rsc associated to one rproc. Happy to take suggestions to add functionality, but I would like to prevent *this* set from suffering from feature

Re: [PATCH 4/9] remoteproc: core: New API to add new resources to the resource table

On Mon, 08 Aug 2016, loic pallardy wrote: > Hi Lee, > > After splitting this patch in 2, it may be good to add a debugfs entry to > display current rsc associated to one rproc. Happy to take suggestions to add functionality, but I would like to prevent *this* set from suffering from feature

Re: [PATCH 7/9] remoteproc: core: Add function to over-ride current resource table

On Mon, 08 Aug 2016, loic pallardy wrote: > Hi Lee > > On 08/04/2016 11:21 AM, Lee Jones wrote: > > Most of the new resource table handling function are now in place, so > > it's time to put it all together. Once new resource table information > > has been requested, the structures will be held

Re: [PATCH 7/9] remoteproc: core: Add function to over-ride current resource table

On Mon, 08 Aug 2016, loic pallardy wrote: > Hi Lee > > On 08/04/2016 11:21 AM, Lee Jones wrote: > > Most of the new resource table handling function are now in place, so > > it's time to put it all together. Once new resource table information > > has been requested, the structures will be held

Applied "ASoC: lpass-platform: don't use snd_soc_pcm_set_drvdata()" to the asoc tree

The patch ASoC: lpass-platform: don't use snd_soc_pcm_set_drvdata() 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)

Applied "regmap: Add a function to check if a regmap register is cached" to the regmap tree

The patch regmap: Add a function to check if a regmap register is cached has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: remove snd_soc_pcm_set/get_drvdata()" to the asoc tree

The patch ASoC: remove snd_soc_pcm_set/get_drvdata() 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

Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close

On Tue, 9 Aug 2016, Alexander Shishkin wrote: > Awesome, I'll have a look. Can you tell it it was messing around with > intel_bts driver from the fuzzer log? the fuzzer is messing around with the aux buffer, but this particular bug triggered quickly so I can't easily tell if this particular bug

Re: linux-next: build failure after merge of Linus' tree

On 8/9/2016 4:54 AM, Leon Romanovsky wrote: > On Mon, Aug 8, 2016 at 6:37 PM, Doug Ledford wrote: >> On 8/7/2016 9:58 PM, Stephen Rothwell wrote: >>> Hi all, >>> >>> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed >>> like this: >>> >>>

Applied "ASoC: lpass-platform: don't use snd_soc_pcm_set_drvdata()" to the asoc tree

The patch ASoC: lpass-platform: don't use snd_soc_pcm_set_drvdata() 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)

Applied "regmap: Add a function to check if a regmap register is cached" to the regmap tree

The patch regmap: Add a function to check if a regmap register is cached has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: remove snd_soc_pcm_set/get_drvdata()" to the asoc tree

The patch ASoC: remove snd_soc_pcm_set/get_drvdata() 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

Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close

On Tue, 9 Aug 2016, Alexander Shishkin wrote: > Awesome, I'll have a look. Can you tell it it was messing around with > intel_bts driver from the fuzzer log? the fuzzer is messing around with the aux buffer, but this particular bug triggered quickly so I can't easily tell if this particular bug

Re: linux-next: build failure after merge of Linus' tree

On 8/9/2016 4:54 AM, Leon Romanovsky wrote: > On Mon, Aug 8, 2016 at 6:37 PM, Doug Ledford wrote: >> On 8/7/2016 9:58 PM, Stephen Rothwell wrote: >>> Hi all, >>> >>> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed >>> like this: >>> >>>

Re: [PATCH 0/5] ipc/msg: Sender/receiver optimizations

On Thu, Aug 04, 2016 at 06:44:09PM +0200, Peter Zijlstra wrote: > On Thu, Jul 28, 2016 at 04:33:34PM -0700, Davidlohr Bueso wrote: > > Hi, > > > > I'm resending Sebastian's sysv msg queue use of wake_qs but updated > > to the last observations I need wrt the need of explicit barriers > > after

Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree

The patch regmap: debugfs: Add support for dumping write only device registers has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Re: [PATCH 0/5] ipc/msg: Sender/receiver optimizations

On Thu, Aug 04, 2016 at 06:44:09PM +0200, Peter Zijlstra wrote: > On Thu, Jul 28, 2016 at 04:33:34PM -0700, Davidlohr Bueso wrote: > > Hi, > > > > I'm resending Sebastian's sysv msg queue use of wake_qs but updated > > to the last observations I need wrt the need of explicit barriers > > after

Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree

The patch regmap: debugfs: Add support for dumping write only device registers has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Re: [PATCH v7 4/4] nmi_backtrace: generate one-line reports for idle cpus

On Mon 2016-08-08 12:03:38, Chris Metcalf wrote: > When doing an nmi backtrace of many cores, most of which are idle, > the output is a little overwhelming and very uninformative. Suppress > messages for cpus that are idling when they are interrupted and just > emit one line, "NMI backtrace for N

Re: [PATCH v7 4/4] nmi_backtrace: generate one-line reports for idle cpus

On Mon 2016-08-08 12:03:38, Chris Metcalf wrote: > When doing an nmi backtrace of many cores, most of which are idle, > the output is a little overwhelming and very uninformative. Suppress > messages for cpus that are idling when they are interrupted and just > emit one line, "NMI backtrace for N

Re: [PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Hey, Op 08-08-16 om 23:03 schreef Lyude: > Since the watermark calculations for Skylake are still broken, we're apt > to hitting underruns very easily under multi-monitor configurations. > While it would be lovely if this was fixed, it's not. Another problem > that's been coming from this

Re: [PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Hey, Op 08-08-16 om 23:03 schreef Lyude: > Since the watermark calculations for Skylake are still broken, we're apt > to hitting underruns very easily under multi-monitor configurations. > While it would be lovely if this was fixed, it's not. Another problem > that's been coming from this

[PATCH 11/20] leds: Remove SEAD3 driver

SEAD3 is now using the generic syscon & regmap based register-bit-led driver, so remove the unused custom SEAD3 LED driver. Signed-off-by: Paul Burton --- drivers/leds/Kconfig | 10 -- drivers/leds/Makefile | 1 - drivers/leds/leds-sead3.c | 78

[PATCH 19/20] MIPS: SEAD3: Use img-ascii-lcd driver

Probe the img-ascii-lcd driver using device tree in order to display a message on the SEAD3 board's LCD display, and remove the platform code that was formerly performing this function. This removes more platform code and moves SEAD3 further towards being entirely DT-based. Signed-off-by: Paul

[PATCH 15/20] MIPS: SEAD3: Drop use of cobalt fbdev driver

The 2 line * 16 character LCD display on the SEAD3 board has no real use as a framebuffer device. It's far too small to produce any meaningful output if used as the kernel console, SEAD3 is a development board that will essentially always have a far more useful UART connection & the code in

[PATCH 20/20] MIPS: SEAD3: Remove custom read_persistent_clock

The SEAD3 board defines a custom implementation of read_persistent_clock which does exactly the same dummy operation as the generic weak version. Remove the not really implemented custom version. Signed-off-by: Paul Burton --- arch/mips/mti-sead3/sead3-time.c | 6

[PATCH 11/20] leds: Remove SEAD3 driver

SEAD3 is now using the generic syscon & regmap based register-bit-led driver, so remove the unused custom SEAD3 LED driver. Signed-off-by: Paul Burton --- drivers/leds/Kconfig | 10 -- drivers/leds/Makefile | 1 - drivers/leds/leds-sead3.c | 78

[PATCH 19/20] MIPS: SEAD3: Use img-ascii-lcd driver

Probe the img-ascii-lcd driver using device tree in order to display a message on the SEAD3 board's LCD display, and remove the platform code that was formerly performing this function. This removes more platform code and moves SEAD3 further towards being entirely DT-based. Signed-off-by: Paul

[PATCH 15/20] MIPS: SEAD3: Drop use of cobalt fbdev driver

The 2 line * 16 character LCD display on the SEAD3 board has no real use as a framebuffer device. It's far too small to produce any meaningful output if used as the kernel console, SEAD3 is a development board that will essentially always have a far more useful UART connection & the code in

[PATCH 20/20] MIPS: SEAD3: Remove custom read_persistent_clock

The SEAD3 board defines a custom implementation of read_persistent_clock which does exactly the same dummy operation as the generic weak version. Remove the not really implemented custom version. Signed-off-by: Paul Burton --- arch/mips/mti-sead3/sead3-time.c | 6 -- 1 file changed, 6

[PATCH 13/20] MIPS: SEAD3: Use generic restart-poweroff driver

Remove the custom platform code to restart when instructed to power off, instead relying upon the generic restart-poweroff driver probed via DT to do the same thing. Remove also the halt implementation, which is incorrect. The generic MIPS version will hang the system as halt should.

[PATCH 17/20] dt-bindings: img-ascii-lcd: Document a binding for simple ASCII LCDs

Add documentation for a devicetree binding for the simple ASCII LCD displays found on development boards such as the MIPS Boston, MIPS Malta & MIPS SEAD3 from Imagination Technologies. Signed-off-by: Paul Burton --- .../devicetree/bindings/auxdisplay/img-ascii-lcd.txt

[PATCH 10/20] MIPS: SEAD3: Use register-bit-led driver via DT for LEDs

Probe a driver for the PLED & FLED LEDs found on the SEAD3 board using the register-bit-led driver via device tree, rather than a custom driver via platform code. Enable support for the register-bit-led driver & its prerequisite syscon in sead3_defconfig. Signed-off-by: Paul Burton

[PATCH 14/20] MIPS: SEAD3: Parse memsize in DT shim

Parse the memsize argument provided by the bootloader in the DT shim code, allowing the user to override it on the command line. This places all of the DT manipulation code into sead3-dtshim.c. Signed-off-by: Paul Burton --- arch/mips/mti-sead3/sead3-dtshim.c | 72

<    8   9   10   11   12   13   14   15   16   17   >