Re: [PATCH 05/21] powerpc: Avoid comparison of unsigned long >= 0 in pfn_valid

Le 02/03/2018 à 20:54, Mathieu Malaterre a écrit : On Mon, Feb 26, 2018 at 9:46 AM, Segher Boessenkool wrote: On Mon, Feb 26, 2018 at 07:32:03AM +0100, Christophe LEROY wrote: Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : -#define pfn_valid(pfn)

Re: [PATCH 05/21] powerpc: Avoid comparison of unsigned long >= 0 in pfn_valid

Le 02/03/2018 à 20:54, Mathieu Malaterre a écrit : On Mon, Feb 26, 2018 at 9:46 AM, Segher Boessenkool wrote: On Mon, Feb 26, 2018 at 07:32:03AM +0100, Christophe LEROY wrote: Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : -#define pfn_valid(pfn) ((pfn) >= ARCH_PFN_OFFSET

Re: [PATCH v2 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

Le 02/03/2018 à 20:50, Mathieu Malaterre a écrit : Rewrite function-like macro into regular static inline function to avoid a warning during macro expansion. Fix warning (treated as error in W=1): CC arch/powerpc/kernel/signal_32.o In file included from ./include/linux/uaccess.h:14:0,

Re: [PATCH v2 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

Le 02/03/2018 à 20:50, Mathieu Malaterre a écrit : Rewrite function-like macro into regular static inline function to avoid a warning during macro expansion. Fix warning (treated as error in W=1): CC arch/powerpc/kernel/signal_32.o In file included from ./include/linux/uaccess.h:14:0,

Re: [PATCH v4 2/2] of: add early boot allocation of of_find_node_by_phandle() cache

Hi Frank, I love your patch! Yet something to improve: [auto build test ERROR on robh/for-next] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [PATCH v4 2/2] of: add early boot allocation of of_find_node_by_phandle() cache

Hi Frank, I love your patch! Yet something to improve: [auto build test ERROR on robh/for-next] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [Outreachy kernel] [PATCH v2 0/6] staging: rtl8712: fix coding style issues

On Sat, 3 Mar 2018, Arushi Singhal wrote: > Fix issues found with checkpatch.pl to conform to the Linux > kernel coding style. For the series: Acked-by: Julia Lawall > > Changes in v2: > * From and Signed-off emails were not same in v1. > * Added detailed commit

Re: [Outreachy kernel] [PATCH v2 0/6] staging: rtl8712: fix coding style issues

On Sat, 3 Mar 2018, Arushi Singhal wrote: > Fix issues found with checkpatch.pl to conform to the Linux > kernel coding style. For the series: Acked-by: Julia Lawall > > Changes in v2: > * From and Signed-off emails were not same in v1. > * Added detailed commit message > > Arushi Singhal

Re: [PATCH] ARM: dts: tpc: Device tree description of the TPC board

Hi Fabio, > Hi Lukasz, > > In addition to Sascha's comments: Thanks for your input - please see my reply below. > > On Fri, Mar 2, 2018 at 9:17 AM, Lukasz Majewski wrote: > > > diff --git a/arch/arm/boot/dts/imx6q-kp-tpc.dts > > b/arch/arm/boot/dts/imx6q-kp-tpc.dts new file

Re: [PATCH] ARM: dts: tpc: Device tree description of the TPC board

Hi Fabio, > Hi Lukasz, > > In addition to Sascha's comments: Thanks for your input - please see my reply below. > > On Fri, Mar 2, 2018 at 9:17 AM, Lukasz Majewski wrote: > > > diff --git a/arch/arm/boot/dts/imx6q-kp-tpc.dts > > b/arch/arm/boot/dts/imx6q-kp-tpc.dts new file mode 100644 > >

Re: [PATCH 5/7] Pmalloc selftest

improve the system] url: https://github.com/0day-ci/linux/commits/Igor-Stoppa/mm-security-ro-protection-for-dynamic-data/20180302-232215 config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https

Re: [PATCH 5/7] Pmalloc selftest

improve the system] url: https://github.com/0day-ci/linux/commits/Igor-Stoppa/mm-security-ro-protection-for-dynamic-data/20180302-232215 config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https

[PATCH] drm: Fix typo in lastclose description

ownershipe -> ownership Signed-off-by: Mun Gwan-gyeong --- include/drm/drm_drv.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h index d23dcdd1bd95..64cb5975613c 100644 --- a/include/drm/drm_drv.h +++

