[PATCH 12/17] ASoC: tlv320aic31xx: Add short circuit detection support

These devices support detecting and reporting short circuits across the output stages. Add support for reporting these issue. Do this by registering an interrupt if available and enabling this error to trigger that interrupt in the device. Signed-off-by: Andrew F. Davis ---

[PATCH 12/17] ASoC: tlv320aic31xx: Add short circuit detection support

These devices support detecting and reporting short circuits across the output stages. Add support for reporting these issue. Do this by registering an interrupt if available and enabling this error to trigger that interrupt in the device. Signed-off-by: Andrew F. Davis ---

[PATCH 04/17] ASoC: tlv320aic31xx: Merge init function into probe

The function aic31xx_device_init() is only called from probe and does nothing that logically shouldn't be in probe, remove this unneeded function call and move its code into probe where it was called. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 55

[PATCH 04/17] ASoC: tlv320aic31xx: Merge init function into probe

The function aic31xx_device_init() is only called from probe and does nothing that logically shouldn't be in probe, remove this unneeded function call and move its code into probe where it was called. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 55

[PATCH 11/17] ASoC: tlv320aic31xx: Reset registers during probe

Add a reset function that toggles the reset line if available or uses the software reset command otherwise. Use this in probe to ensure the registers are in a sane state. This is useful when the driver module is reloaded, or after Kexec, warm-reboots, etc.. Signed-off-by: Andrew F. Davis

[PATCH 11/17] ASoC: tlv320aic31xx: Reset registers during probe

Add a reset function that toggles the reset line if available or uses the software reset command otherwise. Use this in probe to ensure the registers are in a sane state. This is useful when the driver module is reloaded, or after Kexec, warm-reboots, etc.. Signed-off-by: Andrew F. Davis ---

Re: linux-next: Tree for Nov 8 (timer conversions)

e 20 outstanding non-trivial conversions (all are now in-flight). Combined with the trivial treewide conversions and API adjustments it produces an additional: 392 files changed, 1388 insertions(+), 1925 deletions(-) After that, all 1116 timer_setup() callsites will be finished. My tree, based on ne

Re: linux-next: Tree for Nov 8 (timer conversions)

e 20 outstanding non-trivial conversions (all are now in-flight). Combined with the trivial treewide conversions and API adjustments it produces an additional: 392 files changed, 1388 insertions(+), 1925 deletions(-) After that, all 1116 timer_setup() callsites will be finished. My tree, based on ne

Re: [PATCH net-next 00/11] net: dsa: setup stage

From: Vivien Didelot Date: Mon, 6 Nov 2017 16:11:42 -0500 > When probing a DSA switch, there is basically two stages. > > The first stage is the parsing of the switch device, from either device > tree or platform data. It fetches the DSA tree to which it

Re: [PATCH net-next 00/11] net: dsa: setup stage

From: Vivien Didelot Date: Mon, 6 Nov 2017 16:11:42 -0500 > When probing a DSA switch, there is basically two stages. > > The first stage is the parsing of the switch device, from either device > tree or platform data. It fetches the DSA tree to which it belongs, and > validates its ports. The

[PATCH 16/17] NOT FOR MERGING: Add TLV320DAC3101 to BBB for testing

--- arch/arm/boot/dts/am335x-boneblack.dts | 106 + 1 file changed, 106 insertions(+) diff --git a/arch/arm/boot/dts/am335x-boneblack.dts b/arch/arm/boot/dts/am335x-boneblack.dts index d154d3133c16..e52553d144ab 100644 --- a/arch/arm/boot/dts/am335x-boneblack.dts

[PATCH 16/17] NOT FOR MERGING: Add TLV320DAC3101 to BBB for testing

--- arch/arm/boot/dts/am335x-boneblack.dts | 106 + 1 file changed, 106 insertions(+) diff --git a/arch/arm/boot/dts/am335x-boneblack.dts b/arch/arm/boot/dts/am335x-boneblack.dts index d154d3133c16..e52553d144ab 100644 --- a/arch/arm/boot/dts/am335x-boneblack.dts

[PATCH 05/17] ASoC: tlv320aic31xx: Switch GPIO handling to use gpiod_* API

Move to using newer gpiod_* GPIO handling functions. This simplifies the code and eases dropping platform data in the next patch. Also remember GPIO are active low, so set "1" to reset. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 23 ++-

