Re: [Outreachy kernel] [PATCH v3 3/4] staging: sm750fb: Alignment should match open parenthesis

On Tue, 14 Mar 2017, Arushi Singhal wrote: > Fix checkpatch issues: "CHECK: Alignment should match open parenthesis". I thought you were going to take another approach to improve this code? julia > > Signed-off-by: Arushi Singhal > --- >

Re: [Outreachy kernel] [PATCH v3 3/4] staging: sm750fb: Alignment should match open parenthesis

On Tue, 14 Mar 2017, Arushi Singhal wrote: > Fix checkpatch issues: "CHECK: Alignment should match open parenthesis". I thought you were going to take another approach to improve this code? julia > > Signed-off-by: Arushi Singhal > --- > drivers/staging/sm750fb/ddk750_mode.c | 79 >

Re: [PATCH] Fixed a minor coding style warning. Arguments in the macros should be coverd in brackets to aviod any precedence issues.

On Mon, Mar 13, 2017 at 09:52:14PM -0700, mshan wrote: > Signed-off-by: mshan > --- > drivers/staging/fwserial/fwserial.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that

Re: [PATCH] Fixed a minor coding style warning. Arguments in the macros should be coverd in brackets to aviod any precedence issues.

On Mon, Mar 13, 2017 at 09:52:14PM -0700, mshan wrote: > Signed-off-by: mshan > --- > drivers/staging/fwserial/fwserial.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this

Re: [PATCH] MAINTAINERS: add Masahiro Yamada as a Kbuild maintainer

2017-03-10 10:41 GMT+09:00 Masahiro Yamada : > It has been difficult lately for Michal to work on Kbuild on his > regular basis. We discussed the maintainership of Kbuild, and I > decided to be a co-maintainer. > > Add myself to the maintainer field, and replace the

Re: [PATCH] MAINTAINERS: add Masahiro Yamada as a Kbuild maintainer

2017-03-10 10:41 GMT+09:00 Masahiro Yamada : > It has been difficult lately for Michal to work on Kbuild on his > regular basis. We discussed the maintainership of Kbuild, and I > decided to be a co-maintainer. > > Add myself to the maintainer field, and replace the repository with > my own. > >

[PATCH] ks7010: adding parenthesis to macro argument

Description: In driver module ks7010, "checkpatch.pl" flags error for adding parenthesis around macro params. Also, removing extra line. Signed-off-by: Pushkar Jambhlekar --- drivers/staging/ks7010/ks7010_sdio.c | 13 ++--- 1 file changed, 6 insertions(+), 7

[PATCH] ks7010: adding parenthesis to macro argument

Description: In driver module ks7010, "checkpatch.pl" flags error for adding parenthesis around macro params. Also, removing extra line. Signed-off-by: Pushkar Jambhlekar --- drivers/staging/ks7010/ks7010_sdio.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git

Re: [PATCH v5 2/4] dt-bindings: mfd: Add LED subnode binding for MT6323 PMIC

On Mon, 2017-03-13 at 13:00 +0100, Matthias Brugger wrote: > > On 03/03/17 14:56, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > This patch adds documentation for devicetree bindings > > for LED support as the subnode of MT6323 PMIC > > > > Signed-off-by: Sean

Re: [PATCH v5 2/4] dt-bindings: mfd: Add LED subnode binding for MT6323 PMIC

On Mon, 2017-03-13 at 13:00 +0100, Matthias Brugger wrote: > > On 03/03/17 14:56, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > This patch adds documentation for devicetree bindings > > for LED support as the subnode of MT6323 PMIC > > > > Signed-off-by: Sean Wang > > --- > >

Re: [PATCH v9 00/11] uapi: export all headers under uapi directories

Ni Nicolas, 2017-03-14 1:57 GMT+09:00 Nicolas Dichtel : >> BTW, this series does not apply cleanly. >> >> If you could rebase it onto v4.11-rc1 tag, >> it would be helpful. > You really want this on top of 4.11-rc1 or the last linus tag, ie v4.11-rc2? > Basically, I

Re: [PATCH v9 00/11] uapi: export all headers under uapi directories

Ni Nicolas, 2017-03-14 1:57 GMT+09:00 Nicolas Dichtel : >> BTW, this series does not apply cleanly. >> >> If you could rebase it onto v4.11-rc1 tag, >> it would be helpful. > You really want this on top of 4.11-rc1 or the last linus tag, ie v4.11-rc2? > Basically, I queue up patches based on