[PATCH] drm: Fix typo in lastclose description

ownershipe -> ownership Signed-off-by: Mun Gwan-gyeong --- include/drm/drm_drv.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h index d23dcdd1bd95..64cb5975613c 100644 --- a/include/drm/drm_drv.h +++ b/include/drm/drm_drv.h @@

[PATCH v2 3/6] staging: rtl8712: Remove multiple blank line(s)

Remove extra blank line(s) to conform to the Linux kernel coding style. Issue found using checkpatch. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/os_intfs.c | 1 - drivers/staging/rtl8712/rtl8712_bitdef.h | 1 -

[PATCH v2 3/6] staging: rtl8712: Remove multiple blank line(s)

Remove extra blank line(s) to conform to the Linux kernel coding style. Issue found using checkpatch. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/os_intfs.c | 1 - drivers/staging/rtl8712/rtl8712_bitdef.h | 1 -

[PATCH v2 2/6] staging: rtl8712: match alignment with open parenthesis

Delete/Add tabs and spaces to align the code to fix the checkpatch issue: "CHECK: Alignment should match open parenthesis". Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/mlme_linux.c | 2 +- drivers/staging/rtl8712/os_intfs.c | 2 +- 2 files

[PATCH v2 2/6] staging: rtl8712: match alignment with open parenthesis

Delete/Add tabs and spaces to align the code to fix the checkpatch issue: "CHECK: Alignment should match open parenthesis". Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/mlme_linux.c | 2 +- drivers/staging/rtl8712/os_intfs.c | 2 +- 2 files changed, 2 insertions(+), 2

[PATCH v2 5/6] staging: rtl8712: Add spaces around '|'

Add spaces around '|' to conform to the Linux kernel coding style. Issue found using checkpatch. CHECK: spaces preferred around that '|'. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/rtl8712_cmdctrl_bitdef.h | 2 +-

[PATCH v2 5/6] staging: rtl8712: Add spaces around '|'

Add spaces around '|' to conform to the Linux kernel coding style. Issue found using checkpatch. CHECK: spaces preferred around that '|'. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/rtl8712_cmdctrl_bitdef.h | 2 +- drivers/staging/rtl8712/rtl8712_gp_bitdef.h | 2 +- 2 files

[PATCH v2 6/6] staging: rtl8712: remove unnecessary parentheses

Remove unnecessary parentheses around variables to conform to the Linux kernel coding style. Issue found using checkpatch. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/recv_linux.c | 4 +- drivers/staging/rtl8712/rtl8712_cmd.c | 8 ++--

[PATCH v2 6/6] staging: rtl8712: remove unnecessary parentheses

Remove unnecessary parentheses around variables to conform to the Linux kernel coding style. Issue found using checkpatch. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/recv_linux.c | 4 +- drivers/staging/rtl8712/rtl8712_cmd.c | 8 ++-- drivers/staging/rtl8712/rtl8712_led.c | 70

[PATCH v2 1/6] staging: rtl8712: Fixed 'tabstop' coding style warning

Replace a mix of tabs and spaces indentation by tabs only. Fixed checkpatch warning "Statements should start on a tabstop". Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/drv_types.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 0/6] staging: rtl8712: fix coding style issues

Fix issues found with checkpatch.pl to conform to the Linux kernel coding style. Changes in v2: * From and Signed-off emails were not same in v1. * Added detailed commit message Arushi Singhal (6): staging: rtl8712: Fixed 'tabstop' coding style warning staging: rtl8712: match alignment with

[PATCH v2 0/6] staging: rtl8712: fix coding style issues

Fix issues found with checkpatch.pl to conform to the Linux kernel coding style. Changes in v2: * From and Signed-off emails were not same in v1. * Added detailed commit message Arushi Singhal (6): staging: rtl8712: Fixed 'tabstop' coding style warning staging: rtl8712: match alignment with

[PATCH v2 1/6] staging: rtl8712: Fixed 'tabstop' coding style warning

Replace a mix of tabs and spaces indentation by tabs only. Fixed checkpatch warning "Statements should start on a tabstop". Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/drv_types.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 4/6] staging: rtl8712: Added spaces around '+'

Add spaces around arithmetic operator '+', to conform to the Linux kernel coding style. Issue found using checkpatch. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/rtl8712_cmd.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v2 4/6] staging: rtl8712: Added spaces around '+'