[PATCH 17/17] NOT FOR MERGING: Add demo jack detection policy for testing

--- sound/soc/codecs/tlv320aic31xx.c | 26 ++ 1 file changed, 26 insertions(+) diff --git a/sound/soc/codecs/tlv320aic31xx.c b/sound/soc/codecs/tlv320aic31xx.c index 46cd132e93ef..12daba8f60cd 100644 --- a/sound/soc/codecs/tlv320aic31xx.c +++

[PATCH 05/17] ASoC: tlv320aic31xx: Switch GPIO handling to use gpiod_* API

Move to using newer gpiod_* GPIO handling functions. This simplifies the code and eases dropping platform data in the next patch. Also remember GPIO are active low, so set "1" to reset. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 23 ++- 1 file

[PATCH 17/17] NOT FOR MERGING: Add demo jack detection policy for testing

--- sound/soc/codecs/tlv320aic31xx.c | 26 ++ 1 file changed, 26 insertions(+) diff --git a/sound/soc/codecs/tlv320aic31xx.c b/sound/soc/codecs/tlv320aic31xx.c index 46cd132e93ef..12daba8f60cd 100644 --- a/sound/soc/codecs/tlv320aic31xx.c +++

[PATCH 00/17] Add Headphone Detection to TLV320AIC31xx Driver

Hello all, This series has the end goal of adding headphone detection to the tlv320aic31xx driver. The first few patches are mostly cleanups. Then a couple bug fixes I noticed. Followed by adding interrupt handling and finally headphone detection. The last two, as their commit name recommends,

[PATCH 00/17] Add Headphone Detection to TLV320AIC31xx Driver

Hello all, This series has the end goal of adding headphone detection to the tlv320aic31xx driver. The first few patches are mostly cleanups. Then a couple bug fixes I noticed. Followed by adding interrupt handling and finally headphone detection. The last two, as their commit name recommends,

Urgent response !!!

Greetings, I have a business proposal I would love to discuss with you. please reply me for more details Yours Sincerely, miss.melisa.mehmet

[PATCH 02/17] ASoC: tlv320aic31xx: Reformat header file using GENMASK and BIT macros

We also move the comments describing the registers to after the register definition to remove non-uniform vertical white-space, this makes cross-referencing with the datasheet much easier and allowed me to find the errors that are corrected in follow-up patches. Signed-off-by: Andrew F. Davis

[PATCH 06/17] ASoC: tlv320aic31xx: Remove platform data

Platform data is not used by anyone (at least in upstream) so drop this data and switch to using fwnode(DT/ACPI) only. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 65 ++-- sound/soc/codecs/tlv320aic31xx.h | 6 2

Urgent response !!!

Greetings, I have a business proposal I would love to discuss with you. please reply me for more details Yours Sincerely, miss.melisa.mehmet

[PATCH 02/17] ASoC: tlv320aic31xx: Reformat header file using GENMASK and BIT macros

We also move the comments describing the registers to after the register definition to remove non-uniform vertical white-space, this makes cross-referencing with the datasheet much easier and allowed me to find the errors that are corrected in follow-up patches. Signed-off-by: Andrew F. Davis

[PATCH 06/17] ASoC: tlv320aic31xx: Remove platform data

Platform data is not used by anyone (at least in upstream) so drop this data and switch to using fwnode(DT/ACPI) only. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 65 ++-- sound/soc/codecs/tlv320aic31xx.h | 6 2 files changed,

[PATCH 07/17] ASoC: tlv320aic31xx: Add MICBIAS off setting

Leaving microphone bias off is a valid setting and even used in the DT binding document example. Add this setting here and document the same. Signed-off-by: Andrew F. Davis --- Documentation/devicetree/bindings/sound/tlv320aic31xx.txt | 1 +

[PATCH 08/17] ASoC: tlv320aic31xx: Check clock and divider before division

If our set_sysclk DAI callback has not been called yet p_div will be 0 and dividing by this will cause an error. Print an error message and leave before this. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 8 +++- 1 file changed, 7 insertions(+), 1

[PATCH 07/17] ASoC: tlv320aic31xx: Add MICBIAS off setting

Leaving microphone bias off is a valid setting and even used in the DT binding document example. Add this setting here and document the same. Signed-off-by: Andrew F. Davis --- Documentation/devicetree/bindings/sound/tlv320aic31xx.txt | 1 + include/dt-bindings/sound/tlv320aic31xx-micbias.h

