Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests

Le 18/02/2018 à 18:14, Horia Geantă a écrit : On 2/17/2018 6:32 PM, Christophe LEROY wrote: Le 07/02/2018 à 15:39, Horia Geantă a écrit : On 10/6/2017 4:06 PM, Christophe Leroy wrote: At every request, we map and unmap the same hash hw_context. This patch moves the dma mapping/unmapping

Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests

Le 18/02/2018 à 18:14, Horia Geantă a écrit : On 2/17/2018 6:32 PM, Christophe LEROY wrote: Le 07/02/2018 à 15:39, Horia Geantă a écrit : On 10/6/2017 4:06 PM, Christophe Leroy wrote: At every request, we map and unmap the same hash hw_context. This patch moves the dma mapping/unmapping

Re: [PATCH] auxdisplay: Replace licenses with SPDX identifiers

On Sat, Feb 17, 2018 at 8:39 PM, Miguel Ojeda wrote: > Signed-off-by: Miguel Ojeda For: > drivers/auxdisplay/hd44780.c| 6 +- Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s,

Re: [PATCH] auxdisplay: Replace licenses with SPDX identifiers

On Sat, Feb 17, 2018 at 8:39 PM, Miguel Ojeda wrote: > Signed-off-by: Miguel Ojeda For: > drivers/auxdisplay/hd44780.c| 6 +- Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

Re: [PATCH] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi Tony, I love your patch! Perhaps something to improve: [auto build test WARNING on phy/next] [also build test WARNING on v4.16-rc2 next-20180216] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4

Hi Tony, I love your patch! Perhaps something to improve: [auto build test WARNING on phy/next] [also build test WARNING on v4.16-rc2 next-20180216] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] ARM: dts: aspeed: Add LPC reset controller node

On both the ast2400 and ast2500 SoCs, the LPC reset controller is required to bring the UARTs out of reset without waiting for the LPC reset to be deasserted. Signed-off-by: Joel Stanley --- Bindings and driver change is under reivew: https://lkml.org/lkml/2018/2/19/12

[PATCH] ARM: dts: aspeed: Add LPC reset controller node

On both the ast2400 and ast2500 SoCs, the LPC reset controller is required to bring the UARTs out of reset without waiting for the LPC reset to be deasserted. Signed-off-by: Joel Stanley --- Bindings and driver change is under reivew: https://lkml.org/lkml/2018/2/19/12

Re: [PATCH v2 5/6] lightnvm: remove nvm_dev_ops->max_phys_sect

On 02/16/2018 07:48 AM, Javier Gonzalez wrote: On 15 Feb 2018, at 05.11, Matias Bjørling wrote: The value of max_phys_sect is always static. Instead of defining it in the nvm_dev_ops structure, declare it as a global value. Signed-off-by: Matias Bjørling

Re: [PATCH v2 5/6] lightnvm: remove nvm_dev_ops->max_phys_sect

On 02/16/2018 07:48 AM, Javier Gonzalez wrote: On 15 Feb 2018, at 05.11, Matias Bjørling wrote: The value of max_phys_sect is always static. Instead of defining it in the nvm_dev_ops structure, declare it as a global value. Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c

Re: [PATCH 2/8] lightnvm: show generic geometry in sysfs

On 02/16/2018 07:35 AM, Javier Gonzalez wrote: On 15 Feb 2018, at 02.20, Matias Bjørling wrote: On 02/13/2018 03:06 PM, Javier González wrote: From: Javier González Apart from showing the geometry returned by the different identify commands, provide

Re: [PATCH 2/8] lightnvm: show generic geometry in sysfs

On 02/16/2018 07:35 AM, Javier Gonzalez wrote: On 15 Feb 2018, at 02.20, Matias Bjørling wrote: On 02/13/2018 03:06 PM, Javier González wrote: From: Javier González Apart from showing the geometry returned by the different identify commands, provide the generic geometry too, as this is the

[PATCH v2] arm64: dts: rockchip: add OPPs for rk3368-lion

This adds CPU operation points for the RK3368. We only add them to the the RK3368-uQ7 SoM (Lion) because patches for the SoC where reverted in the past. commit 6354a06cbaa8 ("Revert "arm64: dts: rockchip: Add basic cpu frequencies for RK3368"") Signed-off-by: Klaus Goger