Add spaces around arithmetic operator '+', to conform to the Linux kernel coding style. Issue found using checkpatch. Signed-off-by: Arushi Singhal --- drivers/staging/rtl8712/rtl8712_cmd.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[of] b013aa45d2: kernel_BUG_at_arch/x86/mm/physaddr.c

FYI, we noticed the following commit (built with gcc-5): commit: b013aa45d2168019984aec70e00d09cf0a4a00c5 ("of: add early boot allocation of of_find_node_by_phandle() cache") url:

[of] b013aa45d2: kernel_BUG_at_arch/x86/mm/physaddr.c

FYI, we noticed the following commit (built with gcc-5): commit: b013aa45d2168019984aec70e00d09cf0a4a00c5 ("of: add early boot allocation of of_find_node_by_phandle() cache") url:

Re: [PATCH v2] 8250-men-mcb: add support for 16z025 and 16z057

Hi Michael, Thank you for the patch! Yet something to improve: [auto build test ERROR on tty/tty-testing] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

linux-next: Signed-off-by missing for commit in the pinctrl tree

Hi Linus, Commit 77bd5bf24c08 ("pinctrl: sh-pfc: r8a7795: remove duplicate of CLKOUT pin in pinmux_pins[]") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpIiRawQhRrL.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the pinctrl tree

Hi Linus, Commit 77bd5bf24c08 ("pinctrl: sh-pfc: r8a7795: remove duplicate of CLKOUT pin in pinmux_pins[]") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpIiRawQhRrL.pgp Description: OpenPGP digital signature

Re: [PATCH v2] 8250-men-mcb: add support for 16z025 and 16z057

Hi Michael, Thank you for the patch! Yet something to improve: [auto build test ERROR on tty/tty-testing] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

linux-next: Signed-off-by missing for commit in the pci tree

Hi Bjorn, Commit a1a9f434c900 ("PCI: Rename pci_flr_wait() to pci_dev_wait() and make it generic") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpdbGJowAT7f.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the pci tree

Hi Bjorn, Commit a1a9f434c900 ("PCI: Rename pci_flr_wait() to pci_dev_wait() and make it generic") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpdbGJowAT7f.pgp Description: OpenPGP digital signature

Re: [PATCH v3 2/2] PCI/IOV: Use the cached VF BARs size instead of re-reading them

On Fri, 2018-03-02 at 15:48 -0600, Bjorn Helgaas wrote: > On Thu, Mar 01, 2018 at 10:31:37PM +0100, KarimAllah Ahmed wrote: > > > > Use the cached VF BARs size instead of re-reading them from the hardware. > > That avoids doing unnecessarily bus transactions which is specially > > noticable when

Re: [PATCH v3 2/2] PCI/IOV: Use the cached VF BARs size instead of re-reading them

On Fri, 2018-03-02 at 15:48 -0600, Bjorn Helgaas wrote: > On Thu, Mar 01, 2018 at 10:31:37PM +0100, KarimAllah Ahmed wrote: > > > > Use the cached VF BARs size instead of re-reading them from the hardware. > > That avoids doing unnecessarily bus transactions which is specially > > noticable when

[PATCH] PCI/IOV: Skip initializing the base addresses from the VF config space

Per PCIe r4.0, sec 9.3.4.1.11, the BARs registers from the VF config space are all RO Zero for PCI VFs. So just skip reading them for VFs. This is an optimization when enabling SR-IOV on a device with many VFs. Cc: Bjorn Helgaas Cc: linux-...@vger.kernel.org Cc:

[PATCH] PCI/IOV: Skip initializing the base addresses from the VF config space

Per PCIe r4.0, sec 9.3.4.1.11, the BARs registers from the VF config space are all RO Zero for PCI VFs. So just skip reading them for VFs. This is an optimization when enabling SR-IOV on a device with many VFs. Cc: Bjorn Helgaas Cc: linux-...@vger.kernel.org Cc: linux-kernel@vger.kernel.org

[PATCH] coresight: use %px to print pcsr instead of %p

Commit ad67b74d2469 ("printk: hash addresses printed with %p") lets printk specifier %p to hash all addresses before printing, this was resulting in the high 32 bits of pcsr can only output zeros. So module cannot completely print pc value and it's pointless for debugging purpose. This patch

[PATCH] coresight: use %px to print pcsr instead of %p

