Re: [GIT PULL] pin control bulk changes for v4.16

o bring it down > into the .c file? Would the need for that actually indicate that the > include file is designed incorrectly? I put a bit of an explanation in this commit: commit d47529b2e9fe0ec2eb1f072afad8849f52e385c4 Author: Paul Gortmaker Date: Mon Sep 12 18:16:31 2016 -0400

Re: [PATCH] tools: fix cross-compile var export

[Re: [PATCH] tools: fix cross-compile var export] On 07/01/2018 (Sun 10:31) Martin Kelly wrote: [...] > With the change, we add do CC = $(CROSS_COMPILE)gcc if and only if CC is not > already set. I'm happy to add all these details to the commit description. That is probably a step in the right

Re: [PATCH] tools: fix cross-compile var export

[Re: [PATCH] tools: fix cross-compile var export] On 07/01/2018 (Sun 10:31) Martin Kelly wrote: [...] > With the change, we add do CC = $(CROSS_COMPILE)gcc if and only if CC is not > already set. I'm happy to add all these details to the commit description. That is probably a step in the right

Re: [PATCH] tools: fix cross-compile var export

[[PATCH] tools: fix cross-compile var export] On 06/01/2018 (Sat 12:16) Martin Kelly wrote: > From: Martin Kelly > > Currently in a number of Makefiles, we clobber the CC, LD, and/or STRIP env > vars > when cross-compiling, which breaks any additional flags that might

Re: [PATCH] tools: fix cross-compile var export