[PATCH 08/17] ASoC: tlv320aic31xx: Check clock and divider before division

If our set_sysclk DAI callback has not been called yet p_div will be 0 and dividing by this will cause an error. Print an error message and leave before this. Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tlv320aic31xx.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff

Re: [PATCH] locking/lockdep: Revise Documentation/locking/crossrelease.txt

On Wed, Nov 08, 2017 at 10:34:38AM +0100, Ingo Molnar wrote: > > * Byungchul Park wrote: > > > I'm afraid the revision is not perfect yet. Of course, the document can > > have got much better english by others than me. > > > > But, > > > > I think I should enhance it

Re: [PATCH] locking/lockdep: Revise Documentation/locking/crossrelease.txt

On Wed, Nov 08, 2017 at 10:34:38AM +0100, Ingo Molnar wrote: > > * Byungchul Park wrote: > > > I'm afraid the revision is not perfect yet. Of course, the document can > > have got much better english by others than me. > > > > But, > > > > I think I should enhance it as much as I can, before

Re: linux-next: build failure after merge of the kspp tree

On Wed, Nov 08, 2017 at 03:43:47PM -0800, Kees Cook wrote: > On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell > wrote: > > Hi Kees, > > > > After merging the kspp tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from

Re: linux-next: build failure after merge of the kspp tree

On Wed, Nov 08, 2017 at 03:43:47PM -0800, Kees Cook wrote: > On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell > wrote: > > Hi Kees, > > > > After merging the kspp tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from

Re: [PATCH v2] rtc: rx8010: Fix for incorrect return value

On 08/11/2017 at 14:58:14 -0500, Akshay Bhat wrote: > The err variable is not being reset after a successful read. Explicitly > return 0 at the end of function call to account for all return paths. > > Reported-by: Jens-Peter Oswald > Signed-off-by: Akshay Bhat

Re: [PATCH] rtc: x-gene: mark PM functions as __maybe_unused

On 08/11/2017 at 13:08:10 +0100, Arnd Bergmann wrote: > The new xgene_rtc_alarm_irq_enabled() function is only accessed > from PM code, which is inside of an #ifdef; this causes a harmless > build warning when CONFIG_PM is disabled: > > drivers/rtc/rtc-xgene.c:108:12: error:

Re: [PATCH v2] rtc: rx8010: Fix for incorrect return value

On 08/11/2017 at 14:58:14 -0500, Akshay Bhat wrote: > The err variable is not being reset after a successful read. Explicitly > return 0 at the end of function call to account for all return paths. > > Reported-by: Jens-Peter Oswald > Signed-off-by: Akshay Bhat > --- > v2: Address comments from

Re: [PATCH] rtc: x-gene: mark PM functions as __maybe_unused

On 08/11/2017 at 13:08:10 +0100, Arnd Bergmann wrote: > The new xgene_rtc_alarm_irq_enabled() function is only accessed > from PM code, which is inside of an #ifdef; this causes a harmless > build warning when CONFIG_PM is disabled: > > drivers/rtc/rtc-xgene.c:108:12: error:

[PATCH] vhost/scsi: Use safe iteration in vhost_scsi_complete_cmd_work()

I am sorry for having made a mistake on it. -8<- >From ba9a0f76dffceffa4fa3aa2d9be49cdb0d9b7d4f Mon Sep 17 00:00:00 2001 From: Byungchul Park Date: Thu, 9 Nov 2017 09:00:21 +0900 Subject: [PATCH] vhost/scsi: Use safe iteration in vhost_scsi_complete_cmd_work()

[PATCH] vhost/scsi: Use safe iteration in vhost_scsi_complete_cmd_work()

I am sorry for having made a mistake on it. -8<- >From ba9a0f76dffceffa4fa3aa2d9be49cdb0d9b7d4f Mon Sep 17 00:00:00 2001 From: Byungchul Park Date: Thu, 9 Nov 2017 09:00:21 +0900 Subject: [PATCH] vhost/scsi: Use safe iteration in vhost_scsi_complete_cmd_work() The following patch

Re: [PATCH 1/2] MIPS: dts: remove bogus bcm96358nb4ser.dtb from dtb-y entry

