Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, Nov 20, 2017 at 10:10:12PM +0100, Knut Omang wrote: > On Mon, 2017-11-20 at 21:08 +0100, Luc Van Oostenryck wrote: > > > > It should be noted though that CHECKFLAGS contains very very few > > sparse specific things. It's mainly flags for the compiler > > coming from KBUILD_CFLAGS (which

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, Nov 20, 2017 at 10:10:12PM +0100, Knut Omang wrote: > On Mon, 2017-11-20 at 21:08 +0100, Luc Van Oostenryck wrote: > > > > It should be noted though that CHECKFLAGS contains very very few > > sparse specific things. It's mainly flags for the compiler > > coming from KBUILD_CFLAGS (which

Re: [PATCH] fs: Safe rcu access to hlist.

On Mon, Nov 20, 2017 at 09:58:02PM +0100, Luc Van Oostenryck wrote: > On Mon, Nov 20, 2017 at 12:42:53PM -0800, Matthew Wilcox wrote: > > > > I disagree. The notion of whether a pointer is protected by RCU or not > > is definitely not transient. > > Sure. But what about the memory it points to?

Re: [PATCH] fs: Safe rcu access to hlist.

On Mon, Nov 20, 2017 at 09:58:02PM +0100, Luc Van Oostenryck wrote: > On Mon, Nov 20, 2017 at 12:42:53PM -0800, Matthew Wilcox wrote: > > > > I disagree. The notion of whether a pointer is protected by RCU or not > > is definitely not transient. > > Sure. But what about the memory it points to?

[PATCH] Make asus-nb-wmi support the Zenbook UX430UQ

This patch adds support for the Zenbook UX430UQ to the asus_nb_wmi driver. It also renames "quirk_asus_ux330uak" to "quirk_asus_forceals" because it is now used for more than one model of computer, and should thus have a more general name. Signed-off-by: Kiernan Hager

[PATCH] Make asus-nb-wmi support the Zenbook UX430UQ

This patch adds support for the Zenbook UX430UQ to the asus_nb_wmi driver. It also renames "quirk_asus_ux330uak" to "quirk_asus_forceals" because it is now used for more than one model of computer, and should thus have a more general name. Signed-off-by: Kiernan Hager ---

Re: [PATCH 4.14 00/31] 4.14.1-stable review

On 11/19/2017 07:59 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.1 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.14 00/31] 4.14.1-stable review

On 11/19/2017 07:59 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.1 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.13 00/28] 4.13.15-stable review

On 11/19/2017 07:43 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.13.15 release. > There are 28 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.13 00/28] 4.13.15-stable review

On 11/19/2017 07:43 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.13.15 release. > There are 28 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 00/72] 4.9.64-stable review

On 11/19/2017 07:38 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.64 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 00/72] 4.9.64-stable review

On 11/19/2017 07:38 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.64 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH 2/2] ARM: dts: TS-7970: add basic device tree

These device trees add support for TS-7970 by Technologic Systems. More details here: https://wiki.embeddedarm.com/wiki/TS-7970 Signed-off-by: Sebastien Bourdelin --- arch/arm/boot/dts/Makefile| 2 + arch/arm/boot/dts/imx6dl-ts7970.dts

[PATCH 2/2] ARM: dts: TS-7970: add basic device tree

These device trees add support for TS-7970 by Technologic Systems. More details here: https://wiki.embeddedarm.com/wiki/TS-7970 Signed-off-by: Sebastien Bourdelin --- arch/arm/boot/dts/Makefile| 2 + arch/arm/boot/dts/imx6dl-ts7970.dts | 54 +++

[PATCH 1/2] of: documentation: add bindings documentation for TS-7970

This adds the documentation for the TS-7970 by Technologic Systems. Signed-off-by: Sebastien Bourdelin --- Documentation/devicetree/bindings/arm/technologic.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 1/2] of: documentation: add bindings documentation for TS-7970

This adds the documentation for the TS-7970 by Technologic Systems. Signed-off-by: Sebastien Bourdelin --- Documentation/devicetree/bindings/arm/technologic.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/technologic.txt

Re: [PATCH 4.4 00/59] 4.4.100-stable review