[[PATCH] tools: fix cross-compile var export] On 06/01/2018 (Sat 12:16) Martin Kelly wrote: > From: Martin Kelly > > Currently in a number of Makefiles, we clobber the CC, LD, and/or STRIP env > vars > when cross-compiling, which breaks any additional flags that might be set > (such > as

Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.

[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On 29/12/2017 (Fri 10:47) Josh Poimboeuf wrote: > This seems to be related to a kconfig quirk where only silentoldconfig > updates the include/config/auto.conf file. The other config targets > (oldconfig, defconfig,

Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.

[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On 29/12/2017 (Fri 10:47) Josh Poimboeuf wrote: > This seems to be related to a kconfig quirk where only silentoldconfig > updates the include/config/auto.conf file. The other config targets > (oldconfig, defconfig,

Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.

[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On 28/12/2017 (Thu 11:29) Randy Dunlap wrote: > On 12/25/2017 08:30 PM, Paul Gortmaker wrote: > > There is a regression new to 4.15 that happens in a rather common > > workflow which results in the frustr

Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.

[Re: [Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.] On 28/12/2017 (Thu 11:29) Randy Dunlap wrote: > On 12/25/2017 08:30 PM, Paul Gortmaker wrote: > > There is a regression new to 4.15 that happens in a rather common > > workflow which results in the frustr

[Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.

There is a regression new to 4.15 that happens in a rather common workflow which results in the frustrating situation where the user has clearly disabled UNWINDER_ORC in their ".config" file, and yet they still get the immediate false error saying they need libelf-dev since "CONFIG_UNWINDER_ORC=y"

[Regression 4.15] Can't kill CONFIG_UNWINDER_ORC with fire or plague.

There is a regression new to 4.15 that happens in a rather common workflow which results in the frustrating situation where the user has clearly disabled UNWINDER_ORC in their ".config" file, and yet they still get the immediate false error saying they need libelf-dev since "CONFIG_UNWINDER_ORC=y"

Re: [PATCH] lib: add module unload support to sort tests

[Re: [PATCH] lib: add module unload support to sort tests] On 19/12/2017 (Tue 23:10) Pravin Shedge wrote: > On Tue, Dec 19, 2017 at 3:51 AM, Andrew Morton > wrote: > > On Sun, 17 Dec 2017 15:19:27 +0530 Pravin Shedge > > wrote: > > >

Re: [PATCH] lib: add module unload support to sort tests

[Re: [PATCH] lib: add module unload support to sort tests] On 19/12/2017 (Tue 23:10) Pravin Shedge wrote: > On Tue, Dec 19, 2017 at 3:51 AM, Andrew Morton > wrote: > > On Sun, 17 Dec 2017 15:19:27 +0530 Pravin Shedge > > wrote: > > > >> test_sort.c perform array-based and linked list sort

Re: [PATCH] init/version: include instead of

[[PATCH] init/version: include instead of ] On 21/09/2017 (Thu 00:23) Masahiro Yamada wrote: > init/version.c has nothing to do with module, so remove > the . > > Instead, include for EXPORT_SYMBOL_GPL. I checked and there weren't any __init lurking in that file which is the usual other

Re: [PATCH] init/version: include instead of

[[PATCH] init/version: include instead of ] On 21/09/2017 (Thu 00:23) Masahiro Yamada wrote: > init/version.c has nothing to do with module, so remove > the . > > Instead, include for EXPORT_SYMBOL_GPL. I checked and there weren't any __init lurking in that file which is the usual other

[PATCH-next] bus: fsl-mc: fix implicit irq include causing build fails

dpaa2_io_irq(struct dpaa2_io *obj); ^ as seen on arm64 allmodconfig builds. Cc: Stuart Yoder <stuyo...@gmail.com> Cc: Laurentiu Tudor <laurentiu.tu...@nxp.com> Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- [Se

[PATCH-next] bus: fsl-mc: fix implicit irq include causing build fails

dpaa2_io_irq(struct dpaa2_io *obj); ^ as seen on arm64 allmodconfig builds. Cc: Stuart Yoder Cc: Laurentiu Tudor Cc: Greg Kroah-Hartman Signed-off-by: Paul Gortmaker --- [Seen on current linux-next tree.] drivers/staging/fsl-mc/include/dpaa2-io.h | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH-next] IB/hns: fix implicit irq include causing build fails in roce_eq

ail.com> Cc: linux-r...@vger.kernel.org Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- [ Seen on current linux-next tree. ] drivers/infiniband/hw/hns/hns_roce_eq.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/infiniband/hw/hns/hns_roce_eq.c b/dri

[PATCH-next] IB/hns: fix implicit irq include causing build fails in roce_eq

_table->eq + j); ^ as seen on arm64 allmodconfig builds. Cc: Lijun Ou Cc: "Wei Hu(Xavier)" Cc: Doug Ledford Cc: Sean Hefty Cc: Hal Rosenstock Cc: linux-r...@vger.kernel.org Signed-off-by: Paul Gortmaker --- [ Seen on current linux-next tree. ] drivers/infiniband/hw/hns/hns

Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular

[RE: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular] On 06/06/2017 (Tue 15:27) Steve Twiss wrote: > Hi Paul, > > On 05 June 2017 20:30, Paul Gortmaker wrote: > > > Subject: Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular > > > > [RE:

Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular

[RE: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular] On 06/06/2017 (Tue 15:27) Steve Twiss wrote: > Hi Paul, > > On 05 June 2017 20:30, Paul Gortmaker wrote: > > > Subject: Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular > > > > [RE:

Re: [PATCH 3/4] mfd: da9055-core: make it explicitly non-modular

it tree, please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Paul-Gortmaker/mfd-make-da90xx-drivers-explicitly-non-modular/20170603-211054 > base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git > for-mfd

Re: [PATCH 3/4] mfd: da9055-core: make it explicitly non-modular

it tree, please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Paul-Gortmaker/mfd-make-da90xx-drivers-explicitly-non-modular/20170603-211054 > base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git > for-mfd

Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular

[Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular] On 05/06/2017 (Mon 11:36) Lee Jones wrote: > On Sat, 03 Jun 2017, Paul Gortmaker wrote: > > > The Kconfig currently controlling compilation of this code is: > > > > drivers/mfd/Kconfig:config PMIC_DA903X

Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular

[Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular] On 05/06/2017 (Mon 11:36) Lee Jones wrote: > On Sat, 03 Jun 2017, Paul Gortmaker wrote: > > > The Kconfig currently controlling compilation of this code is: > > > > drivers/mfd/Kconfig:config PMIC_DA903X

Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular

[RE: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular] On 05/06/2017 (Mon 10:30) Steve Twiss wrote: > Hi Paul, > > On 03 June 2017 14:04 Paul Gortmaker wrote: > > > To: linux-kernel@vger.kernel.org > > Cc: Paul Gortmaker; Support Opensource; Lee Jones;

Re: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular

[RE: [PATCH 1/4] mfd: da903x: Make it explicitly non-modular] On 05/06/2017 (Mon 10:30) Steve Twiss wrote: > Hi Paul, > > On 03 June 2017 14:04 Paul Gortmaker wrote: > > > To: linux-kernel@vger.kernel.org > > Cc: Paul Gortmaker; Support Opensource; Lee Jones;

[PATCH 1/4] mfd: da903x: Make it explicitly non-modular

formation is already contained at the top of the file in the comments. Cc: Support Opensource <support.opensou...@diasemi.com> Cc: Lee Jones <lee.jo...@linaro.org> Cc: Eric Miao <eric.m...@marvell.com> Cc: Mike Rapoport <m...@compulab.co.il> Signed-off-by: Paul Gortmaker <

[PATCH 1/4] mfd: da903x: Make it explicitly non-modular

formation is already contained at the top of the file in the comments. Cc: Support Opensource Cc: Lee Jones Cc: Eric Miao Cc: Mike Rapoport Signed-off-by: Paul Gortmaker --- drivers/mfd/da903x.c | 26 +++--- 1 file changed, 3 insertions(+), 23 deletions(-) diff --git a/dr

[PATCH 4/4] mfd: da9055-i2c: Make it explicitly non-modular

> Cc: Lee Jones <lee.jo...@linaro.org> Cc: David Dajun Chen <dc...@diasemi.com> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/mfd/da9055-i2c.c | 24 ++-- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/drivers/mfd/d

[PATCH 4/4] mfd: da9055-i2c: Make it explicitly non-modular

jun Chen Signed-off-by: Paul Gortmaker --- drivers/mfd/da9055-i2c.c | 24 ++-- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/drivers/mfd/da9055-i2c.c b/drivers/mfd/da9055-i2c.c index b53e100f577c..7c66f82522f0 100644 --- a/drivers/mfd/da9055-i2c.c +++ b/drivers/mfd/d

[PATCH 3/4] mfd: da9055-core: make it explicitly non-modular

We replace module.h with init.h and export.h ; the latter since the file does export some symbols Cc: Support Opensource <support.opensou...@diasemi.com> Cc: Lee Jones <lee.jo...@linaro.org> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/mfd/da9055-core.

[PATCH 2/4] mfd: da9052-*: Make it explicitly non-modular

iasemi.com> Cc: Lee Jones <lee.jo...@linaro.org> Cc: David Dajun Chen <dc...@diasemi.com> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/mfd/da9052-core.c | 11 --- drivers/mfd/da9052-i2c.c | 22 ++ drivers/mfd/

[PATCH 3/4] mfd: da9055-core: make it explicitly non-modular

We replace module.h with init.h and export.h ; the latter since the file does export some symbols Cc: Support Opensource Cc: Lee Jones Signed-off-by: Paul Gortmaker --- drivers/mfd/da9055-core.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/drivers/mfd/da905

[PATCH 2/4] mfd: da9052-*: Make it explicitly non-modular

with this commit. We replace module.h with init.h where required, i.e. if the the file did not include that already. We also delete the MODULE_LICENSE tag etc. since all that information is already contained at the top of the files in the comments. Cc: Support Opensource Cc: Lee Jones Cc: David D

[PATCH 0/4] mfd: make da90xx drivers explicitly non-modular

at summary speaks for itself. Paul Gortmaker (4): mfd: da903x: Make it explicitly non-modular mfd: da9052-*: Make it explicitly non-modular mfd: da9055-core: make it explicitly non-modular mfd: da9055-i2c: Make it explicitly non-modular drivers/mfd/da903x.c

[PATCH 0/4] mfd: make da90xx drivers explicitly non-modular

at summary speaks for itself. Paul Gortmaker (4): mfd: da903x: Make it explicitly non-modular mfd: da9052-*: Make it explicitly non-modular mfd: da9055-core: make it explicitly non-modular mfd: da9055-i2c: Make it explicitly non-modular drivers/mfd/da903x.c

Re: [PATCH] s390: kernel: Delete an error message for a failed memory allocation in cpcmd()

[[PATCH] s390: kernel: Delete an error message for a failed memory allocation in cpcmd()] On 25/05/2017 (Thu 19:18) SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 25 May 2017 19:09:50 +0200 > > Omit an extra message for a memory allocation failure

Re: [PATCH] s390: kernel: Delete an error message for a failed memory allocation in cpcmd()

[[PATCH] s390: kernel: Delete an error message for a failed memory allocation in cpcmd()] On 25/05/2017 (Thu 19:18) SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 25 May 2017 19:09:50 +0200 > > Omit an extra message for a memory allocation failure in this function. > Since I

Re: [PATCH] sparc64: Add 16GB hugepage support

[[PATCH] sparc64: Add 16GB hugepage support] On 24/05/2017 (Wed 17:29) Nitin Gupta wrote: > Orabug: 25362942 > > Signed-off-by: Nitin Gupta If this wasn't an accidental git send-email misfire, then there should be a long log indicating the use case, the perforamnce

Re: [PATCH] sparc64: Add 16GB hugepage support

[[PATCH] sparc64: Add 16GB hugepage support] On 24/05/2017 (Wed 17:29) Nitin Gupta wrote: > Orabug: 25362942 > > Signed-off-by: Nitin Gupta If this wasn't an accidental git send-email misfire, then there should be a long log indicating the use case, the perforamnce increase, the testing that

Re: [PATCH 3/3] pinctrl: bcm: clean up modular vs. non-modular distinctions

Paul -- From 3f8bf38bcdbf3848418965aac2748cc1d5cd Mon Sep 17 00:00:00 2001 From: Paul Gortmaker <paul.gortma...@windriver.com> Date: Mon, 31 Aug 2015 17:35:47 -0400 Subject: [PATCH] pinctrl: bcm: clean up modular vs. non-modular distinctions Fixups here tend to be more of a conglomerate of some of the othe

Re: [PATCH 3/3] pinctrl: bcm: clean up modular vs. non-modular distinctions

Paul -- From 3f8bf38bcdbf3848418965aac2748cc1d5cd Mon Sep 17 00:00:00 2001 From: Paul Gortmaker Date: Mon, 31 Aug 2015 17:35:47 -0400 Subject: [PATCH] pinctrl: bcm: clean up modular vs. non-modular distinctions Fixups here tend to be more of a conglomerate of some of the other repeated/systematic ones we've seen

Re: [PATCH 1/3] pinctrl: samsung: clean up modular vs. non-modular distinctions

[Re: [PATCH 1/3] pinctrl: samsung: clean up modular vs. non-modular distinctions] On 23/05/2017 (Tue 16:51) Krzysztof Kozlowski wrote: > On Mon, May 22, 2017 at 10:56 PM, Paul Gortmaker > <paul.gortma...@windriver.com> wrote: > > Fixups here tend to be more all over the map vs.

Re: [PATCH 1/3] pinctrl: samsung: clean up modular vs. non-modular distinctions

[Re: [PATCH 1/3] pinctrl: samsung: clean up modular vs. non-modular distinctions] On 23/05/2017 (Tue 16:51) Krzysztof Kozlowski wrote: > On Mon, May 22, 2017 at 10:56 PM, Paul Gortmaker > wrote: > > Fixups here tend to be more all over the map vs. some of the other > > repeat

[PATCH 0/3] pinctrl: bcm/samsung/tegra: make bool code non-modular

Cc: Thierry Reding <thierry.red...@gmail.com> Cc: Thomas Abraham <thomas...@samsung.com> Cc: Tomasz Figa <tomasz.f...@gmail.com> Cc: linux-g...@vger.kernel.org Cc: linux-rpi-ker...@lists.infradead.org Cc: linux-samsung-...@vger.kernel.org Cc: linux-te...@vger.kernel.org Paul Gortmaker (3):

[PATCH 0/3] pinctrl: bcm/samsung/tegra: make bool code non-modular

Cc: Tomasz Figa Cc: linux-g...@vger.kernel.org Cc: linux-rpi-ker...@lists.infradead.org Cc: linux-samsung-...@vger.kernel.org Cc: linux-te...@vger.kernel.org Paul Gortmaker (3): pinctrl: samsung: clean up modular vs. non-modular distinctions pinctrl: tegra: clean up modular vs. non-modular

[PATCH 3/3] pinctrl: bcm: clean up modular vs. non-modular distinctions

m> Cc: Scott Branden <sbran...@broadcom.com> Cc: Stefan Wahren <stefan.wah...@i2se.com> Cc: Sherman Yin <s...@broadcom.com> Cc: bcm-kernel-feedback-l...@broadcom.com Cc: linux-g...@vger.kernel.org Cc: linux-rpi-ker...@lists.infradead.org Signed-off-by: Paul Gortmaker <paul.gortma

[PATCH 3/3] pinctrl: bcm: clean up modular vs. non-modular distinctions

: linux-rpi-ker...@lists.infradead.org Signed-off-by: Paul Gortmaker --- drivers/pinctrl/bcm/pinctrl-bcm281xx.c | 16 drivers/pinctrl/bcm/pinctrl-bcm2835.c| 20 +++- drivers/pinctrl/bcm/pinctrl-cygnus-mux.c | 11 +-- 3 files changed, 16 insertions(+), 31

[PATCH 2/3] pinctrl: tegra: clean up modular vs. non-modular distinctions

mail.com> Cc: Pritesh Raithatha <praitha...@nvidia.com> Cc: Ashwini Ghuge <agh...@nvidia.com> Cc: linux-g...@vger.kernel.org Cc: linux-te...@vger.kernel.org Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/pinctrl/tegra/pinctrl-tegra.c| 1 - dri

[PATCH 1/3] pinctrl: samsung: clean up modular vs. non-modular distinctions

cked-by: Sylwester Nawrocki <s.nawro...@samsung.com> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/pinctrl/samsung/pinctrl-exynos.c | 1 - drivers/pinctrl/samsung/pinctrl-exynos5440.c | 15 +++ drivers/pinctrl/samsung/pinctrl-s3c24xx.c| 2 +- d

[PATCH 1/3] pinctrl: samsung: clean up modular vs. non-modular distinctions

that information was (or is now) contained at the top of the file in the comments. Cc: Tomasz Figa Cc: Thomas Abraham Cc: Linus Walleij Cc: linux-samsung-...@vger.kernel.org Cc: linux-g...@vger.kernel.org Acked-by: Sylwester Nawrocki Signed-off-by: Paul Gortmaker --- drivers/pinctrl/samsung/pinctrl

[PATCH 2/3] pinctrl: tegra: clean up modular vs. non-modular distinctions

Signed-off-by: Paul Gortmaker --- drivers/pinctrl/tegra/pinctrl-tegra.c| 1 - drivers/pinctrl/tegra/pinctrl-tegra114.c | 11 --- drivers/pinctrl/tegra/pinctrl-tegra124.c | 11 --- drivers/pinctrl/tegra/pinctrl-tegra20.c | 11 --- drivers/pinctrl/tegra/pinctrl-tegra210

Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver

[Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver] On 21/05/2017 (Sun 11:51) Hans de Goede wrote: > Hi, > > On 20-05-17 21:26, Paul Gortmaker wrote: > >On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker > ><paul.gortma...@windriver.com> wrote: > >>O

Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver

[Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver] On 21/05/2017 (Sun 11:51) Hans de Goede wrote: > Hi, > > On 20-05-17 21:26, Paul Gortmaker wrote: > >On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker > > wrote: > >>On Mon, May 15, 2017 at 2:20 PM,

Re: [PATCH v2 10/18] pinctrl: madera: Add driver for Cirrus Logic Madera codecs

On Fri, Apr 28, 2017 at 3:39 AM, Linus Walleij wrote: > On Mon, Apr 24, 2017 at 6:08 PM, Richard Fitzgerald > wrote: > >> These codecs have a variable number of I/O lines each of which >> is individually selectable to a wide range of

Re: [PATCH v2 10/18] pinctrl: madera: Add driver for Cirrus Logic Madera codecs

On Fri, Apr 28, 2017 at 3:39 AM, Linus Walleij wrote: > On Mon, Apr 24, 2017 at 6:08 PM, Richard Fitzgerald > wrote: > >> These codecs have a variable number of I/O lines each of which >> is individually selectable to a wide range of possible functions. >> >> The functionality is slightly

Re: [PATCH v3 1/2] PCI: mediatek: Add Mediatek PCIe host controller support

On Tue, May 9, 2017 at 10:06 PM, Ryder Lee wrote: > Add support for the Mediatek PCIe Gen2 controller which can > be found on MT7623 series SoCs. > > Signed-off-by: Ryder Lee > --- > drivers/pci/host/Kconfig | 11 + >

Re: [PATCH v3 1/2] PCI: mediatek: Add Mediatek PCIe host controller support

On Tue, May 9, 2017 at 10:06 PM, Ryder Lee wrote: > Add support for the Mediatek PCIe Gen2 controller which can > be found on MT7623 series SoCs. > > Signed-off-by: Ryder Lee > --- > drivers/pci/host/Kconfig | 11 + > drivers/pci/host/Makefile| 1 + >

Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver

On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker <paul.gortma...@windriver.com> wrote: > On Mon, May 15, 2017 at 2:20 PM, Hans de Goede <hdego...@redhat.com> wrote: >> Hi, >> >> This is actually v7, with the following changes: >> >> Changes in v7: &

Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver

On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker wrote: > On Mon, May 15, 2017 at 2:20 PM, Hans de Goede wrote: >> Hi, >> >> This is actually v7, with the following changes: >> >> Changes in v7: >> -Add explanation why this is a bool and why it s

Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver

On Mon, May 15, 2017 at 2:20 PM, Hans de Goede wrote: > Hi, > > This is actually v7, with the following changes: > > Changes in v7: > -Add explanation why this is a bool and why it selects i2c-designwaree > to the help text rather then as comments in the Kconfig I just

Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver

On Mon, May 15, 2017 at 2:20 PM, Hans de Goede wrote: > Hi, > > This is actually v7, with the following changes: > > Changes in v7: > -Add explanation why this is a bool and why it selects i2c-designwaree > to the help text rather then as comments in the Kconfig I just noticed the changelog

Re: [PATCH 8/9] pinctrl: mvebu: add driver for Armada CP110 pinctrl

On Fri, May 19, 2017 at 12:04 PM, Gregory CLEMENT wrote: > From: Hanna Hawa > > This commit adds a pinctrl driver for the CP110 part of the Marvell > Armada 7K and 8K SoCs. The Armada 7K has a single CP110, where almost all > the MPP pins

Re: [PATCH 8/9] pinctrl: mvebu: add driver for Armada CP110 pinctrl

On Fri, May 19, 2017 at 12:04 PM, Gregory CLEMENT wrote: > From: Hanna Hawa > > This commit adds a pinctrl driver for the CP110 part of the Marvell > Armada 7K and 8K SoCs. The Armada 7K has a single CP110, where almost all > the MPP pins are available. On the other side, the Armada 8K has two >

Re: [PATCH 7/9] pinctrl: mvebu: add driver for Armada AP806 pinctrl

On Fri, May 19, 2017 at 12:04 PM, Gregory CLEMENT wrote: > From: Hanna Hawa > > This commit adds a pinctrl driver for the pin-muxing controller found in > the AP806 part of the Marvell Armada 7K and 8K SoCs. Its register > interface is

Re: [PATCH 7/9] pinctrl: mvebu: add driver for Armada AP806 pinctrl

On Fri, May 19, 2017 at 12:04 PM, Gregory CLEMENT wrote: > From: Hanna Hawa > > This commit adds a pinctrl driver for the pin-muxing controller found in > the AP806 part of the Marvell Armada 7K and 8K SoCs. Its register > interface is compatible with the one used by previous mvebu pin >

Re: linux-next: Tree for May 16 (net/core)

On Tue, May 16, 2017 at 12:28 PM, Randy Dunlap wrote: > On 05/15/17 18:21, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20170515: >> > > on i386 or x86_64: > > when CONFIG_INET is not enabled: > > ../net/core/sock.c: In function 'skb_orphan_partial': >

Re: linux-next: Tree for May 16 (net/core)

On Tue, May 16, 2017 at 12:28 PM, Randy Dunlap wrote: > On 05/15/17 18:21, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20170515: >> > > on i386 or x86_64: > > when CONFIG_INET is not enabled: > > ../net/core/sock.c: In function 'skb_orphan_partial': > ../net/core/sock.c:1810:2: error:

[PATCH -next] soc/qbman: fix implicit header dependency now causing build fails

e.de> Cc: Scott Wood <o...@buserror.net> Cc: linuxppc-...@lists.ozlabs.org Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/soc/fsl/qbman/qman_portal.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/soc/fsl/qbman/qman_portal.c b/drivers/soc/fsl/

[PATCH -next] soc/qbman: fix implicit header dependency now causing build fails

t Wood Cc: linuxppc-...@lists.ozlabs.org Signed-off-by: Paul Gortmaker --- drivers/soc/fsl/qbman/qman_portal.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/soc/fsl/qbman/qman_portal.c b/drivers/soc/fsl/qbman/qman_portal.c index adbaa30d3c5a..4a6a8ae5e0aa 100644 --- a/drivers/soc/fsl/qbman

Re: linux-next: Tree for Apr 24

es of bug > fix patches pending for the current merge release). > > Stats about the size of the tree over time can be seen at > http://neuling.org/linux-next-size.html . > > Status of my local build tests will be at > http://kisskb.ellerman.id.au/linux-next . If maintainers want to give

Re: linux-next: Tree for Apr 24

t merge release). > > Stats about the size of the tree over time can be seen at > http://neuling.org/linux-next-size.html . > > Status of my local build tests will be at > http://kisskb.ellerman.id.au/linux-next . If maintainers want to give > advice about cross compilers/configs that work,

[PATCH] pinctrl: make artpec6 explicitly non-modular

ments. Cc: Jesper Nilsson <jesper.nils...@axis.com> Cc: Lars Persson <lars.pers...@axis.com> Cc: Niklas Cassel <niklas.cas...@axis.com> Cc: Linus Walleij <linus.wall...@linaro.org> Cc: linux-arm-ker...@axis.com Cc: linux-g...@vger.kernel.org Signed-off-by: Paul Gortmaker <paul.

[PATCH] pinctrl: make artpec6 explicitly non-modular

ments. Cc: Jesper Nilsson Cc: Lars Persson Cc: Niklas Cassel Cc: Linus Walleij Cc: linux-arm-ker...@axis.com Cc: linux-g...@vger.kernel.org Signed-off-by: Paul Gortmaker --- drivers/pinctrl/pinctrl-artpec6.c | 12 1 file changed, 12 deletions(-) diff --git a/drivers/pinctrl/pinctrl-ar

Re: [PATCH v2] crypto: arm64/sha: Add constant operand modifier to ASM_EXPORT

On Wed, Apr 5, 2017 at 2:34 PM, Matthias Kaehlcke wrote: > The operand is an integer constant, make the constness explicit by > adding the modifier. This is needed for clang to generate valid code > and also works with gcc. Actually it doesn't work with all gcc. I've got an

Re: [PATCH v2] crypto: arm64/sha: Add constant operand modifier to ASM_EXPORT

On Wed, Apr 5, 2017 at 2:34 PM, Matthias Kaehlcke wrote: > The operand is an integer constant, make the constness explicit by > adding the modifier. This is needed for clang to generate valid code > and also works with gcc. Actually it doesn't work with all gcc. I've got an older arm64

Re: [PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular

[Re: [PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular] On 14/04/2017 (Fri 10:12) Greg Kroah-Hartman wrote: > On Wed, Apr 12, 2017 at 09:57:55PM -0400, Paul Gortmaker wrote: > > The Makefile / Kconfig currently controlling compilation of this code is: >

Re: [PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular

[Re: [PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular] On 14/04/2017 (Fri 10:12) Greg Kroah-Hartman wrote: > On Wed, Apr 12, 2017 at 09:57:55PM -0400, Paul Gortmaker wrote: > > The Makefile / Kconfig currently controlling compilation of this code is: >

Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.

[Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.] On 13/04/2017 (Thu 15:12) Michael Ellerman wrote: > Stephen Rothwell <s...@canb.auug.org.au> writes: > > > Hi Paul, > > > > On Wed, 12 Apr 2017 20:30:14 -0400 Paul Gortmaker > >

Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.

[Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.] On 13/04/2017 (Thu 15:12) Michael Ellerman wrote: > Stephen Rothwell writes: > > > Hi Paul, > > > > On Wed, 12 Apr 2017 20:30:14 -0400 Paul Gortmaker > > wrote: > >> > >

Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.

[Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.] On 13/04/2017 (Thu 13:27) Stephen Rothwell wrote: > Hi Paul, > > On Wed, 12 Apr 2017 20:30:14 -0400 Paul Gortmaker > <paul.gortma...@windriver.com> wrote: > > > > Since ia64 and ppc64 don

Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.

[Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.] On 13/04/2017 (Thu 13:27) Stephen Rothwell wrote: > Hi Paul, > > On Wed, 12 Apr 2017 20:30:14 -0400 Paul Gortmaker > wrote: > > > > Since ia64 and ppc64 don't set CONFIG_64BIT, they w

[PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular

n.org> Cc: Alan Cox <a...@linux.intel.com> Cc: linux-me...@vger.kernel.org Cc: de...@driverdev.osuosl.org Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- .../media/atomisp/platform/clock/vlv2_plat_clock.c | 21 + 1 file changed, 1 insertion(+), 20 deletion

[PATCH] staging/media: make atomisp vlv2_plat_clock explicitly non-modular

org Cc: de...@driverdev.osuosl.org Signed-off-by: Paul Gortmaker --- .../media/atomisp/platform/clock/vlv2_plat_clock.c | 21 + 1 file changed, 1 insertion(+), 20 deletions(-) diff --git a/drivers/staging/media/atomisp/platform/clock/vlv2_plat_clock.c b/drivers/staging/media/atomisp/plat

[PATCH 2/4] mm/hmm: fix warnings and SECTION_SIZE definition overlap

dia.com> Cc: Sherry Cheung <sche...@nvidia.com> Cc: Subhash Gutti <sgu...@nvidia.com> Cc: Andrew Morton <a...@linux-foundation.org> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- mm/hmm.c | 24 +--- 1 file changed, 13 insertions

[PATCH 2/4] mm/hmm: fix warnings and SECTION_SIZE definition overlap

plug header being present, and (2) the arch_remove_memory() support depends on CONFIG_MEMORY_HOTREMOVE. So we fix that as well. Cc: Jérôme Glisse Cc: Evgeny Baskakov Cc: John Hubbard Cc: Mark Hairgrove Cc: Sherry Cheung Cc: Subhash Gutti Cc: Andrew Morton Signed-off-by: Paul Gort

[PATCH 3/4] mm/hmm: fix Kconfig to have valid usage of "select"

rry Cheung <sche...@nvidia.com> Cc: Subhash Gutti <sgu...@nvidia.com> Cc: Andrew Morton <a...@linux-foundation.org> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- mm/Kconfig | 22 -- 1 file changed, 8 insertions(+), 14 deletions(-) diff --

[PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.

; Cc: Andrew Morton <a...@linux-foundation.org> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- mm/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/Kconfig b/mm/Kconfig index 3e9c31bf9aaa..6c27d2003a63 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -293,6 +2

[PATCH 1/4] mm/hmm: make it explicitly non-modular

gli...@redhat.com> Cc: Evgeny Baskakov <ebaska...@nvidia.com> Cc: John Hubbard <jhubb...@nvidia.com> Cc: Mark Hairgrove <mhairgr...@nvidia.com> Cc: Sherry Cheung <sche...@nvidia.com> Cc: Subhash Gutti <sgu...@nvidia.com> Cc: Andrew Morton <a...@linux-founda

[PATCH 3/4] mm/hmm: fix Kconfig to have valid usage of "select"

ed to the end user. So delete it, but ensure the two child options point to the Documentation/vm/hmm.txt file. Cc: Jérôme Glisse Cc: Evgeny Baskakov Cc: John Hubbard Cc: Mark Hairgrove Cc: Sherry Cheung Cc: Subhash Gutti Cc: Andrew Morton Signed-off-by: Paul Gortmaker --- mm/Kconfig | 22 ---

[PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.

d to build and function. Cc: Jérôme Glisse Cc: Evgeny Baskakov Cc: John Hubbard Cc: Mark Hairgrove Cc: Sherry Cheung Cc: Subhash Gutti Cc: Andrew Morton Signed-off-by: Paul Gortmaker --- mm/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/Kconfig b/mm/Kconfig index 3e

[PATCH 1/4] mm/hmm: make it explicitly non-modular

: Evgeny Baskakov Cc: John Hubbard Cc: Mark Hairgrove Cc: Sherry Cheung Cc: Subhash Gutti Cc: Andrew Morton Signed-off-by: Paul Gortmaker --- mm/hmm.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/mm/hmm.c b/mm/hmm.c index f567a8b3b079..8200cf275fb9 100644

[PATCH akpm/next 0/4] Fix various issues in new hmm driver

gr...@nvidia.com> Cc: Sherry Cheung <sche...@nvidia.com> Cc: Subhash Gutti <sgu...@nvidia.com> Cc: Andrew Morton <a...@linux-foundation.org> --- Paul Gortmaker (4): mm/hmm: make it explicitly non-modular mm/hmm: fix warnings and SECTION_SIZE definition overlap mm/hmm: fi

[PATCH akpm/next 0/4] Fix various issues in new hmm driver

ld tested for x86-64, arm64 and s390. Other 64 bit arch don't build and hence appear to be not applicable, as per details in patch 4/4. Cc: Jérôme Glisse Cc: Evgeny Baskakov Cc: John Hubbard Cc: Mark Hairgrove Cc: Sherry Cheung Cc: Subhash Gutti Cc: Andrew Morton --- Paul Gortmaker

Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.

[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote: > Hi Paul, > > On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote: > > Currently ia64 fails building allmodconfig

Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.

[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote: > Hi Paul, > > On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote: > > Currently ia64 fails building allmodconfig

Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.

[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote: > Hi Paul, > > On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote: > > Currently ia64 fails building allmodconfig

Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.

[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote: > Hi Paul, > > On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote: > > Currently ia64 fails building allmodconfig

Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.

On Mon, Jan 9, 2017 at 12:52 PM, Paul Gortmaker <paul.gortma...@windriver.com> wrote: > Currently ia64 fails building allmodconfig with variations of: > >In file included from drivers/nfc/nxp-nci/i2c.c:39:0: >./include/linux/unaligned/access_ok.h:62:29: e

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