Re: [PATCH V7 4/7] LPC: Support the device-tree LPC host on Hip06/Hip07 (fwd)

Line 460 looks suspicious. Can tmprange be different than range but not be an ERR_PTR? If so, lpcdev->io_host will have an invalid value. julia -- Forwarded message -- Date: Tue, 14 Mar 2017 13:12:05 +0800 From: kbuild test robot To: kbu...@01.org Cc:

Re: [PATCH V7 4/7] LPC: Support the device-tree LPC host on Hip06/Hip07 (fwd)

Line 460 looks suspicious. Can tmprange be different than range but not be an ERR_PTR? If so, lpcdev->io_host will have an invalid value. julia -- Forwarded message -- Date: Tue, 14 Mar 2017 13:12:05 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia Lawall Subject:

[PATCH] drm/msm/hdmi: redefinitions of macros not required

4 macros already defined in hdmi.h, which is not required to redefine in hdmi_audio.c Signed-off-by: Vinay Simha BN --- drivers/gpu/drm/msm/hdmi/hdmi_audio.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/drivers/gpu/drm/msm/hdmi/hdmi_audio.c

[PATCH] drm/msm/hdmi: redefinitions of macros not required

4 macros already defined in hdmi.h, which is not required to redefine in hdmi_audio.c Signed-off-by: Vinay Simha BN --- drivers/gpu/drm/msm/hdmi/hdmi_audio.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/drivers/gpu/drm/msm/hdmi/hdmi_audio.c b/drivers/gpu/drm/msm/hdmi/hdmi_audio.c

Re: [PATCH V7 7/7] LPC: Add the ACPI LPC support

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V7 7/7] LPC: Add the ACPI LPC support

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] Kbuild: support designated_init attribute

Hi Kees, 2017-02-02 8:04 GMT+09:00 Kees Cook : > If a structure is marked with __attribute__((designated_init)) from > GCC or Sparse, it needs to have all static initializers using designated > initialization. Fail the build for any missing cases. This attribute will > be

Re: [PATCH] Kbuild: support designated_init attribute

Hi Kees, 2017-02-02 8:04 GMT+09:00 Kees Cook : > If a structure is marked with __attribute__((designated_init)) from > GCC or Sparse, it needs to have all static initializers using designated > initialization. Fail the build for any missing cases. This attribute will > be used by the randstruct

[PATCH] cpufreq: dbx500: Manage cooling device from cpufreq driver

The best place to register the CPU cooling device is from the cpufreq driver as we would know if all the resources are already available or not. That's what is done for the cpufreq-dt.c driver as well. The cpu-cooling driver for dbx500 platform was just (un)registering with the thermal framework

[PATCH] cpufreq: dbx500: Manage cooling device from cpufreq driver

The best place to register the CPU cooling device is from the cpufreq driver as we would know if all the resources are already available or not. That's what is done for the cpufreq-dt.c driver as well. The cpu-cooling driver for dbx500 platform was just (un)registering with the thermal framework

[PATCH v3 2/2] staging: speakup: fix "Alignment match open parenthesis"

Alig arguments with open parenthesis. Signed-off-by: Arushi Singhal --- changes in v3 - Improve the commit message. drivers/staging/speakup/kobjects.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/speakup/kobjects.c

[PATCH v3 2/2] staging: speakup: fix "Alignment match open parenthesis"

Alig arguments with open parenthesis. Signed-off-by: Arushi Singhal --- changes in v3 - Improve the commit message. drivers/staging/speakup/kobjects.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/speakup/kobjects.c b/drivers/staging/speakup/kobjects.c

[PATCH v3 1/2] staging: speakup: Add blank line after declarations

Patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Add a blank line after enum and struct declarations. Signed-off-by: Arushi Singhal --- changes in v3 - change the subject and commit

[PATCH v3 1/2] staging: speakup: Add blank line after declarations

Patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Add a blank line after enum and struct declarations. Signed-off-by: Arushi Singhal --- changes in v3 - change the subject and commit message to make it more relevant.

[PATCH v3 0/2] staging: speakup: checkpatch guided cleanups.

Improve readability by fixing multiple checkpatch.pl issues in speakup driver. Arushi Singhal (2): staging: speakup: Add blank line after declarations staging: speakup: fix "Alignment match open parenthesis" drivers/staging/speakup/kobjects.c | 2 +- drivers/staging/speakup/main.c

[PATCH v3 0/2] staging: speakup: checkpatch guided cleanups.

