[net-next PATCH 11/27] arch/m68k: Add option to skip DMA sync as a part of mapping

This change allows us to pass DMA_ATTR_SKIP_CPU_SYNC which allows us to avoid invoking cache line invalidation if the driver will just handle it later via a sync_for_cpu or sync_for_device call. Cc: Geert Uytterhoeven Cc: linux-m...@lists.linux-m68k.org Signed-off-by:

[net-next PATCH 10/27] arch/hexagon: Add option to skip DMA sync as a part of mapping

This change allows us to pass DMA_ATTR_SKIP_CPU_SYNC which allows us to avoid invoking cache line invalidation if the driver will just handle it later via a sync_for_cpu or sync_for_device call. Cc: Richard Kuo Cc: linux-hexa...@vger.kernel.org Signed-off-by: Alexander Duyck

[net-next PATCH 11/27] arch/m68k: Add option to skip DMA sync as a part of mapping

This change allows us to pass DMA_ATTR_SKIP_CPU_SYNC which allows us to avoid invoking cache line invalidation if the driver will just handle it later via a sync_for_cpu or sync_for_device call. Cc: Geert Uytterhoeven Cc: linux-m...@lists.linux-m68k.org Signed-off-by: Alexander Duyck ---

[net-next PATCH 10/27] arch/hexagon: Add option to skip DMA sync as a part of mapping

This change allows us to pass DMA_ATTR_SKIP_CPU_SYNC which allows us to avoid invoking cache line invalidation if the driver will just handle it later via a sync_for_cpu or sync_for_device call. Cc: Richard Kuo Cc: linux-hexa...@vger.kernel.org Signed-off-by: Alexander Duyck ---

[PATCH 2/2] arm64, numa: Force of_node_to_nid to return NUMA_NO_NODE when numa=off.

From: David Daney When "numa=off" is passed on the command line, of_node_to_nid() still returns the node number (which can be greater than zero). However, in this case all the memory is associated with the dummy node zero. This causes OOPS in kernel/irq/irqdomain.c:

[PATCH 2/2] arm64, numa: Force of_node_to_nid to return NUMA_NO_NODE when numa=off.

From: David Daney When "numa=off" is passed on the command line, of_node_to_nid() still returns the node number (which can be greater than zero). However, in this case all the memory is associated with the dummy node zero. This causes OOPS in kernel/irq/irqdomain.c: domain =

[PATCH 1/2] of, numa: Add function to disable of_node_to_nid().