[PATCH v2] arm64: dts: rockchip: add OPPs for rk3368-lion

This adds CPU operation points for the RK3368. We only add them to the the RK3368-uQ7 SoM (Lion) because patches for the SoC where reverted in the past. commit 6354a06cbaa8 ("Revert "arm64: dts: rockchip: Add basic cpu frequencies for RK3368"") Signed-off-by: Klaus Goger ---

[PATCH v2 2/3] misc: aspeed-lpc: Request and enable LPC clock

The LPC device needs to ensure it's clock is enabled before it can do anything. In the past the clock was enabled and left running by u-boot, however Linux now has an upstream clock driver that disables unused clocks. Tested-by: Lei YU Reviewed-by: Andrew Jeffery

[PATCH v2 2/3] misc: aspeed-lpc: Request and enable LPC clock

The LPC device needs to ensure it's clock is enabled before it can do anything. In the past the clock was enabled and left running by u-boot, however Linux now has an upstream clock driver that disables unused clocks. Tested-by: Lei YU Reviewed-by: Andrew Jeffery Signed-off-by: Joel Stanley

[PATCH v2 1/3] dt-bindings: aspeed-lpc: Document LPC Host Interface Controller

The LPC Host Interface Controller is part of a BMC SoC that is used for communication with the host. Reviewed-by: Rob Herring Signed-off-by: Joel Stanley --- v2: - Move the content to below the Host Node Children heading - Add Rob's review tag ---

[PATCH v2 1/3] dt-bindings: aspeed-lpc: Document LPC Host Interface Controller

The LPC Host Interface Controller is part of a BMC SoC that is used for communication with the host. Reviewed-by: Rob Herring Signed-off-by: Joel Stanley --- v2: - Move the content to below the Host Node Children heading - Add Rob's review tag --- .../devicetree/bindings/mfd/aspeed-lpc.txt

[PATCH v2 3/3] misc: aspeed-lpc-ctrl: Enable FWH and A2H bridge cycles

To date this driver has relied on prevous state from out of tree hacks and vendor u-boot trees in order to have the host be able to access data over the LPC bus. Now we explicitly enable the AHB to LPC bridge and FWH cycles from when the user first configures the address to map. We chose to do

[PATCH v2 0/3] misc: aspeed-lpc-ctrl fixes

Hi Greg, Once Andrew has acked the bindings I think this is ready to go. v2: Fix binding layout and add Rob's ack These patches were developed when testing upstream Linux with OpenBMC on Romulus. We need to ensure the LPC clock is enabled, now that the clock driver turns off any unused clocks.

[PATCH v2 3/3] misc: aspeed-lpc-ctrl: Enable FWH and A2H bridge cycles

To date this driver has relied on prevous state from out of tree hacks and vendor u-boot trees in order to have the host be able to access data over the LPC bus. Now we explicitly enable the AHB to LPC bridge and FWH cycles from when the user first configures the address to map. We chose to do

[PATCH v2 0/3] misc: aspeed-lpc-ctrl fixes

Hi Greg, Once Andrew has acked the bindings I think this is ready to go. v2: Fix binding layout and add Rob's ack These patches were developed when testing upstream Linux with OpenBMC on Romulus. We need to ensure the LPC clock is enabled, now that the clock driver turns off any unused clocks.

Re: INFO: rcu detected stall in xfrm_confirm_neigh

On Tue, Feb 13, 2018 at 10:19:17AM +0100, Dmitry Vyukov wrote: > On Mon, Feb 12, 2018 at 4:26 PM, Dmitry Vyukov wrote: > > On Mon, Feb 12, 2018 at 4:23 PM, syzbot > > wrote: > >> Hello, > >> > >> syzbot hit the following

Re: INFO: rcu detected stall in xfrm_confirm_neigh