Improve readability by fixing multiple checkpatch.pl issues in speakup driver. Arushi Singhal (2): staging: speakup: Add blank line after declarations staging: speakup: fix "Alignment match open parenthesis" drivers/staging/speakup/kobjects.c | 2 +- drivers/staging/speakup/main.c

Re: [PATCH V7 5/7] ACPI: Delay the enumeration on the devices whose dependency has not met

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V7 5/7] ACPI: Delay the enumeration on the devices whose dependency has not met

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V7 6/7] LIBIO: Support the dynamically logical PIO registration of ACPI host I/O

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V7 6/7] LIBIO: Support the dynamically logical PIO registration of ACPI host I/O

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: Synaptics RMI4 touchpad regression in 4.11-rc1

On 03/13/2017 06:35 PM, Andrew Duggan wrote: > > > On 03/13/2017 06:15 AM, Benjamin Tissoires wrote: >> [Resending, forgot to add Jiri in CC] >> >> On Mar 13 2017 or thereabouts, Benjamin Tissoires wrote: >>> On Mar 13 2017 or thereabouts, Thorsten Leemhuis wrote: Lo! On 12.03.2017 02:55,

Re: Synaptics RMI4 touchpad regression in 4.11-rc1

On 03/13/2017 06:35 PM, Andrew Duggan wrote: > > > On 03/13/2017 06:15 AM, Benjamin Tissoires wrote: >> [Resending, forgot to add Jiri in CC] >> >> On Mar 13 2017 or thereabouts, Benjamin Tissoires wrote: >>> On Mar 13 2017 or thereabouts, Thorsten Leemhuis wrote: Lo! On 12.03.2017 02:55,

Re: [PATCH net, v2] dccp/tcp: fix routing redirect race

From: Jon Maxwell Date: Fri, 10 Mar 2017 16:40:33 +1100 > As Eric Dumazet pointed out this also needs to be fixed in IPv6. > v2: Contains the IPv6 tcp/Ipv6 dccp patches as well. > > We have seen a few incidents lately where a dst_enty has been freed > with a dangling TCP

Re: [PATCH net, v2] dccp/tcp: fix routing redirect race

From: Jon Maxwell Date: Fri, 10 Mar 2017 16:40:33 +1100 > As Eric Dumazet pointed out this also needs to be fixed in IPv6. > v2: Contains the IPv6 tcp/Ipv6 dccp patches as well. > > We have seen a few incidents lately where a dst_enty has been freed > with a dangling TCP socket reference

Re: [PATCH net-next 00/12] net: bcmgenet: add support for GENETv5

From: Doug Berger Date: Mon, 13 Mar 2017 17:41:30 -0700 > This collection of patches contains changes related to adding > support for the BCM7260, BCM7268, and BCM7271 devices that > contain a new version of the GENET MAC IP block (v5) and a new > fast ethernet (10/100BASE-T)

Re: [PATCH net-next 00/12] net: bcmgenet: add support for GENETv5

From: Doug Berger Date: Mon, 13 Mar 2017 17:41:30 -0700 > This collection of patches contains changes related to adding > support for the BCM7260, BCM7268, and BCM7271 devices that > contain a new version of the GENET MAC IP block (v5) and a new > fast ethernet (10/100BASE-T) internal PHY. > >

[PATCH] Fixed a minor coding style warning. Arguments in the macros should be coverd in brackets to aviod any precedence issues.

Signed-off-by: mshan --- drivers/staging/fwserial/fwserial.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/fwserial/fwserial.c b/drivers/staging/fwserial/fwserial.c index 41a49c8..d693c03 100644 ---

[PATCH] Fixed a minor coding style warning. Arguments in the macros should be coverd in brackets to aviod any precedence issues.

Signed-off-by: mshan --- drivers/staging/fwserial/fwserial.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/fwserial/fwserial.c b/drivers/staging/fwserial/fwserial.c index 41a49c8..d693c03 100644 --- a/drivers/staging/fwserial/fwserial.c +++

Re: [PATCH] dma-engine: Fix array index out of bounds warning in __get_unmap_pool()

On Mon, Mar 13, 2017 at 02:30:29PM -0700, Matthias Kaehlcke wrote: > This fixes the following warning when building with clang and > CONFIG_DMA_ENGINE_RAID=n : > > drivers/dma/dmaengine.c:1102:11: error: array index 2 is past the end of the > array (which contains 1 element)

Re: [PATCH] dma-engine: Fix array index out of bounds warning in __get_unmap_pool()