Commit ad67b74d2469 ("printk: hash addresses printed with %p") lets printk specifier %p to hash all addresses before printing, this was resulting in the high 32 bits of pcsr can only output zeros. So module cannot completely print pc value and it's pointless for debugging purpose. This patch

[PATCH] x86: devicetree: fix config option around x86_flattree_get_config()

From: Frank Rowand x86_flattree_get_config() is incorrectly protected by ifdef CONFIG_OF_FLATTREE. It uses of_get_flat_dt_size(), which only exists if CONFIG_OF_EARLY_FLATTREE. This issue has not been exposed previously because OF_FLATTREE did not occur unless it was

[PATCH] x86: devicetree: fix config option around x86_flattree_get_config()

From: Frank Rowand x86_flattree_get_config() is incorrectly protected by ifdef CONFIG_OF_FLATTREE. It uses of_get_flat_dt_size(), which only exists if CONFIG_OF_EARLY_FLATTREE. This issue has not been exposed previously because OF_FLATTREE did not occur unless it was selected by

[PATCH -tip] x86: kprobes: Cleanup preempt disabling and enabling

Cleanup x86/kprobes preempt counts so that preemt_disable() and preempt_enable_no_sched() are called from kprobe_int3_handler(). Only if a kprobe runs single-stepping, preemption is kept disabled and that is enabled when - single-stepping is finished - a fault occurs on single-steped instruction

[PATCH -tip] x86: kprobes: Cleanup preempt disabling and enabling

Cleanup x86/kprobes preempt counts so that preemt_disable() and preempt_enable_no_sched() are called from kprobe_int3_handler(). Only if a kprobe runs single-stepping, preemption is kept disabled and that is enabled when - single-stepping is finished - a fault occurs on single-steped instruction

Re: [PATCH 3/3] drivers: clk: Add ZynqMP clock driver

Hi Jolly, Thank you for the patch! Yet something to improve: [auto build test ERROR on clk/clk-next] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [PATCH 3/3] drivers: clk: Add ZynqMP clock driver

Hi Jolly, Thank you for the patch! Yet something to improve: [auto build test ERROR on clk/clk-next] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

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

Hi Petr, On Fri, 2 Mar 2018 16:54:54 +0100 Petr Mladek wrote: > > It is a mistery to me. The error appears when I move any of > dump_stack_print_info() or show_regs_print_info() function > definitions from kernel/printk/printk.c to lib/dump_stack.c. > All the other changes

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

Hi Petr, On Fri, 2 Mar 2018 16:54:54 +0100 Petr Mladek wrote: > > It is a mistery to me. The error appears when I move any of > dump_stack_print_info() or show_regs_print_info() function > definitions from kernel/printk/printk.c to lib/dump_stack.c. > All the other changes seems unrelated.

Re: [PATCH 3/7] struct page: add field for vm_struct

to help improve the system] url: https://github.com/0day-ci/linux/commits/Igor-Stoppa/mm-security-ro-protection-for-dynamic-data/20180302-232215 reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones

Re: [PATCH v2 2/4] rtc: isl1208: switch to rtc_register_device

Hi Denis, Thank you for the patch! Yet something to improve: [auto build test ERROR on abelloni/rtc-next] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH 3/7] struct page: add field for vm_struct

to help improve the system] url: https://github.com/0day-ci/linux/commits/Igor-Stoppa/mm-security-ro-protection-for-dynamic-data/20180302-232215 reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones

Re: [PATCH v2 2/4] rtc: isl1208: switch to rtc_register_device

Hi Denis, Thank you for the patch! Yet something to improve: [auto build test ERROR on abelloni/rtc-next] [also build test ERROR on v4.16-rc3 next-20180302] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v5 00/12] vfio, dax: prevent long term filesystem-dax pins and other fixes

On Fri, Mar 2, 2018 at 3:49 PM, Dan Williams wrote: > On Fri, Mar 2, 2018 at 2:57 PM, Christoph Hellwig wrote: >> On Fri, Mar 02, 2018 at 02:21:40PM -0800, Dan Williams wrote: >>> They are indeed a hodge-podge. The problem is that the current >>> IS_DAX()

Re: [PATCH v5 00/12] vfio, dax: prevent long term filesystem-dax pins and other fixes