On 11/19/2017 07:32 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.100 release. > There are 59 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.4 00/59] 4.4.100-stable review

On 11/19/2017 07:32 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.100 release. > There are 59 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 3.18 00/38] 3.18.83-stable review

On 11/19/2017 07:29 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.83 release. > There are 38 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 3.18 00/38] 3.18.83-stable review

On 11/19/2017 07:29 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.83 release. > There are 38 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang)

On Mon, Nov 20, 2017 at 03:21:32PM -0500, Nicolas Pitre wrote: > On Mon, 20 Nov 2017, Guenter Roeck wrote: > > > On Mon, Nov 20, 2017 at 01:18:38PM -0500, Nicolas Pitre wrote: > > > On Sun, 19 Nov 2017, Guenter Roeck wrote: > > > > > > > On 11/19/2017 08:08 PM, Nicolas Pitre wrote: > > > > > On

Re: [PATCH] KVM: VMX: Fix rflags cache during vCPU reset

On 20/11/2017 10:17, Wanpeng Li wrote: >[ cut here ] >WARNING: CPU: 6 PID: 24431 at /home/kernel/linux/arch/x86/kvm//x86.c:7302 > kvm_arch_vcpu_ioctl_run+0x651/0x2ea0 [kvm] >CPU: 6 PID: 24431 Comm: reprotest Tainted: GW OE 4.14.0+ #26 >RIP:

Re: mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang)

On Mon, Nov 20, 2017 at 03:21:32PM -0500, Nicolas Pitre wrote: > On Mon, 20 Nov 2017, Guenter Roeck wrote: > > > On Mon, Nov 20, 2017 at 01:18:38PM -0500, Nicolas Pitre wrote: > > > On Sun, 19 Nov 2017, Guenter Roeck wrote: > > > > > > > On 11/19/2017 08:08 PM, Nicolas Pitre wrote: > > > > > On

Re: [PATCH] KVM: VMX: Fix rflags cache during vCPU reset

On 20/11/2017 10:17, Wanpeng Li wrote: >[ cut here ] >WARNING: CPU: 6 PID: 24431 at /home/kernel/linux/arch/x86/kvm//x86.c:7302 > kvm_arch_vcpu_ioctl_run+0x651/0x2ea0 [kvm] >CPU: 6 PID: 24431 Comm: reprotest Tainted: GW OE 4.14.0+ #26 >RIP:

Re: [PATCH v3 2/3] leds: Add driver for Qualcomm LPG

On Sun 19 Nov 13:36 PST 2017, Jacek Anaszewski wrote: > Hi Bjorn, > > Thanks for the patch. Please refer to my comments in the code. > > On 11/15/2017 08:13 AM, Bjorn Andersson wrote: [..] > > diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig > > index 52ea34e337cd..ccc3aa4b2474 100644 >

Re: [PATCH v3 2/3] leds: Add driver for Qualcomm LPG

On Sun 19 Nov 13:36 PST 2017, Jacek Anaszewski wrote: > Hi Bjorn, > > Thanks for the patch. Please refer to my comments in the code. > > On 11/15/2017 08:13 AM, Bjorn Andersson wrote: [..] > > diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig > > index 52ea34e337cd..ccc3aa4b2474 100644 >

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, 2017-11-20 at 21:08 +0100, Luc Van Oostenryck wrote: > On Mon, Nov 20, 2017 at 12:48:35PM -0700, Jim Davis wrote: > > > > I'd be nice if people could just specify CHECK and CHECKFLAGS to run > > their favorite checker, but currently CHECKFLAGS seems hardwired for > > running sparse. So

Re: [PATCH] dt-bindings: trivial-devices: Remove fsl,mc13892

On Sat, Nov 18, 2017 at 03:22:32AM +0100, Jonathan Neuschäfer wrote: > This device's bindings are not trivial: Additional properties are > documented in in Documentation/devicetree/bindings/mfd/mc13xxx.txt. > > Signed-off-by: Jonathan Neuschäfer > --- >

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, 2017-11-20 at 21:08 +0100, Luc Van Oostenryck wrote: > On Mon, Nov 20, 2017 at 12:48:35PM -0700, Jim Davis wrote: > > > > I'd be nice if people could just specify CHECK and CHECKFLAGS to run > > their favorite checker, but currently CHECKFLAGS seems hardwired for > > running sparse. So