On Mon, Mar 13, 2017 at 02:30:29PM -0700, Matthias Kaehlcke wrote: > This fixes the following warning when building with clang and > CONFIG_DMA_ENGINE_RAID=n : > > drivers/dma/dmaengine.c:1102:11: error: array index 2 is past the end of the > array (which contains 1 element)

Re: Applied "ASoC: sun8i-codec: Update mixer to use SOC_DAPM_DOUBLE" to the asoc tree

Hi Mark, On Wed, Mar 8, 2017 at 9:22 PM, Mark Brown wrote: > The patch > >ASoC: sun8i-codec: Update mixer to use SOC_DAPM_DOUBLE > > has been applied to the asoc tree at > >git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git > > All being well this means

Re: Applied "ASoC: sun8i-codec: Update mixer to use SOC_DAPM_DOUBLE" to the asoc tree

Hi Mark, On Wed, Mar 8, 2017 at 9:22 PM, Mark Brown wrote: > The patch > >ASoC: sun8i-codec: Update mixer to use SOC_DAPM_DOUBLE > > has been applied to the asoc tree at > >git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git > > All being well this means that it will be

Re: [PATCH V7 6/7] LIBIO: Support the dynamically logical PIO registration of ACPI host I/O

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V7 6/7] LIBIO: Support the dynamically logical PIO registration of ACPI host I/O

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] x86/unwind: Fix last frame check for aligned function stacks

Pavel Machek reported the following warning on x86-32: WARNING: kernel stack frame pointer at f50cdf98 in swapper/2:0 has bad value (null) The warning is caused by the unwinder not realizing that it reached the end of the stack, due to an unusual prologue which gcc sometimes generates for

[PATCH] x86/unwind: Fix last frame check for aligned function stacks

Pavel Machek reported the following warning on x86-32: WARNING: kernel stack frame pointer at f50cdf98 in swapper/2:0 has bad value (null) The warning is caused by the unwinder not realizing that it reached the end of the stack, due to an unusual prologue which gcc sometimes generates for

Re: [PATCH v2 06/12] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk

On Sun, Mar 05, 2017 at 09:37:03PM +0800, Icenowy Zheng wrote: > Originally we enable a special gate bit when the compatible indicates > A23/33. > > But according to BSP sources and user manuals, more SoCs will need this > gate bit. > > So make it a common quirk configured in the config struct.

Re: [PATCH v2 06/12] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk

On Sun, Mar 05, 2017 at 09:37:03PM +0800, Icenowy Zheng wrote: > Originally we enable a special gate bit when the compatible indicates > A23/33. > > But according to BSP sources and user manuals, more SoCs will need this > gate bit. > > So make it a common quirk configured in the config struct.

Re: [PATCH] x86/mm: trivial code cleanup for memory_map_top_doown()

On Mon, Mar 13, 2017 at 07:50:21PM +0100, Borislav Petkov wrote: >On Fri, Feb 17, 2017 at 10:30:33PM +0800, Wei Yang wrote: >> In case (last_start <= step_size), start is for sure to be 0. So, it is > Hmm, I may write it more specific: "start" is for sure to be set to 0 with

Re: [PATCH] x86/mm: trivial code cleanup for memory_map_top_doown()

On Mon, Mar 13, 2017 at 07:50:21PM +0100, Borislav Petkov wrote: >On Fri, Feb 17, 2017 at 10:30:33PM +0800, Wei Yang wrote: >> In case (last_start <= step_size), start is for sure to be 0. So, it is > Hmm, I may write it more specific: "start" is for sure to be set to 0 with

Re: [PATCH] fscrypt: remove broken support for detecting keyring key revocation

On Tue, Feb 21, 2017 at 03:07:11PM -0800, Eric Biggers wrote: > From: Eric Biggers > > Filesystem encryption ostensibly supported revoking a keyring key > that had been used to "unlock" encrypted files, causing those files > to become "locked" again. This was, however, buggy

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

Hi Sakari, I started preparing a long argument about it, but gave up in favor of a simpler one. Em Mon, 13 Mar 2017 14:46:22 +0200 Sakari Ailus escreveu: > Drivers are written to support hardware, not particular use case. No, it is just the reverse: drivers and hardware

Re: [PATCH] fscrypt: remove broken support for detecting keyring key revocation