On Fri, Mar 2, 2018 at 3:49 PM, Dan Williams wrote: > On Fri, Mar 2, 2018 at 2:57 PM, Christoph Hellwig wrote: >> On Fri, Mar 02, 2018 at 02:21:40PM -0800, Dan Williams wrote: >>> They are indeed a hodge-podge. The problem is that the current >>> IS_DAX() is broken. So I'd like to propose fixing

Re: [PATCH v1 18/19] arm: dts: mt7623: add MT7623A reference boards

On Fri, 2018-03-02 at 09:45 -0600, Rob Herring wrote: > On Fri, Feb 23, 2018 at 06:16:38PM +0800, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > Add mt7623a-rfb.dtsi where most nodes can be inherited from > > mt7623n-rfb.dtsi and keep these distinctions from

Re: [PATCH v1 18/19] arm: dts: mt7623: add MT7623A reference boards

On Fri, 2018-03-02 at 09:45 -0600, Rob Herring wrote: > On Fri, Feb 23, 2018 at 06:16:38PM +0800, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > Add mt7623a-rfb.dtsi where most nodes can be inherited from > > mt7623n-rfb.dtsi and keep these distinctions from MT7623A boards in > >

Re: [PATCH v3 3/3] platform/x86: dell-smbios: Link all dell-smbios-* modules together

On Tue, Feb 27, 2018 at 12:23:04PM -0600, Mario Limonciello wrote: > Some race conditions were raised due to dell-smbios and its backends > not being ready by the time that a consumer would call one of the > exported methods. > > To avoid this problem, guarantee that all initialization has been >

Re: [PATCH v3 3/3] platform/x86: dell-smbios: Link all dell-smbios-* modules together

On Tue, Feb 27, 2018 at 12:23:04PM -0600, Mario Limonciello wrote: > Some race conditions were raised due to dell-smbios and its backends > not being ready by the time that a consumer would call one of the > exported methods. > > To avoid this problem, guarantee that all initialization has been >

Re: ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!

On Thu, Mar 01, 2018 at 04:25:45PM +, Robin Murphy wrote: On 01/03/18 03:18, kbuild test robot wrote: Hi Robin, First bad commit (maybe != root cause): I have to admit I'm slightly intrigued how this commit could possibly appear relevant to the IA64 build at all, let alone to this error

Re: ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!

On Thu, Mar 01, 2018 at 04:25:45PM +, Robin Murphy wrote: On 01/03/18 03:18, kbuild test robot wrote: Hi Robin, First bad commit (maybe != root cause): I have to admit I'm slightly intrigued how this commit could possibly appear relevant to the IA64 build at all, let alone to this error

[PATCH V4] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert

In scsi core, __scsi_queue_insert should just put request back on the queue and retry using the same command as before. However, for blk-mq, scsi_mq_requeue_cmd is employed here which will unprepare the request. To align with the semantics of __scsi_queue_insert, use blk_mq_requeue_request with

[PATCH V4] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert

In scsi core, __scsi_queue_insert should just put request back on the queue and retry using the same command as before. However, for blk-mq, scsi_mq_requeue_cmd is employed here which will unprepare the request. To align with the semantics of __scsi_queue_insert, use blk_mq_requeue_request with

RE: [PATCH v3 3/3] platform/x86: dell-smbios: Link all dell-smbios-* modules together

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, March 2, 2018 6:22 PM > To: Limonciello, Mario > Cc: Andy Shevchenko ; pali.ro...@gmail.com; LKML > ;

RE: [PATCH v3 3/3] platform/x86: dell-smbios: Link all dell-smbios-* modules together

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, March 2, 2018 6:22 PM > To: Limonciello, Mario > Cc: Andy Shevchenko ; pali.ro...@gmail.com; LKML > ; platform-driver-...@vger.kernel.org > Subject: Re: [PATCH v3 3/3] platform/x86: dell-smbios: Link

Re: Removing architectures without upstream gcc support

On Wed, Feb 28, 2018 at 09:37:09AM +0100, Arnd Bergmann wrote: > On Wed, Feb 28, 2018 at 3:06 AM, Richard Kuo wrote: > > On Thu, Feb 22, 2018 at 11:43:10PM +0100, Arnd Bergmann wrote: > >> - How do I build an llvm based toolchain for Hexagon? Do I need patches > >> on top

Re: Removing architectures without upstream gcc support

