Re: [PATCH v5 0/6] IR support for A83T

Hi Philipp, On Mon, Feb 12, 2018 at 12:00:02PM +0100, Philipp Rossak wrote: > On 30.01.2018 18:46, Philipp Rossak wrote: > > This patch series adds support for the sunxi A83T ir module and enhances > > the sunxi-ir driver. Right now the base clock frequency for the ir driver > > is a hard coded

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

* David Woodhouse wrote: > On Mon, 2018-02-12 at 12:50 +0100, Peter Zijlstra wrote: > > On Mon, Feb 12, 2018 at 11:22:11AM +0100, Ingo Molnar wrote: > > > > +static inline void firmware_restrict_branch_speculation_start(void) > > > > +{ > > > > +   

Re: [PATCH v5 0/6] IR support for A83T

Hi Philipp, On Mon, Feb 12, 2018 at 12:00:02PM +0100, Philipp Rossak wrote: > On 30.01.2018 18:46, Philipp Rossak wrote: > > This patch series adds support for the sunxi A83T ir module and enhances > > the sunxi-ir driver. Right now the base clock frequency for the ir driver > > is a hard coded

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

* David Woodhouse wrote: > On Mon, 2018-02-12 at 12:50 +0100, Peter Zijlstra wrote: > > On Mon, Feb 12, 2018 at 11:22:11AM +0100, Ingo Molnar wrote: > > > > +static inline void firmware_restrict_branch_speculation_start(void) > > > > +{ > > > > +   alternative_msr_write(MSR_IA32_SPEC_CTRL,

[PATCH v2] Makefile: Fix lying comment re. silentoldconfig

The comment above the silentoldconfig invocation is outdated. 'make oldconfig' updates just .config and doesn't touch the include/config/ tree. This came up in https://lkml.org/lkml/2018/2/12/415. While fixing the comment, make it more informative by explaining the purpose of the unfortunately

[PATCH v2] Makefile: Fix lying comment re. silentoldconfig

The comment above the silentoldconfig invocation is outdated. 'make oldconfig' updates just .config and doesn't touch the include/config/ tree. This came up in https://lkml.org/lkml/2018/2/12/415. While fixing the comment, make it more informative by explaining the purpose of the unfortunately

Re: [PATCH] vsprintf: replace space with readable '=' before crng is ready

Hi, Rasmus, On Tue, 2018-02-13 at 08:16 +0100, Rasmus Villemoes wrote: > On 13 February 2018 at 07:20, Shunyong Yang > wrote: > > > > > > > This patch replaces space with readable "=" when output needs > > padding. > > Following is the output after applying the

Re: [PATCH] vsprintf: replace space with readable '=' before crng is ready

Hi, Rasmus, On Tue, 2018-02-13 at 08:16 +0100, Rasmus Villemoes wrote: > On 13 February 2018 at 07:20, Shunyong Yang > wrote: > > > > > > > This patch replaces space with readable "=" when output needs > > padding. > > Following is the output after applying the patch, > > > > Suggested-by:

Re: [PATCH v7 00/24] Speculative page faults

On 08/02/2018 21:53, Andrew Morton wrote: > On Tue, 6 Feb 2018 17:49:46 +0100 Laurent Dufour > wrote: > >> This is a port on kernel 4.15 of the work done by Peter Zijlstra to >> handle page fault without holding the mm semaphore [1]. >> >> The idea is to try to

Re: [PATCH v7 00/24] Speculative page faults

On 08/02/2018 21:53, Andrew Morton wrote: > On Tue, 6 Feb 2018 17:49:46 +0100 Laurent Dufour > wrote: > >> This is a port on kernel 4.15 of the work done by Peter Zijlstra to >> handle page fault without holding the mm semaphore [1]. >> >> The idea is to try to handle user space page faults

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

* Peter Zijlstra wrote: > On Mon, Feb 12, 2018 at 08:13:31AM -0800, Dave Hansen wrote: > > On 02/12/2018 02:22 AM, Ingo Molnar wrote: > > >> +static inline void firmware_restrict_branch_speculation_end(void) > > >> +{ > > >> +

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

* Peter Zijlstra wrote: > On Mon, Feb 12, 2018 at 08:13:31AM -0800, Dave Hansen wrote: > > On 02/12/2018 02:22 AM, Ingo Molnar wrote: > > >> +static inline void firmware_restrict_branch_speculation_end(void) > > >> +{ > > >> +alternative_msr_write(MSR_IA32_SPEC_CTRL, 0, > > >> +

Re: [PATCH 14/14] x86/crypto: aesni: Update aesni-intel_glue to use scatter/gather

Am Montag, 12. Februar 2018, 20:51:28 CET schrieb Dave Watson: Hi Dave, > Add gcmaes_en/decrypt_sg routines, that will do scatter/gather > by sg. Either src or dst may contain multiple buffers, so > iterate over both at the same time if they are different. > If the input is the same as the

Re: [PATCH 14/14] x86/crypto: aesni: Update aesni-intel_glue to use scatter/gather

Am Montag, 12. Februar 2018, 20:51:28 CET schrieb Dave Watson: Hi Dave, > Add gcmaes_en/decrypt_sg routines, that will do scatter/gather > by sg. Either src or dst may contain multiple buffers, so > iterate over both at the same time if they are different. > If the input is the same as the

Re: [PATCH 2/2] x86/speculation: Support "Enhanced IBRS" on future CPUs

* David Woodhouse wrote: > +extern enum spectre_v2_mitigation spectre_v2_enabled; This needs to be exported if the KVM module wants to use it. > +static inline bool spectre_v2_ibrs_all(void) > +{ > + return spectre_v2_enabled == SPECTRE_V2_IBRS_ALL; > +} > + if

Re: [PATCH 2/2] x86/speculation: Support "Enhanced IBRS" on future CPUs

* David Woodhouse wrote: > +extern enum spectre_v2_mitigation spectre_v2_enabled; This needs to be exported if the KVM module wants to use it. > +static inline bool spectre_v2_ibrs_all(void) > +{ > + return spectre_v2_enabled == SPECTRE_V2_IBRS_ALL; > +} > + if (vmx->spec_ctrl &&

Re: [PATCH v7 1/6] base: power: runtime: Export pm_runtime_get/put_suppliers

Hi Vivek, On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam wrote: > The device link allows the pm framework to tie the supplier and > consumer. So, whenever the consumer is powered-on the supplier > is powered-on first. > > There are however cases in which the consumer

Re: [PATCH v7 1/6] base: power: runtime: Export pm_runtime_get/put_suppliers

Hi Vivek, On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam wrote: > The device link allows the pm framework to tie the supplier and > consumer. So, whenever the consumer is powered-on the supplier > is powered-on first. > > There are however cases in which the consumer wants to power-on > the

[PATCH] Makefile: Fix lying comment re. silentoldconfig

The comment above the silentoldconfig invocation is outdated. 'make oldconfig' updates just .config and doesn't touch the include/config/ tree. This came up in https://lkml.org/lkml/2018/2/12/415. While fixing the comment, make it more informative by explaining the purpose of the unfortunately

[PATCH] Makefile: Fix lying comment re. silentoldconfig

The comment above the silentoldconfig invocation is outdated. 'make oldconfig' updates just .config and doesn't touch the include/config/ tree. This came up in https://lkml.org/lkml/2018/2/12/415. While fixing the comment, make it more informative by explaining the purpose of the unfortunately

Re: [PATCH v3 2/5] x86/apic: Fix restoring boot irq mode in reboot and kexec/kdump

Hi Eric, On 02/11/18 at 09:08pm, Eric W. Biederman wrote: > Baoquan He writes: > > > This is a regression fix. > > > > Before, to fix erratum AVR31, commit 522e66464467 ("x86/apic: Disable > > I/O APIC before shutdown of the local APIC") moved lapic_shutdown() > > calling after

Re: [PATCH v3 2/5] x86/apic: Fix restoring boot irq mode in reboot and kexec/kdump

Hi Eric, On 02/11/18 at 09:08pm, Eric W. Biederman wrote: > Baoquan He writes: > > > This is a regression fix. > > > > Before, to fix erratum AVR31, commit 522e66464467 ("x86/apic: Disable > > I/O APIC before shutdown of the local APIC") moved lapic_shutdown() > > calling after

Re: KASAN: use-after-free Read in remove_wait_queue

On Mon, Feb 12, 2018 at 7:31 PM, Al Viro wrote: > Any chance of bisecting it? Perhaps my fix introduced another (related) problem, I'm looking into it.

Re: KASAN: use-after-free Read in remove_wait_queue

On Mon, Feb 12, 2018 at 7:31 PM, Al Viro wrote: > Any chance of bisecting it? Perhaps my fix introduced another (related) problem, I'm looking into it.

Re: [PATCH v3 1/2] drm/virtio: Add window server support

On Mon, 12 Feb 2018 12:45:40 +0100 Gerd Hoffmann wrote: > Hi, > > > >(a) software rendering: client allocates shared memory buffer, renders > > >into it, then passes a file handle for that shmem block together > > >with some meta data (size, format, ...)

Re: [PATCH v3 1/2] drm/virtio: Add window server support

On Mon, 12 Feb 2018 12:45:40 +0100 Gerd Hoffmann wrote: > Hi, > > > >(a) software rendering: client allocates shared memory buffer, renders > > >into it, then passes a file handle for that shmem block together > > >with some meta data (size, format, ...) to the wayland

Re: [PATCH] x86/entry/64: Remove unused icebp macro

* Borislav Petkov wrote: > On Mon, Feb 12, 2018 at 02:18:55AM -0800, tip-bot for Dominik Brodowski wrote: > > Commit-ID: 5a10e729bc0aa9420a23a70b169eadd229c27bc1 > > Gitweb: > > https://git.kernel.org/tip/5a10e729bc0aa9420a23a70b169eadd229c27bc1 > > Author: Dominik

Re: [PATCH v3 1/2] dt-bindings: gpio: Add Spreadtrum GPIO controller documentation

On Mon, Feb 5, 2018 at 2:55 AM, Baolin Wang wrote: > This patch adds the device tree bindings for the Spreadtrum > GPIO controller. The gpios will be supported by the GPIO > generic library. > > Signed-off-by: Baolin Wang Patch applied with Rob's

Re: [PATCH] x86/entry/64: Remove unused icebp macro

* Borislav Petkov wrote: > On Mon, Feb 12, 2018 at 02:18:55AM -0800, tip-bot for Dominik Brodowski wrote: > > Commit-ID: 5a10e729bc0aa9420a23a70b169eadd229c27bc1 > > Gitweb: > > https://git.kernel.org/tip/5a10e729bc0aa9420a23a70b169eadd229c27bc1 > > Author: Dominik Brodowski > >

Re: [PATCH v3 1/2] dt-bindings: gpio: Add Spreadtrum GPIO controller documentation

On Mon, Feb 5, 2018 at 2:55 AM, Baolin Wang wrote: > This patch adds the device tree bindings for the Spreadtrum > GPIO controller. The gpios will be supported by the GPIO > generic library. > > Signed-off-by: Baolin Wang Patch applied with Rob's ACK from v2. Yours, Linus Walleij

Re: [PATCH] m68k/mm: Stop printing the virtual memory layout

Hi Finn, On Tue, Feb 13, 2018 at 1:48 AM, Finn Thain wrote: > On Mon, 12 Feb 2018, Geert Uytterhoeven wrote: >> Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with >> %p"), the virtual memory layout printed during boot up contains "ptrval" >> instead

Re: [PATCH] m68k/mm: Stop printing the virtual memory layout

Hi Finn, On Tue, Feb 13, 2018 at 1:48 AM, Finn Thain wrote: > On Mon, 12 Feb 2018, Geert Uytterhoeven wrote: >> Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with >> %p"), the virtual memory layout printed during boot up contains "ptrval" >> instead of actual addresses: >> >>

Re: [PATCH 2/2] f2fs: support {d,id,did,x}node checksum

Hi Jaegeuk, On 2018/2/10 10:52, Chao Yu wrote: > On 2018/2/10 9:41, Jaegeuk Kim wrote: >> On 02/01, Chao Yu wrote: >>> >>> >>> On 2018/2/1 6:15, Jaegeuk Kim wrote: On 01/31, Chao Yu wrote: > On 2018/1/31 10:02, Jaegeuk Kim wrote: >> What if we want to add more entries in addition to

Re: [PATCH 2/2] f2fs: support {d,id,did,x}node checksum

Hi Jaegeuk, On 2018/2/10 10:52, Chao Yu wrote: > On 2018/2/10 9:41, Jaegeuk Kim wrote: >> On 02/01, Chao Yu wrote: >>> >>> >>> On 2018/2/1 6:15, Jaegeuk Kim wrote: On 01/31, Chao Yu wrote: > On 2018/1/31 10:02, Jaegeuk Kim wrote: >> What if we want to add more entries in addition to

Re: [PATCH] printk: move dump stack related code to lib/dump_stack.c

On 02/09/18 at 06:15pm, Sergey Senozhatsky wrote: > On (02/09/18 17:00), Dave Young wrote: > [..] > > > > > > I'm hesitating to add #ifdef CONFIG_PRINTK in lib/dump_stack.c. > > Agreed. > > > Maybe conditionally build dump_stack.o only when CONFIG_PRINTK is true, > > but not sure if there are

Re: [PATCH] printk: move dump stack related code to lib/dump_stack.c

On 02/09/18 at 06:15pm, Sergey Senozhatsky wrote: > On (02/09/18 17:00), Dave Young wrote: > [..] > > > > > > I'm hesitating to add #ifdef CONFIG_PRINTK in lib/dump_stack.c. > > Agreed. > > > Maybe conditionally build dump_stack.o only when CONFIG_PRINTK is true, > > but not sure if there are

[PATCH v2] printk: move dump stack related code to lib/dump_stack.c

dump_stack related stuff should belong to lib/dump_stack.c thus move them there. Also conditionally compile lib/dump_stack.c since dump_stack code does not make sense if printk is disabled. Signed-off-by: Dave Young Suggested-by: Steven Rostedt

[PATCH v2] printk: move dump stack related code to lib/dump_stack.c

dump_stack related stuff should belong to lib/dump_stack.c thus move them there. Also conditionally compile lib/dump_stack.c since dump_stack code does not make sense if printk is disabled. Signed-off-by: Dave Young Suggested-by: Steven Rostedt Suggested-by: Sergey Senozhatsky --- Note: dump

Re: [PATCH v2 7/7] ASoC: samsung: Add missing #sound-dai-cells property documentation

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > The #sound-dai-cells property might be helpful in selecting primary > or secondary CPU DAI and it's already present in i2s nodes for some > exynos SoCs so let's add it to the DT binding documentation. > >

Re: [PATCH v2 7/7] ASoC: samsung: Add missing #sound-dai-cells property documentation

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > The #sound-dai-cells property might be helpful in selecting primary > or secondary CPU DAI and it's already present in i2s nodes for some > exynos SoCs so let's add it to the DT binding documentation. > > Signed-off-by: Sylwester

Re: [PATCH v2 6/7] ASoC: samsung: Add support for HDMI audio on TM2 board

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > This patch defines I2S1 - HDMI DAI link and implements related > hw_params callback. The AUD PLL frequency is configured through > the CLK_SCLK_I2S1 leaf clock, the exynos5433 clock tree > definitions are updated

Re: [PATCH v2 6/7] ASoC: samsung: Add support for HDMI audio on TM2 board

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > This patch defines I2S1 - HDMI DAI link and implements related > hw_params callback. The AUD PLL frequency is configured through > the CLK_SCLK_I2S1 leaf clock, the exynos5433 clock tree > definitions are updated in a separate patch. >

Re: [PATCH v2 3/7] ASoC: samsung: i2s: Prevent external abort on exynos5433 I2S1 access

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > It seems both PCLK_I2S1 and SCLK_I2S1 clocks need to be enabled before > I2S1 control registers can be accessed on exynos5433. If SCLK clock > is disabled an exception is triggered. To fix this parent clock of >

Re: [PATCH v2 2/7] ASoC: samsung: i2s: Ensure names of supplied clocks are unique

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > In order to support multiple instances of the I2S IP block the platform > device name is prepended to each clock registered by the driver. > The clock-output-names property is now not used, this should not cause

Re: [PATCH v2 3/7] ASoC: samsung: i2s: Prevent external abort on exynos5433 I2S1 access

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > It seems both PCLK_I2S1 and SCLK_I2S1 clocks need to be enabled before > I2S1 control registers can be accessed on exynos5433. If SCLK clock > is disabled an exception is triggered. To fix this parent clock of > the RCLK_SRC clock is

Re: [PATCH v2 2/7] ASoC: samsung: i2s: Ensure names of supplied clocks are unique

On Mon, Feb 12, 2018 at 5:15 PM, Sylwester Nawrocki wrote: > In order to support multiple instances of the I2S IP block the platform > device name is prepended to each clock registered by the driver. > The clock-output-names property is now not used, this should not cause > any issues as, for

Re: [PATCH V2] auxdisplay: use correct string length

On Tue, Feb 13, 2018 at 09:19:21AM +0800, Xiongfeng Wang wrote: > >> diff --git a/drivers/auxdisplay/panel.c b/drivers/auxdisplay/panel.c > >> index ea7869c..d288900 100644 > >> --- a/drivers/auxdisplay/panel.c > >> +++ b/drivers/auxdisplay/panel.c > >> @@ -1506,10 +1506,10 @@ static struct

Re: [PATCH V2] auxdisplay: use correct string length

On Tue, Feb 13, 2018 at 09:19:21AM +0800, Xiongfeng Wang wrote: > >> diff --git a/drivers/auxdisplay/panel.c b/drivers/auxdisplay/panel.c > >> index ea7869c..d288900 100644 > >> --- a/drivers/auxdisplay/panel.c > >> +++ b/drivers/auxdisplay/panel.c > >> @@ -1506,10 +1506,10 @@ static struct

Re: [PATCH v2 5/5] drm: adv7511: Add support for i2c_new_secondary_device

On Mon, Feb 12, 2018 at 06:11:57PM +, Kieran Bingham wrote: > + adv7511->i2c_packet = i2c_new_secondary_device(i2c, "packet", > + ADV7511_PACKET_I2C_ADDR_DEFAULT); > + if (!adv7511->i2c_packet) { > + ret = -EINVAL; > + goto

Re: [PATCH v2 5/5] drm: adv7511: Add support for i2c_new_secondary_device

On Mon, Feb 12, 2018 at 06:11:57PM +, Kieran Bingham wrote: > + adv7511->i2c_packet = i2c_new_secondary_device(i2c, "packet", > + ADV7511_PACKET_I2C_ADDR_DEFAULT); > + if (!adv7511->i2c_packet) { > + ret = -EINVAL; > + goto

Re: [PATCH] p9caps: add Plan9 capability devices

On Sun, Feb 11, 2018 at 09:50:28PM +, Enrico Weigelt, metux IT consult wrote: > From: "Enrico Weigelt, metux IT consult" > > This driver implements the Plan9 capability devices, used for > switching user id via capability tokens. > > https://9p.io/sys/doc/auth.html > --- >

Re: [PATCH] p9caps: add Plan9 capability devices

On Sun, Feb 11, 2018 at 09:50:28PM +, Enrico Weigelt, metux IT consult wrote: > From: "Enrico Weigelt, metux IT consult" > > This driver implements the Plan9 capability devices, used for > switching user id via capability tokens. > > https://9p.io/sys/doc/auth.html > --- >

Re: [PATCH] vsprintf: replace space with readable '=' before crng is ready

On 13 February 2018 at 07:20, Shunyong Yang wrote: > > This patch replaces space with readable "=" when output needs padding. > Following is the output after applying the patch, > Suggested-by: Rasmus Villemoes > > if

Re: [PATCH] vsprintf: replace space with readable '=' before crng is ready

On 13 February 2018 at 07:20, Shunyong Yang wrote: > > This patch replaces space with readable "=" when output needs padding. > Following is the output after applying the patch, > Suggested-by: Rasmus Villemoes > > if (unlikely(!have_filled_random_ptr_key)) { > + char

[PATCH] media: i2c: ov5640: Add pixel clock support

Some of the camera subsystems like camss in Qualcommm MSM chipsets require pixel clock support in camera sensor drivers. So, this commit adds a default pixel clock rate of 96MHz to OV5640 camera sensor driver. According to the datasheet, 96MHz can be used as a pixel clock rate for most of the

[PATCH] media: i2c: ov5640: Add pixel clock support

Some of the camera subsystems like camss in Qualcommm MSM chipsets require pixel clock support in camera sensor drivers. So, this commit adds a default pixel clock rate of 96MHz to OV5640 camera sensor driver. According to the datasheet, 96MHz can be used as a pixel clock rate for most of the

[PATCH] Add pixel clock support to OV5640 camera sensor

Some of the camera subsystems like camss in Qualcommm MSM chipsets require pixel clock support in camera sensor drivers for proper functioning. So, add a default pixel clock rate of 96MHz to OV5640 camera sensor driver. According to the datasheet, 96MHz can be used as a pixel clock rate for most

[PATCH] Add pixel clock support to OV5640 camera sensor

Some of the camera subsystems like camss in Qualcommm MSM chipsets require pixel clock support in camera sensor drivers for proper functioning. So, add a default pixel clock rate of 96MHz to OV5640 camera sensor driver. According to the datasheet, 96MHz can be used as a pixel clock rate for most

Re: why scripts/link-vmlinux.sh has a final build of init/

On 02/12/2018 10:48 PM, Masahiro Yamada wrote: > 2018-02-12 13:22 GMT+09:00 Cao jin : >> Hi Masahiro-san, >> >> As I remember, init/ is already built during recursive make, and I did >> a clean build(make mrproper, make localmodconfig) with all plugins >> included on

Re: why scripts/link-vmlinux.sh has a final build of init/

On 02/12/2018 10:48 PM, Masahiro Yamada wrote: > 2018-02-12 13:22 GMT+09:00 Cao jin : >> Hi Masahiro-san, >> >> As I remember, init/ is already built during recursive make, and I did >> a clean build(make mrproper, make localmodconfig) with all plugins >> included on x86_64 with following

Re: [PATCH v4 5/5] dmaengine: mediatek: fix zalloc-simple.cocci warnings

On Tue, 13 Feb 2018, Vinod Koul wrote: > On Fri, Feb 09, 2018 at 03:55:58PM +0100, Julia Lawall wrote: > > > > > > - ring->txd = dma_alloc_coherent(hsdma2dev(hsdma), > > > > - pc->sz_ring, >tphys, > > > > -

Re: [PATCH v4 5/5] dmaengine: mediatek: fix zalloc-simple.cocci warnings

On Tue, 13 Feb 2018, Vinod Koul wrote: > On Fri, Feb 09, 2018 at 03:55:58PM +0100, Julia Lawall wrote: > > > > > > - ring->txd = dma_alloc_coherent(hsdma2dev(hsdma), > > > > - pc->sz_ring, >tphys, > > > > -

Re: [tip:x86/boot] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G

Hi Kirill, Something is wrong in this patch. We regularly run CRIU tests on linux-next, and yesterday I found that a kernel didn't boot. We run this tests in Travis-CI, and we don't have access to kernel logs. I tried to reproduce the problem localy, but I failed. In Travis-CI, we build kernel,

Re: [tip:x86/boot] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G

Hi Kirill, Something is wrong in this patch. We regularly run CRIU tests on linux-next, and yesterday I found that a kernel didn't boot. We run this tests in Travis-CI, and we don't have access to kernel logs. I tried to reproduce the problem localy, but I failed. In Travis-CI, we build kernel,

Re: [PATCH v6] devres: combine function devm_ioremap*

On Mon, Feb 12, 2018 at 07:07:34PM +0800, Yisheng Xie wrote: > Hi Greg, Christophe, > > Any comment about this version? And sorry to disturb :) Please give me a chance to dig out from the merge window patch debt. I'll get to this in a week or so... But at first glance, looks fine to me. greg

Re: [PATCH v6] devres: combine function devm_ioremap*

On Mon, Feb 12, 2018 at 07:07:34PM +0800, Yisheng Xie wrote: > Hi Greg, Christophe, > > Any comment about this version? And sorry to disturb :) Please give me a chance to dig out from the merge window patch debt. I'll get to this in a week or so... But at first glance, looks fine to me. greg

Re: ppc elf_map breakage with MAP_FIXED_NOREPLACE

On 02/01/2018 07:18 PM, Michal Hocko wrote: > On Thu 01-02-18 08:43:34, Anshuman Khandual wrote: > [...] >> $dmesg | grep elf_brk >> [9.571192] elf_brk 10030328 elf_bss 1003 >> >> static int load_elf_binary(struct linux_binprm *bprm) >> - >> >> if (unlikely

Re: ppc elf_map breakage with MAP_FIXED_NOREPLACE

On 02/01/2018 07:18 PM, Michal Hocko wrote: > On Thu 01-02-18 08:43:34, Anshuman Khandual wrote: > [...] >> $dmesg | grep elf_brk >> [9.571192] elf_brk 10030328 elf_bss 1003 >> >> static int load_elf_binary(struct linux_binprm *bprm) >> - >> >> if (unlikely

Re: [PATCH v4 5/5] dmaengine: mediatek: fix zalloc-simple.cocci warnings

On Fri, Feb 09, 2018 at 03:55:58PM +0100, Julia Lawall wrote: > > > > - ring->txd = dma_alloc_coherent(hsdma2dev(hsdma), > > > -pc->sz_ring, >tphys, > > > -GFP_ATOMIC | __GFP_ZERO); > > > + ring->txd =

Re: [PATCH v4 5/5] dmaengine: mediatek: fix zalloc-simple.cocci warnings

On Fri, Feb 09, 2018 at 03:55:58PM +0100, Julia Lawall wrote: > > > > - ring->txd = dma_alloc_coherent(hsdma2dev(hsdma), > > > -pc->sz_ring, >tphys, > > > -GFP_ATOMIC | __GFP_ZERO); > > > + ring->txd =

[PATCH v4] pstore: add lz4hc and 842 compression support

Currently, pstore has supported three compression algorithms: zlib, lzo and lz4. This patch added two more compression algorithms: lz4hc and 842. Signed-off-by: Geliang Tang --- Changes in v4: -842 compress is not work in patch v3 since big_oops_buf_sz is too big.

[PATCH v4] pstore: add lz4hc and 842 compression support

Currently, pstore has supported three compression algorithms: zlib, lzo and lz4. This patch added two more compression algorithms: lz4hc and 842. Signed-off-by: Geliang Tang --- Changes in v4: -842 compress is not work in patch v3 since big_oops_buf_sz is too big. change big_oops_buf_sz from

Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

On Thu, Jan 25, 2018 at 10:36 PM, Amir Goldstein wrote: > On Thu, Jan 25, 2018 at 10:20 PM, Shakeel Butt wrote: >> On Wed, Jan 24, 2018 at 11:51 PM, Amir Goldstein wrote: >>> >>> There is a nicer alternative, instead of failing the

Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

On Thu, Jan 25, 2018 at 10:36 PM, Amir Goldstein wrote: > On Thu, Jan 25, 2018 at 10:20 PM, Shakeel Butt wrote: >> On Wed, Jan 24, 2018 at 11:51 PM, Amir Goldstein wrote: >>> >>> There is a nicer alternative, instead of failing the file access, >>> an overflow event can be queued. I sent a

[PATCH] vsprintf: replace space with readable '=' before crng is ready

Before crng is ready, output of "%p" composes of "(ptrval)" and left padding spaces for alignment as no random address can be generated. This seems a little strange when default string width is larger than strlen("(ptrval)"). For example, when irq domain names are built with "%p", the nodes under

Re: [PATCH] PCI: Add quirk for Cavium Thunder-X2 PCIe erratum #173

On Fri, Feb 02, 2018 at 07:00:46AM +, George Cherian wrote: > The PCIe Controller on Cavium ThunderX2 processors does not > respond to downstream CFG/ECFG cycles when root port is > in power management D3-hot state. > > In our tests the above mentioned errata causes the following crash when >

[PATCH] vsprintf: replace space with readable '=' before crng is ready

Before crng is ready, output of "%p" composes of "(ptrval)" and left padding spaces for alignment as no random address can be generated. This seems a little strange when default string width is larger than strlen("(ptrval)"). For example, when irq domain names are built with "%p", the nodes under

Re: [PATCH] PCI: Add quirk for Cavium Thunder-X2 PCIe erratum #173

On Fri, Feb 02, 2018 at 07:00:46AM +, George Cherian wrote: > The PCIe Controller on Cavium ThunderX2 processors does not > respond to downstream CFG/ECFG cycles when root port is > in power management D3-hot state. > > In our tests the above mentioned errata causes the following crash when >

Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree

Hi Brendan, On Tue, Feb 6, 2018 at 10:27 AM, Brendan Higgins wrote: > Add a common device tree for all Nuvoton NPCM750 BMCs and a board > specific device tree for the NPCM750 (Poleg) evaluation board. > > Signed-off-by: Brendan Higgins >

Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree

Hi Brendan, On Tue, Feb 6, 2018 at 10:27 AM, Brendan Higgins wrote: > Add a common device tree for all Nuvoton NPCM750 BMCs and a board > specific device tree for the NPCM750 (Poleg) evaluation board. > > Signed-off-by: Brendan Higgins > Reviewed-by: Tomer Maimon > Reviewed-by: Avi Fishman >

[PATCH] gpio: Handle deferred probing in of_find_gpio() properly

of_get_named_gpiod_flags() used directly in of_find_gpio() or indirectly through of_find_spi_gpio() or of_find_regulator_gpio() can return -EPROBE_DEFER. This gets overwritten by the subsequent of_find_*_gpio() calls. This patch fixes this by trying of_find_spi_gpio() or of_find_regulator_gpio()

[PATCH] gpio: Handle deferred probing in of_find_gpio() properly

of_get_named_gpiod_flags() used directly in of_find_gpio() or indirectly through of_find_spi_gpio() or of_find_regulator_gpio() can return -EPROBE_DEFER. This gets overwritten by the subsequent of_find_*_gpio() calls. This patch fixes this by trying of_find_spi_gpio() or of_find_regulator_gpio()

Re: samples/seccomp/ broken when cross compiling s390, ppc allyesconfig

On Mon, Feb 12, 2018 at 7:25 PM, Michael Ellerman wrote: > Michal Hocko writes: >> Hi, >> my build test machinery chokes on samples/seccomp when cross compiling >> s390 and ppc64 allyesconfig. This has been the case for quite some >> time already but I

Re: samples/seccomp/ broken when cross compiling s390, ppc allyesconfig

On Mon, Feb 12, 2018 at 7:25 PM, Michael Ellerman wrote: > Michal Hocko writes: >> Hi, >> my build test machinery chokes on samples/seccomp when cross compiling >> s390 and ppc64 allyesconfig. This has been the case for quite some >> time already but I never found time to look at the problem and

Re: [PATCH] dmaengine: dmatest: fix container_of member in dmatest_callback

Hi, Wen You're welcome. That's why call this COMMUNITY! :-) Shunyong. Thanks. On Sun, 2018-02-11 at 09:28 +, Wen He wrote: > Thanks for you, Shunyong. > > Best Regards, > Wen He > > > > > -Original Message- > > From: dmaengine-ow...@vger.kernel.org > >

Re: [PATCH] dmaengine: dmatest: fix container_of member in dmatest_callback

Hi, Wen You're welcome. That's why call this COMMUNITY! :-) Shunyong. Thanks. On Sun, 2018-02-11 at 09:28 +, Wen He wrote: > Thanks for you, Shunyong. > > Best Regards, > Wen He > > > > > -Original Message- > > From: dmaengine-ow...@vger.kernel.org > >

Re: [PATCH net-next] trace_events_filter: conditional trace event (tcp_probe full=0)

On Mon, Feb 12, 2018 at 11:29 AM, Masami Hiramatsu wrote: > On Mon, 12 Feb 2018 00:08:46 -0500 > "Md. Islam" wrote: > >> Recently tcp_probe kernel module has been replaced by trace_event. Old >> tcp_probe had full=0 option where it only takes a snapshot

Re: [PATCH net-next] trace_events_filter: conditional trace event (tcp_probe full=0)

On Mon, Feb 12, 2018 at 11:29 AM, Masami Hiramatsu wrote: > On Mon, 12 Feb 2018 00:08:46 -0500 > "Md. Islam" wrote: > >> Recently tcp_probe kernel module has been replaced by trace_event. Old >> tcp_probe had full=0 option where it only takes a snapshot only when >> congestion window is changed.

[PATCH v4 4/6] riscv/ftrace: Add ARCH_SUPPORTS_FTRACE_OPS support

Cc: Greentime Hu Signed-off-by: Alan Kao --- arch/riscv/include/asm/ftrace.h | 1 + arch/riscv/kernel/mcount-dyn.S | 3 +++ 2 files changed, 4 insertions(+) diff --git a/arch/riscv/include/asm/ftrace.h b/arch/riscv/include/asm/ftrace.h index

[PATCH v4 4/6] riscv/ftrace: Add ARCH_SUPPORTS_FTRACE_OPS support

Cc: Greentime Hu Signed-off-by: Alan Kao --- arch/riscv/include/asm/ftrace.h | 1 + arch/riscv/kernel/mcount-dyn.S | 3 +++ 2 files changed, 4 insertions(+) diff --git a/arch/riscv/include/asm/ftrace.h b/arch/riscv/include/asm/ftrace.h index 078743aacfd3..fedadc40e358 100644 ---

[PATCH v4 5/6] riscv/ftrace: Add DYNAMIC_FTRACE_WITH_REGS support

Cc: Greentime Hu Signed-off-by: Alan Kao --- arch/riscv/Kconfig | 1 + arch/riscv/include/asm/ftrace.h | 1 + arch/riscv/kernel/ftrace.c | 17 ++ arch/riscv/kernel/mcount-dyn.S | 122

[PATCH v4 5/6] riscv/ftrace: Add DYNAMIC_FTRACE_WITH_REGS support

Cc: Greentime Hu Signed-off-by: Alan Kao --- arch/riscv/Kconfig | 1 + arch/riscv/include/asm/ftrace.h | 1 + arch/riscv/kernel/ftrace.c | 17 ++ arch/riscv/kernel/mcount-dyn.S | 122 4 files changed, 141 insertions(+) diff

[PATCH v4 2/6] riscv/ftrace: Add dynamic function tracer support

We now have dynamic ftrace with the following added items: * ftrace_make_call, ftrace_make_nop (in kernel/ftrace.c) The two functions turn each recorded call site of filtered functions into a call to ftrace_caller or nops * ftracce_update_ftrace_func (in kernel/ftrace.c) turns the nops at

[PATCH v4 2/6] riscv/ftrace: Add dynamic function tracer support

We now have dynamic ftrace with the following added items: * ftrace_make_call, ftrace_make_nop (in kernel/ftrace.c) The two functions turn each recorded call site of filtered functions into a call to ftrace_caller or nops * ftracce_update_ftrace_func (in kernel/ftrace.c) turns the nops at

[PATCH v4 3/6] riscv/ftrace: Add dynamic function graph tracer support

Once the function_graph tracer is enabled, a filtered function has the following call sequence: * ftracer_caller ==> on/off by ftrace_make_call/ftrace_make_nop * ftrace_graph_caller * ftrace_graph_call ==> on/off by ftrace_en/disable_ftrace_graph_caller * prepare_ftrace_return

[PATCH v4 3/6] riscv/ftrace: Add dynamic function graph tracer support

Once the function_graph tracer is enabled, a filtered function has the following call sequence: * ftracer_caller ==> on/off by ftrace_make_call/ftrace_make_nop * ftrace_graph_caller * ftrace_graph_call ==> on/off by ftrace_en/disable_ftrace_graph_caller * prepare_ftrace_return

[PATCH v4 6/6] riscv/ftrace: Add HAVE_FUNCTION_GRAPH_RET_ADDR_PTR support

In walk_stackframe, the pc now receives the address from calling ftrace_graph_ret_addr instead of manual calculation. Note that the original calculation, pc = frame->ra - 4 is buggy when the instruction at the return address happened to be a compressed inst. But since it is not a critical

[PATCH v4 6/6] riscv/ftrace: Add HAVE_FUNCTION_GRAPH_RET_ADDR_PTR support

In walk_stackframe, the pc now receives the address from calling ftrace_graph_ret_addr instead of manual calculation. Note that the original calculation, pc = frame->ra - 4 is buggy when the instruction at the return address happened to be a compressed inst. But since it is not a critical

[PATCH v4 0/6] Add dynamic ftrace support for RISC-V platforms

This patch set includes the building blocks of dynamic ftrace features for RISC-V machines. Changes in v4: - Organize code structure according to changes in v3 - Rebase onto the riscv-linux-4.15 branch at github's riscv/riscv-linux repo. Note that this set is based on the previous

[PATCH v4 1/6] riscv/ftrace: Add RECORD_MCOUNT support

Now recordmcount.pl recognizes RISC-V object files. For the mechanism to work, we have to disable the linker relaxation. Cc: Greentime Hu Signed-off-by: Alan Kao --- arch/riscv/Kconfig | 1 + arch/riscv/Makefile | 3 +++

  1   2   3   4   5   6   7   8   9   10   >