Re: [PATCH] dt-bindings: trivial-devices: Remove fsl,mc13892

On Sat, Nov 18, 2017 at 03:22:32AM +0100, Jonathan Neuschäfer wrote: > This device's bindings are not trivial: Additional properties are > documented in in Documentation/devicetree/bindings/mfd/mc13xxx.txt. > > Signed-off-by: Jonathan Neuschäfer > --- >

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

On Fri, Nov 17, 2017 at 11:07:46AM -0800, 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

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

On Fri, Nov 17, 2017 at 11:07:46AM -0800, 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 >

Re: [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for the SYSENTER stack

On Mon, Nov 20, 2017 at 1:00 PM, Josh Poimboeuf wrote: > On Mon, Nov 20, 2017 at 12:46:13PM -0800, Andy Lutomirski wrote: >> On Mon, Nov 20, 2017 at 12:42 PM, Josh Poimboeuf wrote: >> > On Mon, Nov 20, 2017 at 09:07:33AM -0800, Andy Lutomirski wrote: >>

Re: [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for the SYSENTER stack

On Mon, Nov 20, 2017 at 1:00 PM, Josh Poimboeuf wrote: > On Mon, Nov 20, 2017 at 12:46:13PM -0800, Andy Lutomirski wrote: >> On Mon, Nov 20, 2017 at 12:42 PM, Josh Poimboeuf wrote: >> > On Mon, Nov 20, 2017 at 09:07:33AM -0800, Andy Lutomirski wrote: >> >> +bool in_SYSENTER_stack(unsigned long

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Tue, 2017-11-21 at 01:18 +0900, Masahiro Yamada wrote: > 2017-11-17 2:01 GMT+09:00 Knut Omang : > > Add interpretation of a new environment variable P={1,2} in spirit of the > > C= option, but executing checkpatch instead of sparse. > > > > Signed-off-by: Knut Omang

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Tue, 2017-11-21 at 01:18 +0900, Masahiro Yamada wrote: > 2017-11-17 2:01 GMT+09:00 Knut Omang : > > Add interpretation of a new environment variable P={1,2} in spirit of the > > C= option, but executing checkpatch instead of sparse. > > > > Signed-off-by: Knut Omang > > Reviewed-by: Håkon

Re: [PATCH v2 00/18] Add support for clang LTO

On Mon, Nov 20, 2017 at 03:21:40PM +, Mark Rutland wrote: > Would it be possible to split this into: > > (1) (basic) arm64 clang support > (2) gold support (no LTO) > (3) LTO support > > ... with any necessary workarounds added as-required to the relevant > series? Absolutely. I'll split

Re: [PATCH v2 00/18] Add support for clang LTO

On Mon, Nov 20, 2017 at 03:21:40PM +, Mark Rutland wrote: > Would it be possible to split this into: > > (1) (basic) arm64 clang support > (2) gold support (no LTO) > (3) LTO support > > ... with any necessary workarounds added as-required to the relevant > series? Absolutely. I'll split

[PATCH] mfd: kempld-core: Use resource_size function on resource object

drivers/mfd/kempld-core.c:461:13-16: WARNING: Suspicious code. resource_size is maybe missing with ioport Generated by: scripts/coccinelle/api/resource_size.cocci Signed-off-by: Vasyl Gomonovych --- drivers/mfd/kempld-core.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] mfd: kempld-core: Use resource_size function on resource object

drivers/mfd/kempld-core.c:461:13-16: WARNING: Suspicious code. resource_size is maybe missing with ioport Generated by: scripts/coccinelle/api/resource_size.cocci Signed-off-by: Vasyl Gomonovych --- drivers/mfd/kempld-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v2 16/18] arm64: crypto: disable LTO for aes-ce-cipher.c

On Mon, Nov 20, 2017 at 03:25:31PM +, Ard Biesheuvel wrote: > However, under LTO this all changes, and it is no longer guaranteed > that the NEON registers are only touched between the kernel mode > neon begin/end calls. LTO operates on LLVM IR, so disabling LTO for this file should make sure

Re: [PATCH v2 16/18] arm64: crypto: disable LTO for aes-ce-cipher.c

On Mon, Nov 20, 2017 at 03:25:31PM +, Ard Biesheuvel wrote: > However, under LTO this all changes, and it is no longer guaranteed > that the NEON registers are only touched between the kernel mode > neon begin/end calls. LTO operates on LLVM IR, so disabling LTO for this file should make sure

Re: [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for the SYSENTER stack

On Mon, Nov 20, 2017 at 12:46:13PM -0800, Andy Lutomirski wrote: > On Mon, Nov 20, 2017 at 12:42 PM, Josh Poimboeuf wrote: > > On Mon, Nov 20, 2017 at 09:07:33AM -0800, Andy Lutomirski wrote: > >> +bool in_SYSENTER_stack(unsigned long *stack, struct stack_info *info) > > > >

Re: [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for the SYSENTER stack

On Mon, Nov 20, 2017 at 12:46:13PM -0800, Andy Lutomirski wrote: > On Mon, Nov 20, 2017 at 12:42 PM, Josh Poimboeuf wrote: > > On Mon, Nov 20, 2017 at 09:07:33AM -0800, Andy Lutomirski wrote: > >> +bool in_SYSENTER_stack(unsigned long *stack, struct stack_info *info) > > > > Can you make it

[PATCH] pinctrl: pxa: pxa2xx: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/pinctrl/pxa/pinctrl-pxa2xx.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] pinctrl: pxa: pxa2xx: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/pinctrl/pxa/pinctrl-pxa2xx.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] power: reset: zx-reboot: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/power/reset/zx-reboot.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] power: reset: zx-reboot: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/power/reset/zx-reboot.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