On Wed, Feb 28, 2018 at 09:37:09AM +0100, Arnd Bergmann wrote: > On Wed, Feb 28, 2018 at 3:06 AM, Richard Kuo wrote: > > On Thu, Feb 22, 2018 at 11:43:10PM +0100, Arnd Bergmann wrote: > >> - How do I build an llvm based toolchain for Hexagon? Do I need patches > >> on top of the llvm-6 release

Re: [PATCH V3] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert

Hi Bart Thanks for your kindly response and directive. On 03/03/2018 12:31 AM, Bart Van Assche wrote: > On Fri, 2018-03-02 at 11:31 +0800, Jianchao Wang wrote: >> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c >> index a86df9c..d2f1838 100644 >> --- a/drivers/scsi/scsi_lib.c >>

Re: [PATCH V3] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert

Hi Bart Thanks for your kindly response and directive. On 03/03/2018 12:31 AM, Bart Van Assche wrote: > On Fri, 2018-03-02 at 11:31 +0800, Jianchao Wang wrote: >> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c >> index a86df9c..d2f1838 100644 >> --- a/drivers/scsi/scsi_lib.c >>

Re: [PATCH 1/1] mm: make start_isolate_page_range() fail if already isolated

On 03/02/2018 04:56 PM, Andrew Morton wrote: > On Fri, 2 Mar 2018 16:38:33 -0800 Mike Kravetz > wrote: > >> On 03/02/2018 04:06 PM, Andrew Morton wrote: >>> On Mon, 26 Feb 2018 11:10:54 -0800 Mike Kravetz >>> wrote: >>>

Re: [PATCH 1/1] mm: make start_isolate_page_range() fail if already isolated

On 03/02/2018 04:56 PM, Andrew Morton wrote: > On Fri, 2 Mar 2018 16:38:33 -0800 Mike Kravetz > wrote: > >> On 03/02/2018 04:06 PM, Andrew Morton wrote: >>> On Mon, 26 Feb 2018 11:10:54 -0800 Mike Kravetz >>> wrote: >>> start_isolate_page_range() is used to set the migrate type of a

[PATCH] drm/vc4: Add support for SAND modifier.

From: Dave Stevenson This is the format generated by VC4's H.264 engine, and preferred by the ISP as well. By displaying SAND buffers directly, we can avoid needing to use the ISP to rewrite the SAND H.264 output to linear before display. This is a joint effort

[PATCH] drm/vc4: Add support for SAND modifier.

From: Dave Stevenson This is the format generated by VC4's H.264 engine, and preferred by the ISP as well. By displaying SAND buffers directly, we can avoid needing to use the ISP to rewrite the SAND H.264 output to linear before display. This is a joint effort by Dave Stevenson (who wrote the

Re: [PATCH] cpu_pm: add syscore_suspend error handling

On Thu, Mar 1, 2018 at 12:39 AM, Sebastian Andrzej Siewior wrote: > On 2018-02-28 19:27:54 [-0800], Derek Basehore wrote: >> If cpu_cluster_pm_enter() fails, cpu_pm_exit() should be called. This >> will put the CPU in the correct state to resume from the failure. > > Was

Re: [PATCH] cpu_pm: add syscore_suspend error handling

On Thu, Mar 1, 2018 at 12:39 AM, Sebastian Andrzej Siewior wrote: > On 2018-02-28 19:27:54 [-0800], Derek Basehore wrote: >> If cpu_cluster_pm_enter() fails, cpu_pm_exit() should be called. This >> will put the CPU in the correct state to resume from the failure. > > Was this triggered or found

Re: [PATCH] x86/kprobe: unbalanced preempt counter with CONFIG_PREEMPT=y

On Fri, 2 Mar 2018 09:36:06 +0100 (CET) Thomas Gleixner wrote: > On Fri, 2 Mar 2018, Masami Hiramatsu wrote: > > On Thu, 1 Mar 2018 22:12:56 +0100 (CET) > > Thomas Gleixner wrote: > > > > For each kprobe hook, preempt_disable() is called twice, but > > >

Re: [PATCH] x86/kprobe: unbalanced preempt counter with CONFIG_PREEMPT=y

On Fri, 2 Mar 2018 09:36:06 +0100 (CET) Thomas Gleixner wrote: > On Fri, 2 Mar 2018, Masami Hiramatsu wrote: > > On Thu, 1 Mar 2018 22:12:56 +0100 (CET) > > Thomas Gleixner wrote: > > > > For each kprobe hook, preempt_disable() is called twice, but > > > > preempt_enable() is called once, when