On Tue, Feb 13, 2018 at 10:19:17AM +0100, Dmitry Vyukov wrote: > On Mon, Feb 12, 2018 at 4:26 PM, Dmitry Vyukov wrote: > > On Mon, Feb 12, 2018 at 4:23 PM, syzbot > > wrote: > >> Hello, > >> > >> syzbot hit the following crash on net-next commit > >> 9515a2e082f91457db0ecff4b65371d0fb5d9aad (Thu

[PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

The cxlflash driver uses "Asynchronous SCSI scanning" enabled by CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash module gets hung with following backtrace: Call Trace: __switch_to+0x2cc/0x470 __schedule+0x288/0xab0 schedule+0x40/0xc0 schedule_timeout+0x254/0x4f0

[PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

The cxlflash driver uses "Asynchronous SCSI scanning" enabled by CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash module gets hung with following backtrace: Call Trace: __switch_to+0x2cc/0x470 __schedule+0x288/0xab0 schedule+0x40/0xc0 schedule_timeout+0x254/0x4f0

Re: 500 ms delay in time saved into RTC

On 2018-02-19 07:40, Igor Plyatov wrote: > Hi! > > I have board based on AT91SAM9G20 (ARM926EJ-S CPU), Linux-4.9.36 kernel > and RTC chip DS1340 (rtc-ds1307.c driver). > > RTC chip connected by means of I2C-bus, without HW IRQ line connected. > > Kernel configured to not use embedded functions

Re: 500 ms delay in time saved into RTC

On 2018-02-19 07:40, Igor Plyatov wrote: > Hi! > > I have board based on AT91SAM9G20 (ARM926EJ-S CPU), Linux-4.9.36 kernel > and RTC chip DS1340 (rtc-ds1307.c driver). > > RTC chip connected by means of I2C-bus, without HW IRQ line connected. > > Kernel configured to not use embedded functions

Re: iSCSI session logout regression after fbce4d97fd ("scsi: fixup kernel warning during rmmod()")

On 02/18/2018 07:33 PM, Max Ivanov wrote: > Hi, > > on my system I can't logout from iSCSI session when on 4.4.18, but > 4.3.19 works just fine. git bisect points to fbce4d97fd ("scsi: fixup > kernel warning during rmmod()") > > Bug manifests itself like following: > - iSCSI session logout

Re: iSCSI session logout regression after fbce4d97fd ("scsi: fixup kernel warning during rmmod()")

On 02/18/2018 07:33 PM, Max Ivanov wrote: > Hi, > > on my system I can't logout from iSCSI session when on 4.4.18, but > 4.3.19 works just fine. git bisect points to fbce4d97fd ("scsi: fixup > kernel warning during rmmod()") > > Bug manifests itself like following: > - iSCSI session logout

[PATCH 3/3] reset: simple: Allow user selection of driver

Currently this driver is only user selectable if COMPILE_TEST is turned on. Users may wish to select (and deselect) it, so remove this restriction. Signed-off-by: Joel Stanley --- drivers/reset/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/3] reset: simple: Enable for ASPEED systems

ASPEED BMC SoCs have a reset controller in the LPC IP that can be controlled using this driver to release the UARTs from reset. No special configuration is required, so only the compatible string is added. Signed-off-by: Joel Stanley --- drivers/reset/Kconfig| 10

[PATCH 2/3] reset: simple: Enable for ASPEED systems

ASPEED BMC SoCs have a reset controller in the LPC IP that can be controlled using this driver to release the UARTs from reset. No special configuration is required, so only the compatible string is added. Signed-off-by: Joel Stanley --- drivers/reset/Kconfig| 10 +++---

[PATCH 3/3] reset: simple: Allow user selection of driver

Currently this driver is only user selectable if COMPILE_TEST is turned on. Users may wish to select (and deselect) it, so remove this restriction. Signed-off-by: Joel Stanley --- drivers/reset/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/reset/Kconfig

[PATCH 0/3] reset: simple: enable for ASPEED SoCs

Hello Philip, Here is a series that enables the simple reset driver for the ASPEED SoCs. You may recall I posted a patch back in May 2017 with a similar idea[1]. I was happy to see that you merged a driver that solves the problem, and suits our purpose for the ASPEED. Thanks! Cheers, Joel [1]

[PATCH 0/3] reset: simple: enable for ASPEED SoCs

Hello Philip, Here is a series that enables the simple reset driver for the ASPEED SoCs. You may recall I posted a patch back in May 2017 with a similar idea[1]. I was happy to see that you merged a driver that solves the problem, and suits our purpose for the ASPEED. Thanks! Cheers, Joel [1]

[PATCH 1/3] dt-bindings: aspeed-lpc: Add reset controller

This describes the reset controller present in the LPC address space. Signed-off-by: Joel Stanley --- .../devicetree/bindings/mfd/aspeed-lpc.txt | 21 + 1 file changed, 21 insertions(+) diff --git

[PATCH 1/3] dt-bindings: aspeed-lpc: Add reset controller

This describes the reset controller present in the LPC address space. Signed-off-by: Joel Stanley --- .../devicetree/bindings/mfd/aspeed-lpc.txt | 21 + 1 file changed, 21 insertions(+) diff --git a/Documentation/devicetree/bindings/mfd/aspeed-lpc.txt

Re: [PATCH 1/2] ASoC: topology: Rename clock_gated to clock_cont in snd_soc_tplg_hw_config

Hi, On Feb 19 2018 15:05, Kirill Marinushkin wrote: In kernel `soc-dai.h`, DAI clock gating is defined as following: \#define SND_SOC_DAIFMT_CONT(1 << 4) /* continuous clock */ \#define SND_SOC_DAIFMT_GATED (0 << 4) /* clock is gated */ Therefore, the

Re: [PATCH 1/2] ASoC: topology: Rename clock_gated to clock_cont in snd_soc_tplg_hw_config

Hi, On Feb 19 2018 15:05, Kirill Marinushkin wrote: In kernel `soc-dai.h`, DAI clock gating is defined as following: \#define SND_SOC_DAIFMT_CONT(1 << 4) /* continuous clock */ \#define SND_SOC_DAIFMT_GATED (0 << 4) /* clock is gated */ Therefore, the

500 ms delay in time saved into RTC

Hi! I have board based on AT91SAM9G20 (ARM926EJ-S CPU), Linux-4.9.36 kernel and RTC chip DS1340 (rtc-ds1307.c driver). RTC chip connected by means of I2C-bus, without HW IRQ line connected. Kernel configured to not use embedded functions for time getting at startup and saving at shutdown:

500 ms delay in time saved into RTC

Hi! I have board based on AT91SAM9G20 (ARM926EJ-S CPU), Linux-4.9.36 kernel and RTC chip DS1340 (rtc-ds1307.c driver). RTC chip connected by means of I2C-bus, without HW IRQ line connected. Kernel configured to not use embedded functions for time getting at startup and saving at shutdown:

[PATCH] arm64: Fix compilation error while accessing MPIDR_HWID_BITMASK from .S files

Since commit e1a50de37860b3a93a9d643b09638db5aff47650 (arm64: cputype: Silence Sparse warnings), compilation of arm64 architecture is broken with the following error messages: AR arch/arm64/kernel/built-in.o arch/arm64/kernel/head.S: Assembler messages: arch/arm64/kernel/head.S:677:

[PATCH] arm64: Fix compilation error while accessing MPIDR_HWID_BITMASK from .S files

Since commit e1a50de37860b3a93a9d643b09638db5aff47650 (arm64: cputype: Silence Sparse warnings), compilation of arm64 architecture is broken with the following error messages: AR arch/arm64/kernel/built-in.o arch/arm64/kernel/head.S: Assembler messages: arch/arm64/kernel/head.S:677:

Re: [PATCH 1/1] scsi: ufs: Add support for Auto-Hibernate Idle Timer

On 18/02/18 11:45, Avri Altman wrote: > > >> -Original Message- >> From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi- >> ow...@vger.kernel.org] On Behalf Of Adrian Hunter >> Sent: Friday, February 16, 2018 2:01 PM >> To: Vinayak Holikatti ; Martin K.

Re: [PATCH 1/1] scsi: ufs: Add support for Auto-Hibernate Idle Timer

On 18/02/18 11:45, Avri Altman wrote: > > >> -Original Message- >> From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi- >> ow...@vger.kernel.org] On Behalf Of Adrian Hunter >> Sent: Friday, February 16, 2018 2:01 PM >> To: Vinayak Holikatti ; Martin K. Petersen >> ; James E.J.