2017-11-09 1:51 GMT+09:00 Rob Herring : > On Mon, Nov 6, 2017 at 5:00 AM, Masahiro Yamada > wrote: >> 2017-11-06 19:41 GMT+09:00 James Hogan : >>> Hi, >>> >>> On Sun, Nov 05, 2017 at 11:11:38PM +0900, Masahiro Yamada wrote:

Re: [PATCH 1/2] MIPS: dts: remove bogus bcm96358nb4ser.dtb from dtb-y entry

2017-11-09 1:51 GMT+09:00 Rob Herring : > On Mon, Nov 6, 2017 at 5:00 AM, Masahiro Yamada > wrote: >> 2017-11-06 19:41 GMT+09:00 James Hogan : >>> Hi, >>> >>> On Sun, Nov 05, 2017 at 11:11:38PM +0900, Masahiro Yamada wrote: +CC Ralf Baechle +CC linux-m...@linux-mips.org +CC Kevin

Re: n900 in next-20170901

* Joonsoo Kim [171109 00:05]: > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > > * Joonsoo Kim [171108 07:43]: > > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > > So it seems the issue is currently at the

Re: [PATCH x86/urgent] bpf: emulate push insns for uprobe on x86

On 11/8/17 4:06 PM, David Miller wrote: From: Yonghong Song Date: Wed, 8 Nov 2017 13:37:12 -0800 Uprobe is a tracing mechanism for userspace programs. Typical uprobe will incur overhead of two traps. First trap is caused by replaced trap insn, and the second trap is to execute

Re: n900 in next-20170901

* Joonsoo Kim [171109 00:05]: > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > > * Joonsoo Kim [171108 07:43]: > > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > > So it seems the issue is currently at the atomic_pool_init() > > > > related code? > > >

Re: [PATCH x86/urgent] bpf: emulate push insns for uprobe on x86

On 11/8/17 4:06 PM, David Miller wrote: From: Yonghong Song Date: Wed, 8 Nov 2017 13:37:12 -0800 Uprobe is a tracing mechanism for userspace programs. Typical uprobe will incur overhead of two traps. First trap is caused by replaced trap insn, and the second trap is to execute the original

[PATCH] perf/x86: Hide TSX events when no TSX

From: Andi Kleen When TSX is not available don't show the TSX events in sysfs for Haswell/Broadwell/Skylake. This fixes a perf test regression reported by 0day on Haswell systems without RTM. The earlier a5df70c35 patch hid the t/ct attributes in this case, so their

[PATCH] perf/x86: Hide TSX events when no TSX

From: Andi Kleen When TSX is not available don't show the TSX events in sysfs for Haswell/Broadwell/Skylake. This fixes a perf test regression reported by 0day on Haswell systems without RTM. The earlier a5df70c35 patch hid the t/ct attributes in this case, so their attributes cannot be parsed

Re: [PATCH v2] mm, shrinker: make shrinker_list lockless

Hi, On Wed, Nov 08, 2017 at 09:37:40AM -0800, Shakeel Butt wrote: > In our production, we have observed that the job loader gets stuck for > 10s of seconds while doing mount operation. It turns out that it was > stuck in register_shrinker() and some unrelated job was under memory > pressure and

Re: [PATCH v2] mm, shrinker: make shrinker_list lockless

Hi, On Wed, Nov 08, 2017 at 09:37:40AM -0800, Shakeel Butt wrote: > In our production, we have observed that the job loader gets stuck for > 10s of seconds while doing mount operation. It turns out that it was > stuck in register_shrinker() and some unrelated job was under memory > pressure and

Admin

ATENÇÃO; Sua caixa de correio excedeu o limite de armazenamento, que é de 5 GB como definido pelo administrador, que está atualmente em execução no 10.9GB, você pode não ser capaz de enviar ou receber novas mensagens até que você re-validar a sua caixa de correio. Para revalidar sua caixa de

Admin

ATENÇÃO; Sua caixa de correio excedeu o limite de armazenamento, que é de 5 GB como definido pelo administrador, que está atualmente em execução no 10.9GB, você pode não ser capaz de enviar ou receber novas mensagens até que você re-validar a sua caixa de correio. Para revalidar sua caixa de

Re: [PATCH x86/urgent] bpf: emulate push insns for uprobe on x86

From: Yonghong Song Date: Wed, 8 Nov 2017 13:37:12 -0800 > Uprobe is a tracing mechanism for userspace programs. > Typical uprobe will incur overhead of two traps. > First trap is caused by replaced trap insn, and > the second trap is to execute the original displaced > insn in user