Re: [PATCH 00/30] security, efi: Add kernel lockdown

On Thu, 9 Nov 2017 17:30:36 + David Howells wrote: > Here's a set of patches to institute a "locked-down mode" in the kernel and > to trigger that mode if the kernel is booted in secure-boot mode or through > the command line. > > Enabling CONFIG_LOCK_DOWN_KERNEL makes

Re: [PATCH 00/30] security, efi: Add kernel lockdown

On Thu, 9 Nov 2017 17:30:36 + David Howells wrote: > Here's a set of patches to institute a "locked-down mode" in the kernel and > to trigger that mode if the kernel is booted in secure-boot mode or through > the command line. > > Enabling CONFIG_LOCK_DOWN_KERNEL makes lockdown mode

[PATCH v2] perf/core: Add support for PMUs that can be read from more than 1 CPU

Some PMUs events can be read from more than the one CPU. So allow the PMU driver to mark events as such. For these events, we don't need to reject reads or make smp calls to the event's CPU (and cause unnecessary overhead and wake ups). When a PMU driver marks an event as such, care must be taken

[PATCH v2] perf/core: Add support for PMUs that can be read from more than 1 CPU

Some PMUs events can be read from more than the one CPU. So allow the PMU driver to mark events as such. For these events, we don't need to reject reads or make smp calls to the event's CPU (and cause unnecessary overhead and wake ups). When a PMU driver marks an event as such, care must be taken

Re: [PATCH v3 1/3] Input: gpio-keys - add support for wakeup event action

Hi Jeffy, On Fri, Mar 02, 2018 at 11:51:00AM +0800, Jeffy Chen wrote: > Add support for specifying event actions to trigger wakeup when using > the gpio-keys input device as a wakeup source. > > This would allow the device to configure when to wakeup the system. For > example a gpio-keys input

Re: [PATCH v3 1/3] Input: gpio-keys - add support for wakeup event action

Hi Jeffy, On Fri, Mar 02, 2018 at 11:51:00AM +0800, Jeffy Chen wrote: > Add support for specifying event actions to trigger wakeup when using > the gpio-keys input device as a wakeup source. > > This would allow the device to configure when to wakeup the system. For > example a gpio-keys input

Re: [PATCH v3 2/2] mm/page_alloc: fix memmap_init_zone pageblock alignment

On Sat, Mar 3, 2018 at 1:40 AM, Andrew Morton wrote: > On Sat, 3 Mar 2018 01:12:26 +0100 Daniel Vacek wrote: > >> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns >> where possible") introduced a bug where move_freepages()

Re: [PATCH v3 2/2] mm/page_alloc: fix memmap_init_zone pageblock alignment

On Sat, Mar 3, 2018 at 1:40 AM, Andrew Morton wrote: > On Sat, 3 Mar 2018 01:12:26 +0100 Daniel Vacek wrote: > >> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns >> where possible") introduced a bug where move_freepages() triggers a >> VM_BUG_ON() on uninitialized page

RE: [PATCH] pci-iov: Add support for unmanaged SR-IOV

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Saturday, March 3, 2018 2:14 AM > > On Fri, 2 Mar 2018 06:54:17 + > "Tian, Kevin" wrote: > > > > From: Alex Williamson > > > Sent: Friday, March 2, 2018 4:22 AM > > > > > > > > I am pretty sure that

RE: [PATCH] pci-iov: Add support for unmanaged SR-IOV

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Saturday, March 3, 2018 2:14 AM > > On Fri, 2 Mar 2018 06:54:17 + > "Tian, Kevin" wrote: > > > > From: Alex Williamson > > > Sent: Friday, March 2, 2018 4:22 AM > > > > > > > > I am pretty sure that you are describing is

[PATCH] acpi: edit ACPI_PROCFS_POWER help text

: linux-a...@vger.kernel.org Signed-off-by: Randy Dunlap <rdun...@infradead.org> --- drivers/acpi/Kconfig |8 1 file changed, 4 insertions(+), 4 deletions(-) --- linux-next-20180302.orig/drivers/acpi/Kconfig +++ linux-next-20180302/drivers/acpi/Kconfig @@ -105,14 +

[PATCH] acpi: edit ACPI_PROCFS_POWER help text