Re: [PATCH] ASoC: Intel: Skylake: Fix compiler warning -Wmaybe-uninitialized

Hi, On Feb 19 2018 15:02, Kirill Marinushkin wrote: Configuration: SND_SOC_INTEL_SKYLAKE=y PM_SLEEP=y Warning message: sound/soc/intel/skylake/skl.c: In function 'skl_resume': sound/soc/intel/skylake/skl.c:326:6: warning: 'ret' may be used uninitialized in this function

Re: [PATCH] ASoC: Intel: Skylake: Fix compiler warning -Wmaybe-uninitialized

Hi, On Feb 19 2018 15:02, Kirill Marinushkin wrote: Configuration: SND_SOC_INTEL_SKYLAKE=y PM_SLEEP=y Warning message: sound/soc/intel/skylake/skl.c: In function 'skl_resume': sound/soc/intel/skylake/skl.c:326:6: warning: 'ret' may be used uninitialized in this function

Re: [PATCH v3 4/4] of: improve reporting invalid overlay target path

On 02/18/18 19:21, Rob Herring wrote: > On Wed, Feb 14, 2018 at 09:35:46PM -0800, frowand.l...@gmail.com wrote: >> From: Frank Rowand >> >> Errors while developing the patch to create of_overlay_fdt_apply() >> exposed inadequate error messages to debug problems when overlay