Re: [PATCH x86/urgent] bpf: emulate push insns for uprobe on x86

From: Yonghong Song Date: Wed, 8 Nov 2017 13:37:12 -0800 > Uprobe is a tracing mechanism for userspace programs. > Typical uprobe will incur overhead of two traps. > First trap is caused by replaced trap insn, and > the second trap is to execute the original displaced > insn in user space. ...

Re: n900 in next-20170901

On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171108 07:43]: > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > So it seems the issue is currently at the atomic_pool_init() > > > related code? > > > > Yes, your test

Re: n900 in next-20170901

On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171108 07:43]: > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > So it seems the issue is currently at the atomic_pool_init() > > > related code? > > > > Yes, your test showed it although I

Re: [PATCH 13/15] arm64: fix mrs_s/msr_s macros for clang LTO

> There's the series from Andi Kleen that enables LTO for Linux on x86: > https://lwn.net/Articles/512548/ > https://github.com/andikleen/linux-misc/tree/lto-411-1 > > It has solved many problems you also try to solve, and some patches > are looking very similar. > > At now we have different

Re: [PATCH 13/15] arm64: fix mrs_s/msr_s macros for clang LTO

> There's the series from Andi Kleen that enables LTO for Linux on x86: > https://lwn.net/Articles/512548/ > https://github.com/andikleen/linux-misc/tree/lto-411-1 > > It has solved many problems you also try to solve, and some patches > are looking very similar. > > At now we have different

Re: [PATCH AUTOSEL for-4.9 04/53] spi: imx: adjust watermark level according to transfer length

On Wed, Nov 08, 2017 at 11:11:11PM +, Mark Brown wrote: >On Wed, Nov 08, 2017 at 10:48:14PM +, Levin, Alexander (Sasha Levin) wrote: >> On Wed, Nov 08, 2017 at 10:11:02PM +, Mark Brown wrote: > >> >expose problems if we start using it. If you look at the history of the >> >driver

Re: [PATCH AUTOSEL for-4.9 04/53] spi: imx: adjust watermark level according to transfer length

On Wed, Nov 08, 2017 at 11:11:11PM +, Mark Brown wrote: >On Wed, Nov 08, 2017 at 10:48:14PM +, Levin, Alexander (Sasha Levin) wrote: >> On Wed, Nov 08, 2017 at 10:11:02PM +, Mark Brown wrote: > >> >expose problems if we start using it. If you look at the history of the >> >driver

Re: [RFC][PATCH] x86, sched: allow topolgies where NUMA nodes share an LLC

On 11/08/2017 01:31 AM, Peter Zijlstra wrote: > And SNC makes it even smaller; it effectively puts a cache in between > the two on-die nodes; not entirely unlike the s390 BOOK domain. Which > makes ignoring NUMA even more tempting. > > What does this topology approach do for those workloads?

Re: [RFC][PATCH] x86, sched: allow topolgies where NUMA nodes share an LLC

On 11/08/2017 01:31 AM, Peter Zijlstra wrote: > And SNC makes it even smaller; it effectively puts a cache in between > the two on-die nodes; not entirely unlike the s390 BOOK domain. Which > makes ignoring NUMA even more tempting. > > What does this topology approach do for those workloads?

[GIT PULL] timers-conversion updates for next (part 5)

Hi Thomas, Please pull these timer conversions for tip/timers/core. These are the last of the pre-rc1 changes. The rest of the changes are for late-rc1 (due to various tree dependencies). Following that are the tree-wide changes, and the API adjustments and removals. Thanks! -Kees The

[GIT PULL] timers-conversion updates for next (part 5)

Hi Thomas, Please pull these timer conversions for tip/timers/core. These are the last of the pre-rc1 changes. The rest of the changes are for late-rc1 (due to various tree dependencies). Following that are the tree-wide changes, and the API adjustments and removals. Thanks! -Kees The

Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license

On Tue, Nov 07, 2017 at 07:29:03PM +0100, Greg Kroah-Hartman wrote: > On Tue, Nov 07, 2017 at 09:20:42AM -0800, Darrick J. Wong wrote: > > On Tue, Nov 07, 2017 at 08:39:40AM +0100, Greg Kroah-Hartman wrote: > > > On Mon, Nov 06, 2017 at 11:20:40PM -0800, Christoph Hellwig wrote: > > > > NAK, for

Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license