On Tue, Feb 21, 2017 at 03:07:11PM -0800, Eric Biggers wrote: > From: Eric Biggers > > Filesystem encryption ostensibly supported revoking a keyring key > that had been used to "unlock" encrypted files, causing those files > to become "locked" again. This was, however, buggy for several >

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

Hi Sakari, I started preparing a long argument about it, but gave up in favor of a simpler one. Em Mon, 13 Mar 2017 14:46:22 +0200 Sakari Ailus escreveu: > Drivers are written to support hardware, not particular use case. No, it is just the reverse: drivers and hardware are developed to

Re: [PATCH v2 2/2] dma: xilinx: Add reset support

On Mon, Mar 06, 2017 at 12:17:39PM +, Ramiro Oliveira wrote: > Add a DT property to control an optional external reset line > > Signed-off-by: Ramiro Oliveira > --- > drivers/dma/xilinx/xilinx_dma.c | 24 > 1 file changed, 20 insertions(+), 4

Re: [PATCH v2 2/2] dma: xilinx: Add reset support

On Mon, Mar 06, 2017 at 12:17:39PM +, Ramiro Oliveira wrote: > Add a DT property to control an optional external reset line > > Signed-off-by: Ramiro Oliveira > --- > drivers/dma/xilinx/xilinx_dma.c | 24 > 1 file changed, 20 insertions(+), 4 deletions(-) > > diff

[PATCH v8 3/4] irqchip/qeic: merge qeic_of_init into qe_ic_init

qeic_of_init just get device_node of qeic from dtb and call qe_ic_init, pass the device_node to qe_ic_init. So merge qeic_of_init into qe_ic_init to get the qeic node in qe_ic_init. Signed-off-by: Zhao Qiang --- drivers/irqchip/irq-qeic.c | 82

[PATCH v8 4/4] irqchip/qeic: remove PPCisms for QEIC

QEIC was supported on PowerPC, and dependent on PPC, Now it is supported on other platforms, so remove PPCisms. Signed-off-by: Zhao Qiang --- arch/powerpc/platforms/83xx/km83xx.c | 1 - arch/powerpc/platforms/83xx/misc.c| 1 -

[PATCH v8 3/4] irqchip/qeic: merge qeic_of_init into qe_ic_init

qeic_of_init just get device_node of qeic from dtb and call qe_ic_init, pass the device_node to qe_ic_init. So merge qeic_of_init into qe_ic_init to get the qeic node in qe_ic_init. Signed-off-by: Zhao Qiang --- drivers/irqchip/irq-qeic.c | 82 ++

[PATCH v8 4/4] irqchip/qeic: remove PPCisms for QEIC

QEIC was supported on PowerPC, and dependent on PPC, Now it is supported on other platforms, so remove PPCisms. Signed-off-by: Zhao Qiang --- arch/powerpc/platforms/83xx/km83xx.c | 1 - arch/powerpc/platforms/83xx/misc.c| 1 - arch/powerpc/platforms/83xx/mpc832x_mds.c

[PATCH v8 1/4] irqchip/qeic: move qeic driver from drivers/soc/fsl/qe

move the driver from drivers/soc/fsl/qe to drivers/irqchip, merge qe_ic.h and qe_ic.c into irq-qeic.c. Signed-off-by: Zhao Qiang --- MAINTAINERS| 6 ++ drivers/irqchip/Makefile | 1 +

[PATCH v8 1/4] irqchip/qeic: move qeic driver from drivers/soc/fsl/qe