Re: [PATCH v3 4/4] of: improve reporting invalid overlay target path

On 02/18/18 19:21, Rob Herring wrote: > On Wed, Feb 14, 2018 at 09:35:46PM -0800, frowand.l...@gmail.com wrote: >> From: Frank Rowand >> >> Errors while developing the patch to create of_overlay_fdt_apply() >> exposed inadequate error messages to debug problems when overlay >> devicetree fragment

Re: [PATCH] of: Kconfig: OF_OVERLAY, select OF_EARLY_FLATTREE

On 02/18/18 17:46, Rob Herring wrote: > On Sun, Feb 18, 2018 at 6:29 PM, wrote: >> From: Frank Rowand >> >> kbuild test robot reported a new warning for a recent patch: drivers/of/overlay.c:832:2: error: implicit declaration of function

Re: [PATCH] of: Kconfig: OF_OVERLAY, select OF_EARLY_FLATTREE

On 02/18/18 17:46, Rob Herring wrote: > On Sun, Feb 18, 2018 at 6:29 PM, wrote: >> From: Frank Rowand >> >> kbuild test robot reported a new warning for a recent patch: drivers/of/overlay.c:832:2: error: implicit declaration of function 'of_fdt_unflatten_tree'

[PATCH 2/2] ASoC: topology: Add missing clock gating parameter when parsing hw_configs

Clock gating parameter is a part of `dai_fmt`. It is supported by `alsa-lib` when creating a topology binary file, but ignored by kernel when loading this topology file. After applying this commit, the clock gating parameter is not ignored any more. The old behaviour is not broken, as by default

[PATCH 2/2] ASoC: topology: Add missing clock gating parameter when parsing hw_configs

Clock gating parameter is a part of `dai_fmt`. It is supported by `alsa-lib` when creating a topology binary file, but ignored by kernel when loading this topology file. After applying this commit, the clock gating parameter is not ignored any more. The old behaviour is not broken, as by default

[PATCH 1/2] ASoC: topology: Rename clock_gated to clock_cont in snd_soc_tplg_hw_config

In kernel `soc-dai.h`, DAI clock gating is defined as following: \#define SND_SOC_DAIFMT_CONT(1 << 4) /* continuous clock */ \#define SND_SOC_DAIFMT_GATED (0 << 4) /* clock is gated */ Therefore, the corresponding field of struct snd_soc_tplg_hw_config should be

[PATCH 1/2] ASoC: topology: Rename clock_gated to clock_cont in snd_soc_tplg_hw_config

In kernel `soc-dai.h`, DAI clock gating is defined as following: \#define SND_SOC_DAIFMT_CONT(1 << 4) /* continuous clock */ \#define SND_SOC_DAIFMT_GATED (0 << 4) /* clock is gated */ Therefore, the corresponding field of struct snd_soc_tplg_hw_config should be

[PATCH] ASoC: Intel: Skylake: Fix compiler warning -Wmaybe-uninitialized