On Tue, Nov 07, 2017 at 07:29:03PM +0100, Greg Kroah-Hartman wrote: > On Tue, Nov 07, 2017 at 09:20:42AM -0800, Darrick J. Wong wrote: > > On Tue, Nov 07, 2017 at 08:39:40AM +0100, Greg Kroah-Hartman wrote: > > > On Mon, Nov 06, 2017 at 11:20:40PM -0800, Christoph Hellwig wrote: > > > > NAK, for

Re: [RFC] hung task: check specific tasks for long uninterruptible sleep state

On Wed, 8 Nov 2017 20:57:42 +0900 Tetsuo Handa wrote: > Lingutla Chandrasekhar wrote: > > Some tasks may intentionally moves to uninterruptable sleep state, > > which shouldn't leads to khungtask panics, as those are recoverable > > hungs. So to avoid false

Re: [RFC] hung task: check specific tasks for long uninterruptible sleep state

On Wed, 8 Nov 2017 20:57:42 +0900 Tetsuo Handa wrote: > Lingutla Chandrasekhar wrote: > > Some tasks may intentionally moves to uninterruptable sleep state, > > which shouldn't leads to khungtask panics, as those are recoverable > > hungs. So to avoid false hung reports, add an option to select

Re: linux-next: build failure after merge of the kspp tree

On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell wrote: > Hi Kees, > > After merging the kspp tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/compiler_types.h:58:0, > from

Re: linux-next: build failure after merge of the kspp tree

On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell wrote: > Hi Kees, > > After merging the kspp tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/compiler_types.h:58:0, > from include/uapi/linux/stddef.h:2, >

Re: linux-next: build warning after merge of the netfilter-next tree

On Wed, Nov 08, 2017 at 07:00:52PM +1100, Stephen Rothwell wrote: > Hi Dave, > > On Tue, 7 Nov 2017 11:02:48 +1100 Stephen Rothwell > wrote: > > > > Hi all, > > > > After merging the netfilter-next tree, today's linux-next build (powerpc > > ppc64_defconfig) produced

Re: linux-next: build warning after merge of the netfilter-next tree

On Wed, Nov 08, 2017 at 07:00:52PM +1100, Stephen Rothwell wrote: > Hi Dave, > > On Tue, 7 Nov 2017 11:02:48 +1100 Stephen Rothwell > wrote: > > > > Hi all, > > > > After merging the netfilter-next tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > >

Re: [PATCH ALT4 V3 1/2] audit: show fstype:pathname for entries with anonymous parents

On Wednesday, September 20, 2017 12:52:32 PM EST Paul Moore wrote: > On Wed, Aug 23, 2017 at 7:03 AM, Richard Guy Briggs wrote: > > Tracefs or debugfs were causing hundreds to thousands of null PATH > > records to be associated with the init_module and finit_module SYSCALL > >

Re: [PATCH ALT4 V3 1/2] audit: show fstype:pathname for entries with anonymous parents

On Wednesday, September 20, 2017 12:52:32 PM EST Paul Moore wrote: > On Wed, Aug 23, 2017 at 7:03 AM, Richard Guy Briggs wrote: > > Tracefs or debugfs were causing hundreds to thousands of null PATH > > records to be associated with the init_module and finit_module SYSCALL > > records on a few

Re: [PATCH 0/3] zfcp: timer_setup() refactoring feature for v4.15-rc1

Kees, >> Kees Cook (1): >> zfcp: convert timers to use timer_setup() >> >> Steffen Maier (2): >> zfcp: purely mechanical update using timer API, plus blank lines >> zfcp: drop open coded assignments of timer_list.function > > These looks great, thanks! These look good to me too.

Re: [PATCH 0/3] zfcp: timer_setup() refactoring feature for v4.15-rc1

Kees, >> Kees Cook (1): >> zfcp: convert timers to use timer_setup() >> >> Steffen Maier (2): >> zfcp: purely mechanical update using timer API, plus blank lines >> zfcp: drop open coded assignments of timer_list.function > > These looks great, thanks! These look good to me too.

Re: [PATCH 8/9] ASoC: tlv320aic31xx: Fix the reset GPIO OF name

On 11/08/2017 04:18 PM, Mark Brown wrote: > On Wed, Nov 08, 2017 at 03:53:51PM -0600, Andrew F. Davis wrote: >> On 11/08/2017 03:36 PM, Mark Brown wrote: >>> On Wed, Nov 08, 2017 at 03:25:04PM -0600, Andrew F. Davis wrote: > >>> This is obviously an incompatible change in the binding which will