From: David Daney On arm64 NUMA kernels we can pass "numa=off" on the command line to disable NUMA. A side effect of this is that kmalloc_node() calls to non-zero nodes will crash the system with an OOPS: [0.00] [] __alloc_pages_nodemask+0xa4/0xe68 [

[PATCH 0/2] arm64, numa: Fix OOPS with numa=off

From: David Daney We get an OOPS in the arm64 kernel on NUMA systems when numa=off is passed on the command line. Fix it by returning NUMA_NO_NODE from of_node_to_nid when numa=off. David Daney (2): of, numa: Add function to disable of_node_to_nid(). arm64, numa:

[PATCH 1/2] of, numa: Add function to disable of_node_to_nid().

From: David Daney On arm64 NUMA kernels we can pass "numa=off" on the command line to disable NUMA. A side effect of this is that kmalloc_node() calls to non-zero nodes will crash the system with an OOPS: [0.00] [] __alloc_pages_nodemask+0xa4/0xe68 [0.00] [] new_slab+0xd0/0x57c

[PATCH 0/2] arm64, numa: Fix OOPS with numa=off

From: David Daney We get an OOPS in the arm64 kernel on NUMA systems when numa=off is passed on the command line. Fix it by returning NUMA_NO_NODE from of_node_to_nid when numa=off. David Daney (2): of, numa: Add function to disable of_node_to_nid(). arm64, numa: Force of_node_to_nid to

Re: [RFC][PATCH] usb: dwc2: Make sure we disconnect the gadget state on reset

On 10/19/2016 11:00 PM, John Stultz wrote: > I had seen some odd behavior with HiKey's usb-gadget interface > that I finally seemed to have chased down. Basically every other > time I pluged in the OTG port, the gadget interface would > properly initialize. The other times, I'd get a big WARN_ON >

Re: [RFC][PATCH] usb: dwc2: Make sure we disconnect the gadget state on reset

On 10/19/2016 11:00 PM, John Stultz wrote: > I had seen some odd behavior with HiKey's usb-gadget interface > that I finally seemed to have chased down. Basically every other > time I pluged in the OTG port, the gadget interface would > properly initialize. The other times, I'd get a big WARN_ON >

[PATCH] crypto: caam: fix type mismatch warning

Building the caam driver on arm64 produces a harmless warning: drivers/crypto/caam/caamalg.c:140:139: warning: comparison of distinct pointer types lacks a cast We can use min_t to tell the compiler which type we want it to use here. Fixes: 5ecf8ef9103c ("crypto: caam - fix sg dump")

[PATCH] crypto: caam: fix type mismatch warning

Building the caam driver on arm64 produces a harmless warning: drivers/crypto/caam/caamalg.c:140:139: warning: comparison of distinct pointer types lacks a cast We can use min_t to tell the compiler which type we want it to use here. Fixes: 5ecf8ef9103c ("crypto: caam - fix sg dump")

Re: [RFC PATCH 01/13] of: Remove comments that state the obvious

On Tue, 2016-10-25 at 13:58 -0700, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Remove comments that state the obvious, to reduce clutter Some of these removals might be overly aggressive. > diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c [] > @@

Re: [RFC PATCH 01/13] of: Remove comments that state the obvious

On Tue, 2016-10-25 at 13:58 -0700, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Remove comments that state the obvious, to reduce clutter Some of these removals might be overly aggressive. > diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c [] > @@ -125,7 +114,6 @@ static

Re: [RFC/PATCH 2/2] perf sched: Make common options cascading

On Tue, Oct 25, 2016 at 02:21:32PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 24, 2016 at 07:03:32PM +0200, Jiri Olsa escreveu: > > On Mon, Oct 24, 2016 at 12:00:03PM +0900, Namhyung Kim wrote: > > > The -i and -v options can be used in subcommands so enable cascading the > > >

Re: [RFC/PATCH 2/2] perf sched: Make common options cascading

On Tue, Oct 25, 2016 at 02:21:32PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 24, 2016 at 07:03:32PM +0200, Jiri Olsa escreveu: > > On Mon, Oct 24, 2016 at 12:00:03PM +0900, Namhyung Kim wrote: > > > The -i and -v options can be used in subcommands so enable cascading the > > >

Re: [PATCH 1/3] perf sched map: Apply cpu color when there's an activity

Hi Arnaldo, On Tue, Oct 25, 2016 at 03:07:46PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 24, 2016 at 11:02:43AM +0900, Namhyung Kim escreveu: > > Applying cpu color always doesn't help readability IMHO. Instead it > > might be better to applying the color when there's an activity on

Re: [PATCH 1/3] perf sched map: Apply cpu color when there's an activity

Hi Arnaldo, On Tue, Oct 25, 2016 at 03:07:46PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 24, 2016 at 11:02:43AM +0900, Namhyung Kim escreveu: > > Applying cpu color always doesn't help readability IMHO. Instead it > > might be better to applying the color when there's an activity on

[PATCH v2 1/2] staging: lustre: remove broken dead code in cfs_cpt_table_create_pattern

After a recent bugfix, we get a warning about the use of an uninitialized variable: drivers/staging/lustre/lnet/libcfs/linux/linux-cpu.c: In function 'cfs_cpt_table_create_pattern': drivers/staging/lustre/lnet/libcfs/linux/linux-cpu.c:833:7: error: 'str' may be used uninitialized in this

[PATCH v2 1/2] staging: lustre: remove broken dead code in cfs_cpt_table_create_pattern

After a recent bugfix, we get a warning about the use of an uninitialized variable: drivers/staging/lustre/lnet/libcfs/linux/linux-cpu.c: In function 'cfs_cpt_table_create_pattern': drivers/staging/lustre/lnet/libcfs/linux/linux-cpu.c:833:7: error: 'str' may be used uninitialized in this

[PATCH v2 2/2] staging: lustre: restore initialization of return code

A recent rework removed the initialization of the successful return code from lov_getstripe: drivers/staging/lustre/lustre/lov/lov_pack.c: In function 'lov_getstripe': drivers/staging/lustre/lustre/lov/lov_pack.c:426:9: error: 'rc' may be used uninitialized in this function

[PATCH v2 2/2] staging: lustre: restore initialization of return code

A recent rework removed the initialization of the successful return code from lov_getstripe: drivers/staging/lustre/lustre/lov/lov_pack.c: In function 'lov_getstripe': drivers/staging/lustre/lustre/lov/lov_pack.c:426:9: error: 'rc' may be used uninitialized in this function

Re: [PATCH v2] Input: synaptics-rmi4 - stop scanning PDT after two empty pages

On Tue, Oct 25, 2016 at 1:36 PM, Nick Dyer wrote: > We have encountered some RMI4 firmwares where there are blank pages in > between PDT pages which contain functions. This change makes them > correctly enumerate all functions on the device. > > Tested on S7817 (has empty page

Re: [PATCH v2] Input: synaptics-rmi4 - stop scanning PDT after two empty pages

On Tue, Oct 25, 2016 at 1:36 PM, Nick Dyer wrote: > We have encountered some RMI4 firmwares where there are blank pages in > between PDT pages which contain functions. This change makes them > correctly enumerate all functions on the device. > > Tested on S7817 (has empty page 2). > >

Re: [PATCH net-next] ibmveth: calculate correct gso_size and set gso_type

>> + u16 hdr_len = ETH_HLEN + sizeof(struct tcphdr); > Compiler may optmize this, but maybe move hdr_len to [*] ?> There are other places in the stack where a u16 is used for the same purpose. So I'll rather stick to that convention. I'll make the other formatting changes you suggested and

Re: [PATCH net-next] ibmveth: calculate correct gso_size and set gso_type

>> + u16 hdr_len = ETH_HLEN + sizeof(struct tcphdr); > Compiler may optmize this, but maybe move hdr_len to [*] ?> There are other places in the stack where a u16 is used for the same purpose. So I'll rather stick to that convention. I'll make the other formatting changes you suggested and

Re: [PATCH 0/3] iopmem : A block device for PCIe memory

On Tue, Oct 25, 2016 at 05:50:43AM -0600, Stephen Bates wrote: > Hi Dave and Christoph > > On Fri, Oct 21, 2016 at 10:12:53PM +1100, Dave Chinner wrote: > > On Fri, Oct 21, 2016 at 02:57:14AM -0700, Christoph Hellwig wrote: > > > On Fri, Oct 21, 2016 at 10:22:39AM +1100, Dave Chinner wrote: > > >

Re: [PATCH 0/3] iopmem : A block device for PCIe memory

On Tue, Oct 25, 2016 at 05:50:43AM -0600, Stephen Bates wrote: > Hi Dave and Christoph > > On Fri, Oct 21, 2016 at 10:12:53PM +1100, Dave Chinner wrote: > > On Fri, Oct 21, 2016 at 02:57:14AM -0700, Christoph Hellwig wrote: > > > On Fri, Oct 21, 2016 at 10:22:39AM +1100, Dave Chinner wrote: > > >

You Have A Deposit Pending On Your USAA Bank Account

PENDING USAA DEPOSIT.pdf Description: Adobe PDF document

You Have A Deposit Pending On Your USAA Bank Account

PENDING USAA DEPOSIT.pdf Description: Adobe PDF document

Re: UBIFS LEB properties tree with odd addresses

Naga Sureshkumar Relli, On 25.10.2016 08:05, Naga Sureshkumar Relli wrote: > Hi, > > We are testing UBIFS (NOR) on Zynq Ultrascale+ MPSoC GQSPI controller driver. > Apart from my previous mail thread about UBIFS, i.e along with dma issue I am > facing one more > Problem related to offsets. > >

Re: UBIFS LEB properties tree with odd addresses

Naga Sureshkumar Relli, On 25.10.2016 08:05, Naga Sureshkumar Relli wrote: > Hi, > > We are testing UBIFS (NOR) on Zynq Ultrascale+ MPSoC GQSPI controller driver. > Apart from my previous mail thread about UBIFS, i.e along with dma issue I am > facing one more > Problem related to offsets. > >

Re: [PATCH V2 0/8] PM / OPP: Multiple regulator support

Hi, On 10/23/2016 11:26 PM, Viresh Kumar wrote: On 23-10-16, 20:08, Dave Gerlach wrote: Overall this series looks good to me apart from a few small things. Most importantly I was able to get a working implementation using two regulators on ti dra7xx platform with proper sequencing built on top

Re: [PATCH V2 0/8] PM / OPP: Multiple regulator support

Hi, On 10/23/2016 11:26 PM, Viresh Kumar wrote: On 23-10-16, 20:08, Dave Gerlach wrote: Overall this series looks good to me apart from a few small things. Most importantly I was able to get a working implementation using two regulators on ti dra7xx platform with proper sequencing built on top

[PATCH 3/5] pinctrl: core: Add generic pinctrl functions for managing groups

We can add generic helpers for function handling for cases where the pin controller driver does not need to use static arrays. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 4 ++ drivers/pinctrl/core.c | 2 + drivers/pinctrl/core.h | 18 +

[RFC PATCH 00/13] of: Make drivers/of/resolver.c more readable

From: Frank Rowand drivers/of/resolve.c is a bit difficult to read. Clean it up so that review of future overlay related patches will be easier. Most of the patches are intended to be reformatting, with no functional change. Patches that are expected to have a

[PATCH 3/5] pinctrl: core: Add generic pinctrl functions for managing groups

We can add generic helpers for function handling for cases where the pin controller driver does not need to use static arrays. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 4 ++ drivers/pinctrl/core.c | 2 + drivers/pinctrl/core.h | 18 + drivers/pinctrl/pinmux.c |

[RFC PATCH 00/13] of: Make drivers/of/resolver.c more readable

From: Frank Rowand drivers/of/resolve.c is a bit difficult to read. Clean it up so that review of future overlay related patches will be easier. Most of the patches are intended to be reformatting, with no functional change. Patches that are expected to have a functional change are: Remove

[PATCH 2/5] pinctrl: core: Add generic pinctrl functions for managing groups

We can add generic helpers for pin group handling for cases where the pin controller driver does not need to use static arrays. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 3 + drivers/pinctrl/core.c | 178

[RFC PATCH 03/13] of: Remove braces around single line blocks.

From: Frank Rowand The single line blocks were created by previous patches in the series. Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 25 - 1 file changed, 8 insertions(+), 17 deletions(-) diff --git

[PATCH 1/5] pinctrl: core: Use delayed work for hogs

Having the pin control framework call pin controller functions before it's probe has finished is not nice as the pin controller device driver does not yet have struct pinctrl_dev handle. Let's fix this issue by adding deferred work for hogs. This is needed to be able to add pinctrl generic helper

[PATCH 2/5] pinctrl: core: Add generic pinctrl functions for managing groups

We can add generic helpers for pin group handling for cases where the pin controller driver does not need to use static arrays. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 3 + drivers/pinctrl/core.c | 178

[RFC PATCH 03/13] of: Remove braces around single line blocks.

From: Frank Rowand The single line blocks were created by previous patches in the series. Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 25 - 1 file changed, 8 insertions(+), 17 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index

[PATCH 1/5] pinctrl: core: Use delayed work for hogs

Having the pin control framework call pin controller functions before it's probe has finished is not nice as the pin controller device driver does not yet have struct pinctrl_dev handle. Let's fix this issue by adding deferred work for hogs. This is needed to be able to add pinctrl generic helper

[RFC PATCH 02/13] of: Remove excessive printks to reduce clutter

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 28 1 file changed, 28 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 4ff0220d7aa2..93a7ca0bf98c 100644

[RFC PATCH 02/13] of: Remove excessive printks to reduce clutter

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 28 1 file changed, 28 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 4ff0220d7aa2..93a7ca0bf98c 100644 --- a/drivers/of/resolver.c +++

Re: [RFC PATCH 00/13] of: Make drivers/of/resolver.c more readable

On 10/25/16 13:58, frowand.l...@gmail.com wrote: > From: Frank Rowand > > drivers/of/resolve.c is a bit difficult to read. Clean it up so > that review of future overlay related patches will be easier. < snip > Hi Pantelis, Can you test this patch series on some

Re: [RFC PATCH 00/13] of: Make drivers/of/resolver.c more readable

On 10/25/16 13:58, frowand.l...@gmail.com wrote: > From: Frank Rowand > > drivers/of/resolve.c is a bit difficult to read. Clean it up so > that review of future overlay related patches will be easier. < snip > Hi Pantelis, Can you test this patch series on some real hardware? Thanks,

Re: [PATCH v2 1/1] remoteproc: Add support for xo clock

On 10/25/2016 01:57 PM, Sarangdhar Joshi wrote: Add xo clock support required to boot up Qualcomm ADSP processor. The ADSP remoteproc driver keeps xo clock enabled until the driver receives "handover" irq, in order to allow ADSP processor to vote for xo clock with rpm. Signed-off-by: Sarangdhar

Re: [PATCH v2 1/1] remoteproc: Add support for xo clock

On 10/25/2016 01:57 PM, Sarangdhar Joshi wrote: Add xo clock support required to boot up Qualcomm ADSP processor. The ADSP remoteproc driver keeps xo clock enabled until the driver receives "handover" irq, in order to allow ADSP processor to vote for xo clock with rpm. Signed-off-by: Sarangdhar

[PATCH 4/5] pinctrl: single: Use generic pinctrl helpers for managing groups

We can now drop the driver specific code for managing groups. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 2 +- drivers/pinctrl/pinctrl-single.c | 155 +++ 2 files changed, 11 insertions(+), 146 deletions(-) diff

[PATCH 4/5] pinctrl: single: Use generic pinctrl helpers for managing groups

We can now drop the driver specific code for managing groups. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 2 +- drivers/pinctrl/pinctrl-single.c | 155 +++ 2 files changed, 11 insertions(+), 146 deletions(-) diff --git

[PATCH 5/5] pinctrl: single: Use generic pinmux helpers for managing functions

We can now drop the driver specific code for managing functions. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 2 +- drivers/pinctrl/pinctrl-single.c | 134 ++- 2 files changed, 19 insertions(+), 117 deletions(-)

[RFC PATCH 09/13] of: Remove redundant size check

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 708daca1d522..76c09cb57eae 100644 ---

[PATCH 5/5] pinctrl: single: Use generic pinmux helpers for managing functions

We can now drop the driver specific code for managing functions. Signed-off-by: Tony Lindgren --- drivers/pinctrl/Kconfig | 2 +- drivers/pinctrl/pinctrl-single.c | 134 ++- 2 files changed, 19 insertions(+), 117 deletions(-) diff --git

[RFC PATCH 09/13] of: Remove redundant size check

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 708daca1d522..76c09cb57eae 100644 --- a/drivers/of/resolver.c +++ b/drivers/of/resolver.c @@ -216,7

[PATCH 1/2] ARM: imx: mmdc perf function support i.MX6QP

i.MX6QP added new reigster bit PROFILE_SEL in MADPCR0. need set it at perf start. Signed-off-by: Frank Li --- arch/arm/mach-imx/mmdc.c | 45 +++-- 1 file changed, 39 insertions(+), 6 deletions(-) diff --git a/arch/arm/mach-imx/mmdc.c

[RFC PATCH 05/13] of: Rename functions to more accurately reflect what they do

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index

[PATCH 1/2] ARM: imx: mmdc perf function support i.MX6QP

i.MX6QP added new reigster bit PROFILE_SEL in MADPCR0. need set it at perf start. Signed-off-by: Frank Li --- arch/arm/mach-imx/mmdc.c | 45 +++-- 1 file changed, 39 insertions(+), 6 deletions(-) diff --git a/arch/arm/mach-imx/mmdc.c

[RFC PATCH 05/13] of: Rename functions to more accurately reflect what they do

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 31fd3800787a..3d123b612789 100644 --- a/drivers/of/resolver.c +++

[PATCH 0/5] Add generic pinctrl helpers for managing groups and functions

Hi all, Here are some changes to add generic helpers for managing pinctrl groups and functions. Regards, Tony Tony Lindgren (5): pinctrl: core: Use delayed work for hogs pinctrl: core: Add generic pinctrl functions for managing groups pinctrl: core: Add generic pinctrl functions for

[RFC PATCH 01/13] of: Remove comments that state the obvious

From: Frank Rowand Remove comments that state the obvious, to reduce clutter Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 31 ++- 1 file changed, 2 insertions(+), 29 deletions(-) diff --git

[PATCH 0/5] Add generic pinctrl helpers for managing groups and functions

Hi all, Here are some changes to add generic helpers for managing pinctrl groups and functions. Regards, Tony Tony Lindgren (5): pinctrl: core: Use delayed work for hogs pinctrl: core: Add generic pinctrl functions for managing groups pinctrl: core: Add generic pinctrl functions for

[RFC PATCH 01/13] of: Remove comments that state the obvious

From: Frank Rowand Remove comments that state the obvious, to reduce clutter Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 31 ++- 1 file changed, 2 insertions(+), 29 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index

[RFC PATCH 08/13] of: Update structure of code, remove BUG_ON()

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 48 +--- 1 file changed, 17 insertions(+), 31 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c

[RFC PATCH 11/13] of: Add back an error message, restructured

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 4e6df385118b..664c97e1ecb4

[RFC PATCH 10/13] of: Update comments to reflect changes and increase clarity

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 51 --- 1 file changed, 32 insertions(+), 19 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c

[RFC PATCH 07/13] of: Rename variables to better reflect purpose or follow convention

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 172 +- 1 file changed, 85 insertions(+), 87 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c

[RFC PATCH 11/13] of: Add back an error message, restructured

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 4e6df385118b..664c97e1ecb4 100644 --- a/drivers/of/resolver.c +++

[RFC PATCH 10/13] of: Update comments to reflect changes and increase clarity

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 51 --- 1 file changed, 32 insertions(+), 19 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 76c09cb57eae..4e6df385118b 100644 ---

[RFC PATCH 07/13] of: Rename variables to better reflect purpose or follow convention

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 172 +- 1 file changed, 85 insertions(+), 87 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 0ce38aa0ed3c..0778747cdd58 100644 ---

[RFC PATCH 08/13] of: Update structure of code, remove BUG_ON()

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 48 +--- 1 file changed, 17 insertions(+), 31 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 0778747cdd58..708daca1d522 100644 ---

[RFC PATCH 06/13] of: Remove prefix "__of_" and prefix "__" from local function names

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 3d123b612789..0ce38aa0ed3c 100644 ---

[RFC PATCH 06/13] of: Remove prefix "__of_" and prefix "__" from local function names

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 3d123b612789..0ce38aa0ed3c 100644 --- a/drivers/of/resolver.c +++ b/drivers/of/resolver.c

[RFC PATCH 04/13] of: Convert comparisons to zero or NULL to simplify logical expressions

From: Frank Rowand A small number of such comparisons remain where they provide more clarity of the numeric nature of a variable. Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 42 -- 1 file

[RFC PATCH 12/13] of: Move setting of pointer to beside test for non-null

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 664c97e1ecb4..3f7cf569c7ea 100644 ---

[RFC PATCH 13/13] of: Remove unused variable overlay_symbols

From: Frank Rowand This unused variable is a reminder that symbols in overlays are not available to subsequent overlays. If such a feature is desired then there are several ways it could be implemented. Signed-off-by: Frank Rowand ---

[RFC PATCH 12/13] of: Move setting of pointer to beside test for non-null

From: Frank Rowand Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c index 664c97e1ecb4..3f7cf569c7ea 100644 --- a/drivers/of/resolver.c +++ b/drivers/of/resolver.c @@ -305,8

[RFC PATCH 13/13] of: Remove unused variable overlay_symbols

From: Frank Rowand This unused variable is a reminder that symbols in overlays are not available to subsequent overlays. If such a feature is desired then there are several ways it could be implemented. Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 5 + 1 file changed, 1

[RFC PATCH 04/13] of: Convert comparisons to zero or NULL to simplify logical expressions

From: Frank Rowand A small number of such comparisons remain where they provide more clarity of the numeric nature of a variable. Signed-off-by: Frank Rowand --- drivers/of/resolver.c | 42 -- 1 file changed, 20 insertions(+), 22 deletions(-) diff

[PATCH v2 1/1] remoteproc: Add support for xo clock

Add xo clock support required to boot up Qualcomm ADSP processor. The ADSP remoteproc driver keeps xo clock enabled until the driver receives "handover" irq, in order to allow ADSP processor to vote for xo clock with rpm. Signed-off-by: Sarangdhar Joshi ---

[v4.9 PATCH] spi: fsl-espi: avoid processing uninitalized data on error

When we get a spurious interrupt in fsl_espi_irq, we end up processing four uninitalized bytes of data, as shown in this warning message: drivers/spi/spi-fsl-espi.c: In function 'fsl_espi_irq': drivers/spi/spi-fsl-espi.c:462:4: warning: 'rx_data' may be used uninitialized in this function

Re: [PATCH 17/28] spi: fsl-espi: avoid processing uninitalized data on error

On Tuesday, October 25, 2016 8:13:09 PM CEST Mark Brown wrote: > > Not enough information to check signature validity. Show Details > On Mon, Oct 24, 2016 at 10:37:53PM +0200, Arnd Bergmann wrote: > > > I think my patch (the version I sent) should ideally make it into > > v4.9 as a bugfix.

Re: [PATCH 17/28] spi: fsl-espi: avoid processing uninitalized data on error

On Tuesday, October 25, 2016 8:13:09 PM CEST Mark Brown wrote: > > Not enough information to check signature validity. Show Details > On Mon, Oct 24, 2016 at 10:37:53PM +0200, Arnd Bergmann wrote: > > > I think my patch (the version I sent) should ideally make it into > > v4.9 as a bugfix.

[PATCH v2 1/1] remoteproc: Add support for xo clock

Add xo clock support required to boot up Qualcomm ADSP processor. The ADSP remoteproc driver keeps xo clock enabled until the driver receives "handover" irq, in order to allow ADSP processor to vote for xo clock with rpm. Signed-off-by: Sarangdhar Joshi --- drivers/remoteproc/qcom_adsp_pil.c |

[v4.9 PATCH] spi: fsl-espi: avoid processing uninitalized data on error

When we get a spurious interrupt in fsl_espi_irq, we end up processing four uninitalized bytes of data, as shown in this warning message: drivers/spi/spi-fsl-espi.c: In function 'fsl_espi_irq': drivers/spi/spi-fsl-espi.c:462:4: warning: 'rx_data' may be used uninitialized in this function

[PATCH 0/2] x86: use stdout for success and stdout for failure

For some time now my x86 builds are warning free. Yay! But there's still one single line printed to stderr: Succeed: decoded and checked 1767380 instructions This message is printed if the "insn decoder test" ran successful. Patch 1/2 sends this message to stdout (and fixes the typo). Patch

[PATCH 2/2] x86: use stderr if insn sanity test fails

If the instruction sanity test fails, it prints a "Failure" message to stdout. Make this program behave like the rest of the build and print that message to stderr. Signed-off-by: Paul Bolle --- arch/x86/tools/insn_sanity.c | 3 ++- 1 file changed, 2 insertions(+), 1

[PATCH 1/2] x86: use stdout if insn decoder test is successful

If the instruction decoder test ran successful it prints a message like this to stderr: Succeed: decoded and checked 1767380 instructions But, as described in "console mode programming user interface guidelines version 101" which doesn't exist, programs should use stderr for errors or

[PATCH 0/2] x86: use stdout for success and stdout for failure

For some time now my x86 builds are warning free. Yay! But there's still one single line printed to stderr: Succeed: decoded and checked 1767380 instructions This message is printed if the "insn decoder test" ran successful. Patch 1/2 sends this message to stdout (and fixes the typo). Patch

[PATCH 2/2] x86: use stderr if insn sanity test fails

If the instruction sanity test fails, it prints a "Failure" message to stdout. Make this program behave like the rest of the build and print that message to stderr. Signed-off-by: Paul Bolle --- arch/x86/tools/insn_sanity.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 1/2] x86: use stdout if insn decoder test is successful

If the instruction decoder test ran successful it prints a message like this to stderr: Succeed: decoded and checked 1767380 instructions But, as described in "console mode programming user interface guidelines version 101" which doesn't exist, programs should use stderr for errors or

Re: Regression caused by commit c83ed4c9dbb3 "ubifs: Abort readdir on error"

Peter, On 25.10.2016 22:09, Richard Weinberger wrote: >> /bin/mkdir -p /mnt/ovl/ovl >> /bin/mkdir -p /mnt/ovl/work >> # with c83ed4c9dbb3, the following mount fails with >> # mount: mounting overlay on /mnt/merge failed: No such file or directory >> /bin/mount -t overlay -o >>

Re: Regression caused by commit c83ed4c9dbb3 "ubifs: Abort readdir on error"

Peter, On 25.10.2016 22:09, Richard Weinberger wrote: >> /bin/mkdir -p /mnt/ovl/ovl >> /bin/mkdir -p /mnt/ovl/work >> # with c83ed4c9dbb3, the following mount fails with >> # mount: mounting overlay on /mnt/merge failed: No such file or directory >> /bin/mount -t overlay -o >>

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

On Tuesday, October 25, 2016 3:23:34 PM CEST Imran Khan wrote: > On 10/21/2016 4:03 PM, Arnd Bergmann wrote: > >> +/* socinfo: sysfs functions */ > > > > This seems overly verbose, having both raw and human-readable > > IDs is generally not necessary, pick one of the two. If you > > need any

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

On Tuesday, October 25, 2016 3:23:34 PM CEST Imran Khan wrote: > On 10/21/2016 4:03 PM, Arnd Bergmann wrote: > >> +/* socinfo: sysfs functions */ > > > > This seems overly verbose, having both raw and human-readable > > IDs is generally not necessary, pick one of the two. If you > > need any

Re: [PATCH V5 1/2] ACPI: Add support for ResourceSource/IRQ domain mapping

Hi Marc, Lorenzo, On 2016-10-20 13:51, Marc Zyngier wrote: On 20/10/16 17:48, Lorenzo Pieralisi wrote: Hi Agustin, On Tue, Oct 18, 2016 at 01:41:48PM -0400, Agustin Vega-Frias wrote: This allows irqchip drivers to associate an ACPI DSDT device to an IRQ domain and provides support for using

Re: [PATCH V5 1/2] ACPI: Add support for ResourceSource/IRQ domain mapping

Hi Marc, Lorenzo, On 2016-10-20 13:51, Marc Zyngier wrote: On 20/10/16 17:48, Lorenzo Pieralisi wrote: Hi Agustin, On Tue, Oct 18, 2016 at 01:41:48PM -0400, Agustin Vega-Frias wrote: This allows irqchip drivers to associate an ACPI DSDT device to an IRQ domain and provides support for using

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