Configuration: SND_SOC_INTEL_SKYLAKE=y PM_SLEEP=y Warning message: sound/soc/intel/skylake/skl.c: In function 'skl_resume': sound/soc/intel/skylake/skl.c:326:6: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] int ret; ^~~ Fixes: 4557c305d4fc ("ASoC:

[PATCH] ASoC: Intel: Skylake: Fix compiler warning -Wmaybe-uninitialized

Configuration: SND_SOC_INTEL_SKYLAKE=y PM_SLEEP=y Warning message: sound/soc/intel/skylake/skl.c: In function 'skl_resume': sound/soc/intel/skylake/skl.c:326:6: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] int ret; ^~~ Fixes: 4557c305d4fc ("ASoC:

Re: [PATCH v4] perf ftrace: Append an EOL when write tracing files

On Mon, Feb 19, 2018 at 10:33:29AM +0800, changbin...@intel.com wrote: > From: Changbin Du > > Before this change, the '--graph-funcs', '--nograph-funcs' and > '--trace-funcs' options didn't work as expected when the doesn't > exist. Because the kernel side hid possible

Re: [PATCH v4] perf ftrace: Append an EOL when write tracing files

On Mon, Feb 19, 2018 at 10:33:29AM +0800, changbin...@intel.com wrote: > From: Changbin Du > > Before this change, the '--graph-funcs', '--nograph-funcs' and > '--trace-funcs' options didn't work as expected when the doesn't > exist. Because the kernel side hid possible errors. > > $ sudo

Re: [PATCH 1/3] tools include powerpc: Grab a copy of arch/powerpc/include/uapi/asm/unistd.h

Arnaldo Carvalho de Melo writes: > Em Fri, Feb 16, 2018 at 02:29:01PM -0300, Arnaldo Carvalho de Melo escreveu: >> Humm, we need to create two tables, one for 32-bit and another for 64, >> even with ppc not having (AFAIK) clashes in syscall numbers for 32/64... >> >> Trying to

Re: [PATCH 11/23] kconfig: add 'shell-stdout' function

On Fri, Feb 16, 2018 at 11:17:52AM -0800, Linus Torvalds wrote: > On Fri, Feb 16, 2018 at 10:38 AM, Masahiro Yamada > wrote: > > This is the second built-in function, which retrieves the first line > > of stdout from the given shell command. > > This is the only

Re: [PATCH 1/3] tools include powerpc: Grab a copy of arch/powerpc/include/uapi/asm/unistd.h

Arnaldo Carvalho de Melo writes: > Em Fri, Feb 16, 2018 at 02:29:01PM -0300, Arnaldo Carvalho de Melo escreveu: >> Humm, we need to create two tables, one for 32-bit and another for 64, >> even with ppc not having (AFAIK) clashes in syscall numbers for 32/64... >> >> Trying to do it now. > >

Re: [PATCH 11/23] kconfig: add 'shell-stdout' function

On Fri, Feb 16, 2018 at 11:17:52AM -0800, Linus Torvalds wrote: > On Fri, Feb 16, 2018 at 10:38 AM, Masahiro Yamada > wrote: > > This is the second built-in function, which retrieves the first line > > of stdout from the given shell command. > > This is the only part I really don't much like in

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

On 2/19/2018 5:02 AM, Stephen Rothwell wrote: Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: sound/soc/amd/acp-da7219-max98357a.c: In function 'cz_da7219_init': sound/soc/amd/acp-da7219-max98357a.c:79:22: error: passing argument 1

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

On 2/19/2018 5:02 AM, Stephen Rothwell wrote: Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: sound/soc/amd/acp-da7219-max98357a.c: In function 'cz_da7219_init': sound/soc/amd/acp-da7219-max98357a.c:79:22: error: passing argument 1

[PATCH 4/4 v2] ASoC: ak5558: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Note: xxx_codec_xxx() -> xxx_component_xxx() .idle_bias_off = 0 -> .idle_bias_on = 1 .ignore_pmdown_time = 0 -> .use_pmdown_time = 1

[PATCH 4/4 v2] ASoC: ak5558: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Note: xxx_codec_xxx() -> xxx_component_xxx() .idle_bias_off = 0 -> .idle_bias_on = 1 .ignore_pmdown_time = 0 -> .use_pmdown_time = 1 -

[PATCH 3/4 v2] ASoC: ak4458: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Note: xxx_codec_xxx() -> xxx_component_xxx() .idle_bias_off = 0 -> .idle_bias_on = 1 .ignore_pmdown_time = 0 -> .use_pmdown_time = 1

[PATCH 3/4 v2] ASoC: ak4458: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Note: xxx_codec_xxx() -> xxx_component_xxx() .idle_bias_off = 0 -> .idle_bias_on = 1 .ignore_pmdown_time = 0 -> .use_pmdown_time = 1 -

[PATCH 2/4 v2] ASoC: amd: acp-da7219-max98357: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - no change sound/soc/amd/acp-da7219-max98357a.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 2/4 v2] ASoC: amd: acp-da7219-max98357: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - no change sound/soc/amd/acp-da7219-max98357a.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/soc/amd/acp-da7219-max98357a.c