Re: [PATCH] fs: Safe rcu access to hlist.

On Mon, Nov 20, 2017 at 12:42:53PM -0800, Matthew Wilcox wrote: > > I disagree. The notion of whether a pointer is protected by RCU or not > is definitely not transient. Sure. But what about the memory it points to? It's just 'normal' kernel memory, there is nowhere something like some 'RCU

Re: [PATCH] fs: Safe rcu access to hlist.

On Mon, Nov 20, 2017 at 12:42:53PM -0800, Matthew Wilcox wrote: > > I disagree. The notion of whether a pointer is protected by RCU or not > is definitely not transient. Sure. But what about the memory it points to? It's just 'normal' kernel memory, there is nowhere something like some 'RCU

Re: Autoselect patches for stable (Was: Re: [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV)

On Mon, Nov 20, 2017 at 8:13 AM, Daniel Vetter wrote: > On Mon, Nov 20, 2017 at 01:39:31PM +0100, Daniel Vetter wrote: >> On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote: >> > Hi all, >> > >> > Since I'm going slightly off-topic, I've tweaked the subject line and >>

[PATCH] net: phy: cortina: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/net/phy/cortina.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file. MODULE_DESCRIPTION and

Re: Autoselect patches for stable (Was: Re: [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV)

On Mon, Nov 20, 2017 at 8:13 AM, Daniel Vetter wrote: > On Mon, Nov 20, 2017 at 01:39:31PM +0100, Daniel Vetter wrote: >> On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote: >> > Hi all, >> > >> > Since I'm going slightly off-topic, I've tweaked the subject line and >> > trimmed some of

[PATCH] net: phy: cortina: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/net/phy/cortina.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file. MODULE_DESCRIPTION and

[PATCHv2] drm: adv7511/33: Fix adv7511_cec_init() failure handling

If the device tree for a board did not specify a cec clock, then adv7511_cec_init would return an error, which would cause adv7511_probe() to fail and thus there is no HDMI output. There is no need to have adv7511_probe() fail if the CEC initialization fails, so just change adv7511_cec_init() to

[PATCHv2] drm: adv7511/33: Fix adv7511_cec_init() failure handling

If the device tree for a board did not specify a cec clock, then adv7511_cec_init would return an error, which would cause adv7511_probe() to fail and thus there is no HDMI output. There is no need to have adv7511_probe() fail if the CEC initialization fails, so just change adv7511_cec_init() to

[PATCH] mtd: nand: denali_pci: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/mtd/nand/denali_pci.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] mtd: nand: denali_pci: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/mtd/nand/denali_pci.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/media/platform/tegra-cec/tegra_cec.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/media/platform/tegra-cec/tegra_cec.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] [media] soc_camera: soc_scale_crop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/media/platform/soc_camera/soc_scale_crop.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file.