Re: [PATCH 8/9] ASoC: tlv320aic31xx: Fix the reset GPIO OF name

On 11/08/2017 04:18 PM, Mark Brown wrote: > On Wed, Nov 08, 2017 at 03:53:51PM -0600, Andrew F. Davis wrote: >> On 11/08/2017 03:36 PM, Mark Brown wrote: >>> On Wed, Nov 08, 2017 at 03:25:04PM -0600, Andrew F. Davis wrote: > >>> This is obviously an incompatible change in the binding which will

Re: [PATCH] pci: fix kernel-doc build warning

On Sun, Oct 29, 2017 at 05:07:11PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Fix build error in kernel-doc notation: > > ../drivers/pci/pci.c:3479: ERROR: Unexpected indentation. > > Signed-off-by: Randy Dunlap Applied to pci/misc for

Re: [Xen-devel] [PATCH] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute

Thanks Pasi for your response. Please see below for my comments. On 11/8/2017 11:38 AM, Pasi Kärkkäinen wrote: Hi, On Wed, Nov 08, 2017 at 09:44:48AM -0600, Govinda Tatti wrote: Thanks Jan for your review comments. Please see below for my comments. On 11/7/2017 8:40 AM, Jan Beulich wrote:

Re: [PATCH] pci: fix kernel-doc build warning

On Sun, Oct 29, 2017 at 05:07:11PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Fix build error in kernel-doc notation: > > ../drivers/pci/pci.c:3479: ERROR: Unexpected indentation. > > Signed-off-by: Randy Dunlap Applied to pci/misc for v4.15, thanks! > Cc: Bjorn Helgaas > Cc:

Re: [Xen-devel] [PATCH] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute

Thanks Pasi for your response. Please see below for my comments. On 11/8/2017 11:38 AM, Pasi Kärkkäinen wrote: Hi, On Wed, Nov 08, 2017 at 09:44:48AM -0600, Govinda Tatti wrote: Thanks Jan for your review comments. Please see below for my comments. On 11/7/2017 8:40 AM, Jan Beulich wrote:

[RFC PATCH v2 improved] ftrace: support very early function tracing

Hi Steve, here is the latest changes and fixes of v2, there are 3 points that still need to be fixed: 1) Use early boot timestamps : I removed arch specific code and use the default  clock. 2) Make filters depends on FTRACE_MCOUNT_RECORD instead of CONFIG_DYNAMIC_FTRACE, so we can use filtering

[RFC PATCH v2 improved] ftrace: support very early function tracing

Hi Steve, here is the latest changes and fixes of v2, there are 3 points that still need to be fixed: 1) Use early boot timestamps : I removed arch specific code and use the default  clock. 2) Make filters depends on FTRACE_MCOUNT_RECORD instead of CONFIG_DYNAMIC_FTRACE, so we can use filtering