move the driver from drivers/soc/fsl/qe to drivers/irqchip, merge qe_ic.h and qe_ic.c into irq-qeic.c. Signed-off-by: Zhao Qiang --- MAINTAINERS| 6 ++ drivers/irqchip/Makefile | 1 + drivers/{soc/fsl/qe/qe_ic.c =>

[PATCH v8 0/4] this patchset is to remove PPCisms for QEIC

QEIC is supported more than just powerpc boards, so remove PPCisms. changelog: Changes for v8: - use IRQCHIP_DECLARE() instead of subsys_initcall in qeic driver - remove include/soc/fsl/qe/qe_ic.h Zhao Qiang (4): irqchip/qeic: move qeic driver from drivers/soc/fsl/qe

[PATCH v8 2/4] irqchip/qeic: merge qeic init code from platforms to a common function

The codes of qe_ic init from a variety of platforms are redundant, merge them to a common function and put it to irqchip/irq-qeic.c For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0, qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of "qe_ic_init(np, 0,

[PATCH v8 2/4] irqchip/qeic: merge qeic init code from platforms to a common function

The codes of qe_ic init from a variety of platforms are redundant, merge them to a common function and put it to irqchip/irq-qeic.c For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0, qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of "qe_ic_init(np, 0,

[PATCH v8 0/4] this patchset is to remove PPCisms for QEIC

QEIC is supported more than just powerpc boards, so remove PPCisms. changelog: Changes for v8: - use IRQCHIP_DECLARE() instead of subsys_initcall in qeic driver - remove include/soc/fsl/qe/qe_ic.h Zhao Qiang (4): irqchip/qeic: move qeic driver from drivers/soc/fsl/qe

[Patch V2 1/2] x86/mm/numa: trivial fix on typo and error message

When allocating pg_data in alloc_node_data(), it will try to allocate from local node first and then from any node. If it fails at the second trial, it means there is not available memory on any node. This patch fixes the error message and correct one typo. Signed-off-by: Wei Yang

Re: [PATCH] kernfs: Check KERNFS_HAS_RELEASE before calling kernfs_release_file()

On Tue, Mar 14, 2017 at 08:17:00AM +0530, Vaibhav Jain wrote: > Recently started seeing a kernel oops when a module tries removing a > memory mapped sysfs bin_attribute. On closer investigation the root > cause seems to be kernfs_release_file() trying to call > kernfs_op.release() callback that's

[Patch V2 1/2] x86/mm/numa: trivial fix on typo and error message

When allocating pg_data in alloc_node_data(), it will try to allocate from local node first and then from any node. If it fails at the second trial, it means there is not available memory on any node. This patch fixes the error message and correct one typo. Signed-off-by: Wei Yang --- v2: *

Re: [PATCH] kernfs: Check KERNFS_HAS_RELEASE before calling kernfs_release_file()

On Tue, Mar 14, 2017 at 08:17:00AM +0530, Vaibhav Jain wrote: > Recently started seeing a kernel oops when a module tries removing a > memory mapped sysfs bin_attribute. On closer investigation the root > cause seems to be kernfs_release_file() trying to call > kernfs_op.release() callback that's

[Patch V2 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo()

numa_nodemask_from_meminfo() is called to set bit according to numa_meminfo. While the only two places for this call is used to set proper bit to a copy of numa_nodes_parsed from numa_meminfo. With current code path, those numa node information in numa_meminfo is a subset of numa_nodes_parsed. So

[Patch V2 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo()

numa_nodemask_from_meminfo() is called to set bit according to numa_meminfo. While the only two places for this call is used to set proper bit to a copy of numa_nodes_parsed from numa_meminfo. With current code path, those numa node information in numa_meminfo is a subset of numa_nodes_parsed. So

Re: [PATCH] PM / QOS: Remove the global notifiers

On 13-03-17, 14:32, Kevin Hilman wrote: > Ulf Hansson writes: > > > On 13 March 2017 at 17:01, Ulf Hansson wrote: > >> On 22 February 2017 at 09:28, Viresh Kumar wrote: > >>> They were never used in the kernel, not sure

Re: [PATCH] lockdep: call time_hardirqs_off after clearing hardirqs_enabled

On Tue, 14 Mar 2017 10:00:07 +0800 Qi Hou wrote: > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c > index 577f026..e8b35e4 100644 > --- a/kernel/locking/lockdep.c > +++ b/kernel/locking/lockdep.c > @@ -2627,8 +2627,6 @@ __visible void

Re: [PATCH v2] mm: fix condition for throttle_direct_reclaim

On March 14, 2017 6:19 AM Shakeel Butt wrote: > > Recently kswapd has been modified to give up after MAX_RECLAIM_RETRIES > number of unsucessful iterations. Before going to sleep, kswapd thread > will unconditionally wakeup all threads sleeping on pfmemalloc_wait. > However the awoken threads

Re: [PATCH] PM / QOS: Remove the global notifiers

On 13-03-17, 14:32, Kevin Hilman wrote: > Ulf Hansson writes: > > > On 13 March 2017 at 17:01, Ulf Hansson wrote: > >> On 22 February 2017 at 09:28, Viresh Kumar wrote: > >>> They were never used in the kernel, not sure why they got merged into > >>> the kernel though. Get rid of them. > >> >

Re: [PATCH] lockdep: call time_hardirqs_off after clearing hardirqs_enabled

On Tue, 14 Mar 2017 10:00:07 +0800 Qi Hou wrote: > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c > index 577f026..e8b35e4 100644 > --- a/kernel/locking/lockdep.c > +++ b/kernel/locking/lockdep.c > @@ -2627,8 +2627,6 @@ __visible void trace_hardirqs_off_caller(unsigned long >

Re: [PATCH v2] mm: fix condition for throttle_direct_reclaim

On March 14, 2017 6:19 AM Shakeel Butt wrote: > > Recently kswapd has been modified to give up after MAX_RECLAIM_RETRIES > number of unsucessful iterations. Before going to sleep, kswapd thread > will unconditionally wakeup all threads sleeping on pfmemalloc_wait. > However the awoken threads

Re: [PATCH 4.10 00/75] 4.10.3-stable review

On Mon, Mar 13, 2017 at 07:11:12AM -0700, kernelci.org bot wrote: > stable-rc boot: 530 boots: 5 failed, 516 passed with 9 offline > (v4.10.2-76-g43100e143367) These are ok, right? And 4.9 seems to not be doing many boots, is the build farm just busy? thanks, greg k-h

Re: [PATCH 4.10 00/75] 4.10.3-stable review

On Mon, Mar 13, 2017 at 07:11:12AM -0700, kernelci.org bot wrote: > stable-rc boot: 530 boots: 5 failed, 516 passed with 9 offline > (v4.10.2-76-g43100e143367) These are ok, right? And 4.9 seems to not be doing many boots, is the build farm just busy? thanks, greg k-h

Re: [PATCH] lockdep: call time_hardirqs_off after clearing hardirqs_enabled

Please stop sending "guesswork" patches. This message to you is not new. I am running out of avenues where I can ask you to cease and desist; spamming maintainers like this is not acceptable. You are one step away from being in a kill-file. On Mon, Mar 13, 2017 at 10:00 PM, Qi Hou

Re: [PATCH] lockdep: call time_hardirqs_off after clearing hardirqs_enabled

Please stop sending "guesswork" patches. This message to you is not new. I am running out of avenues where I can ask you to cease and desist; spamming maintainers like this is not acceptable. You are one step away from being in a kill-file. On Mon, Mar 13, 2017 at 10:00 PM, Qi Hou wrote: >

Re: [PATCH 4.10 00/75] 4.10.3-stable review

On Mon, Mar 13, 2017 at 03:38:11PM -0700, Guenter Roeck wrote: > On Mon, Mar 13, 2017 at 04:43:09PM +0800, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.10.3 release. > > There are 75 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.10 00/75] 4.10.3-stable review

On Mon, Mar 13, 2017 at 03:38:11PM -0700, Guenter Roeck wrote: > On Mon, Mar 13, 2017 at 04:43:09PM +0800, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.10.3 release. > > There are 75 patches in this series, all will be posted as a response > > to this one.

Re: [scsi] scsi: ufs: don't check unsigned type for a negative value

> "Tomas" == Tomas Winkler writes: Tomas> Fix compilation warning drivers/scsi/ufs/ufshcd.c:7645:13: Tomas> warning: comparison of unsigned expression < 0 is always false Tomas> [-Wtype-limits] if ((value < UFS_PM_LVL_0) || (value >= Tomas> UFS_PM_LVL_MAX)) Applied

Re: [scsi] scsi: ufs: don't check unsigned type for a negative value

> "Tomas" == Tomas Winkler writes: Tomas> Fix compilation warning drivers/scsi/ufs/ufshcd.c:7645:13: Tomas> warning: comparison of unsigned expression < 0 is always false Tomas> [-Wtype-limits] if ((value < UFS_PM_LVL_0) || (value >= Tomas> UFS_PM_LVL_MAX)) Applied to 4.11/scsi-fixes,

Re: [PATCH v1 2/2] dmaengine: Add DW AXI DMAC driver

On Tue, Feb 21, 2017 at 11:38:04PM +0300, Eugeniy Paltsev wrote: > +static struct axi_dma_desc *axi_desc_get(struct axi_dma_chan *chan) > +{ > + struct dw_axi_dma *dw = chan->chip->dw; > + struct axi_dma_desc *desc; > + dma_addr_t phys; > + > + desc =

Re: [PATCH v1 2/2] dmaengine: Add DW AXI DMAC driver

On Tue, Feb 21, 2017 at 11:38:04PM +0300, Eugeniy Paltsev wrote: > +static struct axi_dma_desc *axi_desc_get(struct axi_dma_chan *chan) > +{ > + struct dw_axi_dma *dw = chan->chip->dw; > + struct axi_dma_desc *desc; > + dma_addr_t phys; > + > + desc =

Re: Compat 32-bit syscall entry from 64-bit task!?

On Wed, Mar 08, 2017 at 08:39:55PM -0800, Andrew Lutomirski wrote: > On Wed, Mar 8, 2017 at 3:41 PM, Dmitry V. Levin wrote: [...] > > Is there any progress with this (or any alternative) solution? > > > > I see the kernel side has changed a bit, and the strace part > > is in a better shape than 5

Re: Compat 32-bit syscall entry from 64-bit task!?

On Wed, Mar 08, 2017 at 08:39:55PM -0800, Andrew Lutomirski wrote: > On Wed, Mar 8, 2017 at 3:41 PM, Dmitry V. Levin wrote: [...] > > Is there any progress with this (or any alternative) solution? > > > > I see the kernel side has changed a bit, and the strace part > > is in a better shape than 5

fsx tests on DAX started to fail with msync failure on 0307 -next tree

Hi, xfstests cases: generic/075 generic/112 generic/127 generic/231 generic/263 fail with DAX, pass without it. Both xfs and ext4. It was okay on 0306 -next tree. + ./check generic/075 FSTYP -- xfs (non-debug) PLATFORM -- Linux/x86_64 hp-dl360g9-12

fsx tests on DAX started to fail with msync failure on 0307 -next tree

Hi, xfstests cases: generic/075 generic/112 generic/127 generic/231 generic/263 fail with DAX, pass without it. Both xfs and ext4. It was okay on 0306 -next tree. + ./check generic/075 FSTYP -- xfs (non-debug) PLATFORM -- Linux/x86_64 hp-dl360g9-12

Re: [RFC PATCH kernel] gcc-goto.sh: Allow to pass with CONFIG_DEBUG_INFO_SPLIT=y

On 03/03/17 11:51, Alexey Kardashevskiy wrote: > With just CONFIG_DEBUG_INFO=y, the makefile adds "-g" to > KBUILD_CFLAGS/KBUILD_AFLAGS and the test passes. > > However, if CONFIG_DEBUG_INFO_SPLIT is also enabled, the makefile > adds "-gsplit-dwarf" instead which makes the test fail with $?==1 >

Re: [RFC PATCH kernel] gcc-goto.sh: Allow to pass with CONFIG_DEBUG_INFO_SPLIT=y

On 03/03/17 11:51, Alexey Kardashevskiy wrote: > With just CONFIG_DEBUG_INFO=y, the makefile adds "-g" to > KBUILD_CFLAGS/KBUILD_AFLAGS and the test passes. > > However, if CONFIG_DEBUG_INFO_SPLIT is also enabled, the makefile > adds "-gsplit-dwarf" instead which makes the test fail with $?==1 >

Re: [PATCH 1/2] x86/mm/numa: trivial fix on typo and error message

On Mon, Mar 13, 2017 at 02:00:10PM +0100, Borislav Petkov wrote: >On Mon, Feb 06, 2017 at 11:35:28PM +0800, Wei Yang wrote: >> When allocating pg_data in alloc_node_data(), it will try to allocate from >> local node first and then from any node. If it fails at the second trial, >> it means there

Re: [PATCH 1/2] x86/mm/numa: trivial fix on typo and error message

On Mon, Mar 13, 2017 at 02:00:10PM +0100, Borislav Petkov wrote: >On Mon, Feb 06, 2017 at 11:35:28PM +0800, Wei Yang wrote: >> When allocating pg_data in alloc_node_data(), it will try to allocate from >> local node first and then from any node. If it fails at the second trial, >> it means there

Re: [PATCH 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo()

On Mon, Mar 13, 2017 at 02:30:46PM +0100, Borislav Petkov wrote: >On Mon, Feb 06, 2017 at 11:35:29PM +0800, Wei Yang wrote: >> numa_nodemask_from_meminfo() is called to set bit according to >> numa_meminfo. While the only two places for this call is used to set proper >> bit to a copy of

Re: [PATCH 2/2] x86/mm/numa: remove the numa_nodemask_from_meminfo()

On Mon, Mar 13, 2017 at 02:30:46PM +0100, Borislav Petkov wrote: >On Mon, Feb 06, 2017 at 11:35:29PM +0800, Wei Yang wrote: >> numa_nodemask_from_meminfo() is called to set bit according to >> numa_meminfo. While the only two places for this call is used to set proper >> bit to a copy of

  1   2   3   4   5   6   7   8   9   10   >