[PATCH] [media] soc_camera: soc_scale_crop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/media/platform/soc_camera/soc_scale_crop.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file.

[PATCH] iio: adc: qcom-vadc: add missing MODULE_DESCRIPTION/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/iio/adc/qcom-vadc-common.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] iio: adc: qcom-vadc: add missing MODULE_DESCRIPTION/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/iio/adc/qcom-vadc-common.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables

On Mon, 20 Nov 2017, Andy Lutomirski wrote: > On Mon, Nov 20, 2017 at 12:22 PM, Thomas Gleixner wrote: > > On Fri, 10 Nov 2017, Dave Hansen wrote: > >> __set_fixmap(get_cpu_gdt_ro_index(cpu), get_cpu_gdt_paddr(cpu), > >> prot); > >> + > >> + /* CPU 0's mapping is

Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables

On Mon, 20 Nov 2017, Andy Lutomirski wrote: > On Mon, Nov 20, 2017 at 12:22 PM, Thomas Gleixner wrote: > > On Fri, 10 Nov 2017, Dave Hansen wrote: > >> __set_fixmap(get_cpu_gdt_ro_index(cpu), get_cpu_gdt_paddr(cpu), > >> prot); > >> + > >> + /* CPU 0's mapping is done in kaiser_init()

[PATCH] iio: accel: kxsd9-i2c: add missing MODULE_AUTHOR/DESCRIPTION/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/iio/accel/kxsd9-i2c.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] iio: accel: kxsd9-i2c: add missing MODULE_AUTHOR/DESCRIPTION/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/iio/accel/kxsd9-i2c.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file.

[PATCH] gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-iop.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file. MODULE_DESCRIPTION and

Re: [PATCH 17/30] x86, kaiser: map debug IDT tables

On Mon, 20 Nov 2017, Andy Lutomirski wrote: > On Fri, Nov 10, 2017 at 11:31 AM, Dave Hansen > wrote: > > > > From: Dave Hansen > > > > The IDT is another structure which the CPU references via a > > virtual address. It also obviously

Re: [PATCH 2/3] mmc: tmio: use mmc_can_gpio_cd() instead of checking TMIO_MMC_USE_GPIO_CD

> I am puzzled by this driver. And now imagine that it is already cleaned up :) I will check these CD patches tomorrow. I need a fresh brain for that. Thanks for the work! signature.asc Description: PGP signature

Re: [PATCH 17/30] x86, kaiser: map debug IDT tables

On Mon, 20 Nov 2017, Andy Lutomirski wrote: > On Fri, Nov 10, 2017 at 11:31 AM, Dave Hansen > wrote: > > > > From: Dave Hansen > > > > The IDT is another structure which the CPU references via a > > virtual address. It also obviously needs these to handle an > > interrupt in userspace, so

Re: [PATCH 2/3] mmc: tmio: use mmc_can_gpio_cd() instead of checking TMIO_MMC_USE_GPIO_CD

> I am puzzled by this driver. And now imagine that it is already cleaned up :) I will check these CD patches tomorrow. I need a fresh brain for that. Thanks for the work! signature.asc Description: PGP signature

[PATCH] gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-iop.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file. MODULE_DESCRIPTION and

[PATCH] auxdisplay: img-ascii-lcd: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/auxdisplay/img-ascii-lcd.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file.

[PATCH] gpio: ath79: add missing MODULE_DESCRIPTION/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-ath79.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file. MODULE_DESCRIPTION is

[PATCH] auxdisplay: img-ascii-lcd: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/auxdisplay/img-ascii-lcd.o see include/linux/module.h for more information This adds the license as "GPL", which matches the header of the file.

[PATCH] gpio: ath79: add missing MODULE_DESCRIPTION/LICENSE

This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-ath79.o see include/linux/module.h for more information This adds the license as "GPL v2", which matches the header of the file. MODULE_DESCRIPTION is

Re: [PATCH v2 18/18] arm64: select ARCH_SUPPORTS_LTO_CLANG

On Mon, Nov 20, 2017 at 08:32:56PM +0100, Peter Zijlstra wrote: > On Mon, Nov 20, 2017 at 06:05:55PM +, Will Deacon wrote: > > Although the current direction of the C++ committee is to prefer > > that dependencies are explicitly "marked", this is not deemed to be > > acceptable for the kernel

Re: [PATCH v2 18/18] arm64: select ARCH_SUPPORTS_LTO_CLANG

On Mon, Nov 20, 2017 at 08:32:56PM +0100, Peter Zijlstra wrote: > On Mon, Nov 20, 2017 at 06:05:55PM +, Will Deacon wrote: > > Although the current direction of the C++ committee is to prefer > > that dependencies are explicitly "marked", this is not deemed to be > > acceptable for the kernel

Re: [PATCH v2 18/18] arm64: select ARCH_SUPPORTS_LTO_CLANG

On Mon, Nov 20, 2017 at 08:28:06PM +0100, Peter Zijlstra wrote: > On Mon, Nov 20, 2017 at 06:05:55PM +, Will Deacon wrote: > > This is a thorny issue, but RCU (specifically rcu_dereference but probably > > also some READ_ONCEs) relies on being able to utilise syntactic dependency > > chains to

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk

On 11/20/2017 01:49 PM, Christian Borntraeger wrote: > > > On 11/20/2017 08:42 PM, Jens Axboe wrote: >> On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >>> >>> >>> On 11/20/2017 08:20 PM, Bart Van Assche wrote: On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote: > This

Re: [PATCH v2 18/18] arm64: select ARCH_SUPPORTS_LTO_CLANG

On Mon, Nov 20, 2017 at 08:28:06PM +0100, Peter Zijlstra wrote: > On Mon, Nov 20, 2017 at 06:05:55PM +, Will Deacon wrote: > > This is a thorny issue, but RCU (specifically rcu_dereference but probably > > also some READ_ONCEs) relies on being able to utilise syntactic dependency > > chains to

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk

On 11/20/2017 01:49 PM, Christian Borntraeger wrote: > > > On 11/20/2017 08:42 PM, Jens Axboe wrote: >> On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >>> >>> >>> On 11/20/2017 08:20 PM, Bart Van Assche wrote: On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote: > This

[RFC] perf script: modify field selection option

Hi, I have been using the perf script -F option on the latest perf and I find it not very convenient to use. I appreciate the + and - prefix to field names to add or suppress them. But most of the time, I want to print only one or two fields and I have to guess which ones are there by default so

[RFC] perf script: modify field selection option

Hi, I have been using the perf script -F option on the latest perf and I find it not very convenient to use. I appreciate the + and - prefix to field names to add or suppress them. But most of the time, I want to print only one or two fields and I have to guess which ones are there by default so

Re: [PATCH] mfd: tmio: move register macros to tmio_core.c

On Tue, Nov 07, 2017 at 05:14:12PM +0900, Masahiro Yamada wrote: > These registers are only used in drivers/mfd/tmio_core.c > > Signed-off-by: Masahiro Yamada Well, yes, why not... Acked-by: Wolfram Sang signature.asc

Re: [PATCH] mfd: tmio: move register macros to tmio_core.c

On Tue, Nov 07, 2017 at 05:14:12PM +0900, Masahiro Yamada wrote: > These registers are only used in drivers/mfd/tmio_core.c > > Signed-off-by: Masahiro Yamada Well, yes, why not... Acked-by: Wolfram Sang signature.asc Description: PGP signature

Re: [PATCH v2 16/18] arm64: crypto: disable LTO for aes-ce-cipher.c

On Mon, Nov 20, 2017 at 03:20:14PM +, Mark Rutland wrote: > Could you elaborate on what the integrated asembler doesn't like? Here's the error, looks like in aes_sub: :1:69: error: invalid operand for instruction dup v1.4s, w12 ;movi v0.16b, #0 ;aese

Re: [PATCH v2 16/18] arm64: crypto: disable LTO for aes-ce-cipher.c

On Mon, Nov 20, 2017 at 03:20:14PM +, Mark Rutland wrote: > Could you elaborate on what the integrated asembler doesn't like? Here's the error, looks like in aes_sub: :1:69: error: invalid operand for instruction dup v1.4s, w12 ;movi v0.16b, #0 ;aese

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk

On 11/20/2017 08:42 PM, Jens Axboe wrote: > On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >> >> >> On 11/20/2017 08:20 PM, Bart Van Assche wrote: >>> On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote: This is b7a71e66d (Jens Axboe2017-08-01

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk

On 11/20/2017 08:42 PM, Jens Axboe wrote: > On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >> >> >> On 11/20/2017 08:20 PM, Bart Van Assche wrote: >>> On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote: This is b7a71e66d (Jens Axboe2017-08-01

Re: [PATCH 4/6] mmc: tmio: move mmc_host_ops to struct tmio_mmc_host from static data

> + struct mmc_host_ops mmc_host_ops; Just came to think of it: maybe a shorter name? host->ops is still nicely readable, I'd think... signature.asc Description: PGP signature

Re: [PATCH 4/6] mmc: tmio: move mmc_host_ops to struct tmio_mmc_host from static data

> + struct mmc_host_ops mmc_host_ops; Just came to think of it: maybe a shorter name? host->ops is still nicely readable, I'd think... signature.asc Description: PGP signature

Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables

On Mon, Nov 20, 2017 at 12:22 PM, Thomas Gleixner wrote: > On Fri, 10 Nov 2017, Dave Hansen wrote: >> __set_fixmap(get_cpu_gdt_ro_index(cpu), get_cpu_gdt_paddr(cpu), prot); >> + >> + /* CPU 0's mapping is done in kaiser_init() */ >> + if (cpu) { >> +

Re: [PATCH 12/30] x86, kaiser: map GDT into user page tables

On Mon, Nov 20, 2017 at 12:22 PM, Thomas Gleixner wrote: > On Fri, 10 Nov 2017, Dave Hansen wrote: >> __set_fixmap(get_cpu_gdt_ro_index(cpu), get_cpu_gdt_paddr(cpu), prot); >> + >> + /* CPU 0's mapping is done in kaiser_init() */ >> + if (cpu) { >> + int ret; >> + >> +

Re: [PATCH 6/6] mmc: tmio: move mmc_of_parse() out of tmio_mmc_host_probe()

On Tue, Nov 07, 2017 at 05:09:32PM +0900, Masahiro Yamada wrote: > mmc_of_parse() parses various DT properties and sets capability flags > accordingly. However, drivers have no chance to run platform init > code depending on such flags because mmc_of_parse() is called from >

Re: [PATCH 6/6] mmc: tmio: move mmc_of_parse() out of tmio_mmc_host_probe()

On Tue, Nov 07, 2017 at 05:09:32PM +0900, Masahiro Yamada wrote: > mmc_of_parse() parses various DT properties and sets capability flags > accordingly. However, drivers have no chance to run platform init > code depending on such flags because mmc_of_parse() is called from >

Re: [PATCH 20/30] x86, mm: remove hard-coded ASID limit checks

On Fri, 10 Nov 2017, Dave Hansen wrote: > > +/* There are 12 bits of space for ASIDS in CR3 */ > +#define CR3_HW_ASID_BITS 12 > +/* When enabled, KAISER consumes a single bit for user/kernel switches */ > +#define KAISER_CONSUMED_ASID_BITS 0 > + > +#define CR3_AVAIL_ASID_BITS

Re: [PATCH 20/30] x86, mm: remove hard-coded ASID limit checks

On Fri, 10 Nov 2017, Dave Hansen wrote: > > +/* There are 12 bits of space for ASIDS in CR3 */ > +#define CR3_HW_ASID_BITS 12 > +/* When enabled, KAISER consumes a single bit for user/kernel switches */ > +#define KAISER_CONSUMED_ASID_BITS 0 > + > +#define CR3_AVAIL_ASID_BITS

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