linux-next: manual merge of the vfs tree with the overlayfs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/overlayfs/super.c between commits: 7c84d842e11e ("ovl: reduce the number of arguments for ovl_workdir_create()") 17d554474412 ("ovl: rename ufs to ofs") from the overlayfs tree and commit: c2c6773f9942 ("VFS: Roll

linux-next: manual merge of the vfs tree with the overlayfs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/overlayfs/super.c between commits: 7c84d842e11e ("ovl: reduce the number of arguments for ovl_workdir_create()") 17d554474412 ("ovl: rename ufs to ofs") from the overlayfs tree and commit: c2c6773f9942 ("VFS: Roll

[PATCH V2] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute

The life-cycle of a PCI device in Xen pciback is complex and is constrained by the generic PCI locking mechanism. - It starts with the device being bound to us, for which we do a function reset (done via SysFS so the PCI lock is held). - If the device is unbound from us, we also do a function

[PATCH V2] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute

The life-cycle of a PCI device in Xen pciback is complex and is constrained by the generic PCI locking mechanism. - It starts with the device being bound to us, for which we do a function reset (done via SysFS so the PCI lock is held). - If the device is unbound from us, we also do a function

Re: [PATCH AUTOSEL for-4.9 04/53] spi: imx: adjust watermark level according to transfer length

On Wed, Nov 08, 2017 at 10:48:14PM +, Levin, Alexander (Sasha Levin) wrote: > On Wed, Nov 08, 2017 at 10:11:02PM +, Mark Brown wrote: > >expose problems if we start using it. If you look at the history of the > >driver there's some quirks were added later on for example, and I didn't >

Re: [PATCH AUTOSEL for-4.9 04/53] spi: imx: adjust watermark level according to transfer length

On Wed, Nov 08, 2017 at 10:48:14PM +, Levin, Alexander (Sasha Levin) wrote: > On Wed, Nov 08, 2017 at 10:11:02PM +, Mark Brown wrote: > >expose problems if we start using it. If you look at the history of the > >driver there's some quirks were added later on for example, and I didn't >

Re: [PATCH] aacraid: use timespec64 instead of timeval

Arnd, > aacraid passes the current time to the firmware in one of two ways, > either as year/month/day/... or as 32-bit unsigned seconds. > > The first one is broken on 32-bit architectures as it cannot go past > year 2038. Using timespec64 here makes it behave properly on both > 32-bit and

Re: [PATCH] aacraid: use timespec64 instead of timeval

Arnd, > aacraid passes the current time to the firmware in one of two ways, > either as year/month/day/... or as 32-bit unsigned seconds. > > The first one is broken on 32-bit architectures as it cannot go past > year 2038. Using timespec64 here makes it behave properly on both > 32-bit and

Re: [GIT PULL] License cleanup: add SPDX license identifiers to some kernel files

On Thu, Nov 2, 2017 at 10:16 AM, Greg KH wrote: > [resend without the full diffstat as lkml and some email systems didn't > like to see emails with 12k lines...] > > Hi, > > As discussed at the Maintainers Summit last week, here is a pull request > that adds some SPDX

Re: [GIT PULL] License cleanup: add SPDX license identifiers to some kernel files

On Thu, Nov 2, 2017 at 10:16 AM, Greg KH wrote: > [resend without the full diffstat as lkml and some email systems didn't > like to see emails with 12k lines...] > > Hi, > > As discussed at the Maintainers Summit last week, here is a pull request > that adds some SPDX license identifiers to

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/super.c between commit: ea6767337f86 ("f2fs: support quota sys files") from the f2fs tree and commit: c2c6773f9942 ("VFS: Roll out mount flag differentiation (MS_* -> SB_*) generally") from the vfs tree. I

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/super.c between commit: ea6767337f86 ("f2fs: support quota sys files") from the f2fs tree and commit: c2c6773f9942 ("VFS: Roll out mount flag differentiation (MS_* -> SB_*) generally") from the vfs tree. I

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/checkpoint.c between commits: 1f227a3e215d ("f2fs: stop all the operations by cp_error flag") ea6767337f86 ("f2fs: support quota sys files") from the f2fs tree and commit: c2c6773f9942 ("VFS: Roll out mount

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/checkpoint.c between commits: 1f227a3e215d ("f2fs: stop all the operations by cp_error flag") ea6767337f86 ("f2fs: support quota sys files") from the f2fs tree and commit: c2c6773f9942 ("VFS: Roll out mount

linux-next: manual merge of the vfs tree with the ext3 tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/ext2/super.c between commits: 088519572ca8 ("ext2: Parse mount options into a dedicated structure") 8af634ff9e5c ("ext2: Fix possible sleep in atomic during mount option parsing") from the ext3 tree and commit:

linux-next: manual merge of the vfs tree with the ext3 tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/ext2/super.c between commits: 088519572ca8 ("ext2: Parse mount options into a dedicated structure") 8af634ff9e5c ("ext2: Fix possible sleep in atomic during mount option parsing") from the ext3 tree and commit:

Re: [PATCH 1/5] kobject: add SPDX identifiers to all kobject files

On Tue, Nov 7, 2017 at 10:30 AM, Greg Kroah-Hartman wrote: > It's good to have SPDX identifiers in all files to make it easier to > audit the kernel tree for correct licenses. > > Update the kobject files files with the correct SPDX license identifier > based on the

Re: [PATCH 1/5] kobject: add SPDX identifiers to all kobject files

On Tue, Nov 7, 2017 at 10:30 AM, Greg Kroah-Hartman wrote: > It's good to have SPDX identifiers in all files to make it easier to > audit the kernel tree for correct licenses. > > Update the kobject files files with the correct SPDX license identifier > based on the license text in the file

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