[PATCH 1/4 v2] ASoC: intel: kbl_da7219_max98357: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - no change sound/soc/intel/boards/kbl_da7219_max98357a.c | 12 ++-- 1 file changed, 6

[PATCH 1/4 v2] ASoC: intel: kbl_da7219_max98357: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - no change sound/soc/intel/boards/kbl_da7219_max98357a.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[PATCH 0/4 v2] ASoC: missing replace codec to component

Hi Mark These are v2 of replace patch for new added driver on mark/for-next branch. The diff v1 -> v2 is that compile warning issue was solved on ak driver Kuninori Morimoto (4): ASoC: intel: kbl_da7219_max98357: replace codec to component ASoC: amd: acp-da7219-max98357: replace codec to

[PATCH 0/4 v2] ASoC: missing replace codec to component

Hi Mark These are v2 of replace patch for new added driver on mark/for-next branch. The diff v1 -> v2 is that compile warning issue was solved on ak driver Kuninori Morimoto (4): ASoC: intel: kbl_da7219_max98357: replace codec to component ASoC: amd: acp-da7219-max98357: replace codec to

Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Anshuman-Khandual/lib-scatterlist-Add-SG_CHAIN-and-SG_END-macros-for-LSB-encodings/20180218-015554 > config: x86_64-randconfig-s3-02180201 (attached as .config) >

Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Anshuman-Khandual/lib-scatterlist-Add-SG_CHAIN-and-SG_END-macros-for-LSB-encodings/20180218-015554 > config: x86_64-randconfig-s3-02180201 (attached as .config) >

Re: [PATCH] cpufreq: s3c24xx: Delete an error message for a failed memory allocation in two functions

On 15-02-18, 17:40, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 17:28:40 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > >

Re: [PATCH] cpufreq: s3c24xx: Delete an error message for a failed memory allocation in two functions

On 15-02-18, 17:40, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 17:28:40 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- >

Re: [PATCH] cpufreq: qoriq: Delete two error messages for a failed memory allocation in qoriq_cpufreq_cpu_init()

On 15-02-18, 18:08, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 18:00:37 +0100 > > Omit extra messages for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by:

Re: [PATCH] cpufreq: qoriq: Delete two error messages for a failed memory allocation in qoriq_cpufreq_cpu_init()

On 15-02-18, 18:08, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 18:00:37 +0100 > > Omit extra messages for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- >

Re: [PATCH 2/2] cpufreq: powernow-k8: Delete an unnecessary return statement in two functions

On 15-02-18, 20:30, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 20:14:32 +0100 > > The script "checkpatch.pl" pointed information out like the following. > > WARNING: void function return statements are not generally useful > > Thus

Re: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties

On 18-02-18, 17:29, Rob Herring wrote: > On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote: > > The "cooling-min-level" and "cooling-max-level" properties are not > > parsed by any part of kernel currently and the max cooling state of a > > CPU cooling device is found by referring to

Re: [PATCH 2/2] cpufreq: powernow-k8: Delete an unnecessary return statement in two functions

On 15-02-18, 20:30, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 20:14:32 +0100 > > The script "checkpatch.pl" pointed information out like the following. > > WARNING: void function return statements are not generally useful > > Thus remove such a statement in the