fig |8 1 file changed, 4 insertions(+), 4 deletions(-) --- linux-next-20180302.orig/drivers/acpi/Kconfig +++ linux-next-20180302/drivers/acpi/Kconfig @@ -105,14 +105,14 @@ config ACPI_PROCFS_POWER deprecated power /proc/acpi/ directories to exist, even when they

Re: [PATCH 1/1] mm: make start_isolate_page_range() fail if already isolated

On Fri, 2 Mar 2018 16:38:33 -0800 Mike Kravetz wrote: > On 03/02/2018 04:06 PM, Andrew Morton wrote: > > On Mon, 26 Feb 2018 11:10:54 -0800 Mike Kravetz > > wrote: > > > >> start_isolate_page_range() is used to set the migrate type of a > >>

Re: [PATCH 1/1] mm: make start_isolate_page_range() fail if already isolated

On Fri, 2 Mar 2018 16:38:33 -0800 Mike Kravetz wrote: > On 03/02/2018 04:06 PM, Andrew Morton wrote: > > On Mon, 26 Feb 2018 11:10:54 -0800 Mike Kravetz > > wrote: > > > >> start_isolate_page_range() is used to set the migrate type of a > >> set of page blocks to MIGRATE_ISOLATE while

Re: [PATCH v3 3/3] platform/x86: dell-smbios: Link all dell-smbios-* modules together

On Tue, Feb 27, 2018 at 12:23:04PM -0600, Mario Limonciello wrote: > Some race conditions were raised due to dell-smbios and its backends > not being ready by the time that a consumer would call one of the > exported methods. > > To avoid this problem, guarantee that all initialization has been >

Re: [PATCH v3 3/3] platform/x86: dell-smbios: Link all dell-smbios-* modules together

On Tue, Feb 27, 2018 at 12:23:04PM -0600, Mario Limonciello wrote: > Some race conditions were raised due to dell-smbios and its backends > not being ready by the time that a consumer would call one of the > exported methods. > > To avoid this problem, guarantee that all initialization has been >

Re: [PATCH] rcu: Remove deprecated RCU debugfs tracing code

On Fri, Mar 02, 2018 at 04:39:12PM +0900, Byungchul Park wrote: > Commit ae91aa0adb14(rcu: Remove debugfs tracing) removed the RCU debugfs > tracing code, and left deprecated code. > > Because exp_workdone{0,1,2,3} won't be used anymore since the commit, > it's better to remove code to do with

Re: [PATCH] rcu: Remove deprecated RCU debugfs tracing code

On Fri, Mar 02, 2018 at 04:39:12PM +0900, Byungchul Park wrote: > Commit ae91aa0adb14(rcu: Remove debugfs tracing) removed the RCU debugfs > tracing code, and left deprecated code. > > Because exp_workdone{0,1,2,3} won't be used anymore since the commit, > it's better to remove code to do with

Re: [PATCH 00/45] arm Spectre fix backport review for LTS 4.9

On 03/02/2018 06:30 PM, Will Deacon wrote: > On Fri, Mar 02, 2018 at 05:02:32PM +0800, Alex Shi wrote: >> As testing the spectre bug fix, that's a good question. I also asked >> this question to original patch authors, like Marc. They said they just >> figure out these patches could block

Re: [PATCH 00/45] arm Spectre fix backport review for LTS 4.9

On 03/02/2018 06:30 PM, Will Deacon wrote: > On Fri, Mar 02, 2018 at 05:02:32PM +0800, Alex Shi wrote: >> As testing the spectre bug fix, that's a good question. I also asked >> this question to original patch authors, like Marc. They said they just >> figure out these patches could block

Re: [PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

On Fri, Mar 02, 2018 at 03:06:21PM -0500, Steven Rostedt wrote: > On Thu, 1 Mar 2018 12:48:58 -0800 > "Paul E. McKenney" wrote: > > > So how about I rename cond_resched_rcu_qs() to cond_resched_tasks_rcu_qs(), > > which at least gives a hint as to where it needs to be

Re: [PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

On Fri, Mar 02, 2018 at 03:06:21PM -0500, Steven Rostedt wrote: > On Thu, 1 Mar 2018 12:48:58 -0800 > "Paul E. McKenney" wrote: > > > So how about I rename cond_resched_rcu_qs() to cond_resched_tasks_rcu_qs(), > > which at least gives a hint as to where it needs to be used? > > > > Would that

  1   2   3   4   5   6   7   8   9   10   >