Re: [PATCH 10/10] dt-bindings: thermal: Remove "cooling-{min|max}-level" properties

On 18-02-18, 17:29, Rob Herring wrote: > On Fri, Feb 09, 2018 at 02:28:10PM +0530, Viresh Kumar wrote: > > The "cooling-min-level" and "cooling-max-level" properties are not > > parsed by any part of kernel currently and the max cooling state of a > > CPU cooling device is found by referring to

Re: [PATCH 1/2] cpufreq: powernow-k8: Delete an error message for a failed memory allocation in three functions

On 15-02-18, 20:29, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 20:00:23 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > >

Re: [PATCH 1/2] cpufreq: powernow-k8: Delete an error message for a failed memory allocation in three functions

On 15-02-18, 20:29, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 15 Feb 2018 20:00:23 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- >

Re: [PATCH 1/3] pata_arasan_cf: Delete an error message for a failed memory allocation in arasan_cf_probe()

On 16-02-18, 16:57, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 16 Feb 2018 16:01:12 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > >

Re: [PATCH 1/3] pata_arasan_cf: Delete an error message for a failed memory allocation in arasan_cf_probe()

On 16-02-18, 16:57, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 16 Feb 2018 16:01:12 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- >

Re: [PATCH v3 06/15] arm64: dts: mt7622: add cpufreq related device nodes

On 18-02-18, 03:54, sean.w...@mediatek.com wrote: > From: Sean Wang > > Add clocks, regulators and opp information into cpu nodes. > In addition, the power supply for cpu nodes is deployed on > mt7622-rfb1 board. > > Signed-off-by: Sean Wang >

Re: [PATCH v3 06/15] arm64: dts: mt7622: add cpufreq related device nodes

On 18-02-18, 03:54, sean.w...@mediatek.com wrote: > From: Sean Wang > > Add clocks, regulators and opp information into cpu nodes. > In addition, the power supply for cpu nodes is deployed on > mt7622-rfb1 board. > > Signed-off-by: Sean Wang > Cc: Viresh Kumar > --- >

Re: [PATCH v3 4/4] of: improve reporting invalid overlay target path

On Wed, Feb 14, 2018 at 09:35:46PM -0800, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Errors while developing the patch to create of_overlay_fdt_apply() > exposed inadequate error messages to debug problems when overlay > devicetree fragment nodes contain an

Re: [PATCH v3 4/4] of: improve reporting invalid overlay target path

On Wed, Feb 14, 2018 at 09:35:46PM -0800, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Errors while developing the patch to create of_overlay_fdt_apply() > exposed inadequate error messages to debug problems when overlay > devicetree fragment nodes contain an invalid target path.

Re: [PATCH v2] serial: 8250: Add Nuvoton NPCM UART

On Thu, Feb 15, 2018 at 12:47:20PM +1030, Joel Stanley wrote: > The Nuvoton UART is almost compatible with the 8250 driver when probed > via the 8250_of driver, however it requires some extra configuration > at startup. > > Signed-off-by: Joel Stanley > --- > v2: > Remove

Re: [PATCH v2] serial: 8250: Add Nuvoton NPCM UART

On Thu, Feb 15, 2018 at 12:47:20PM +1030, Joel Stanley wrote: > The Nuvoton UART is almost compatible with the 8250 driver when probed > via the 8250_of driver, however it requires some extra configuration > at startup. > > Signed-off-by: Joel Stanley > --- > v2: > Remove redundant whitespace >

Re: [PATCH] kbuild: Don't source kernel config

Hi Richard, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180216] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] kbuild: Don't source kernel config

Hi Richard, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180216] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 2/2] mfd: arizona: Update DT doc to support more standard reset binding

On Wed, Feb 14, 2018 at 03:55:12PM +, Charles Keepax wrote: > Signed-off-by: Charles Keepax > --- > Documentation/devicetree/bindings/mfd/arizona.txt | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git

Re: [PATCH 2/2] mfd: arizona: Update DT doc to support more standard reset binding

On Wed, Feb 14, 2018 at 03:55:12PM +, Charles Keepax wrote: > Signed-off-by: Charles Keepax > --- > Documentation/devicetree/bindings/mfd/arizona.txt | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt >

  1   2   3   4   5   6   >