Re: [PATCH V6 2/5] PCI/ACPI: Check platform specific ECAM quirks

On 13.09.2016 00:47, Duc Dang wrote: On Mon, Sep 12, 2016 at 3:24 PM, Duc Dang wrote: On Fri, Sep 9, 2016 at 12:24 PM, Tomasz Nowicki wrote: Some platforms may not be fully compliant with generic set of PCI config accessors. For these cases we implement

Re: [PATCH V6 2/5] PCI/ACPI: Check platform specific ECAM quirks

On 13.09.2016 00:47, Duc Dang wrote: On Mon, Sep 12, 2016 at 3:24 PM, Duc Dang wrote: On Fri, Sep 9, 2016 at 12:24 PM, Tomasz Nowicki wrote: Some platforms may not be fully compliant with generic set of PCI config accessors. For these cases we implement the way to overwrite CFG accessors

[PATCH V2] checkpatch: Add --strict test for precedence challenged macro arguments

Add a test for macro arguents that have a non-comma leading or trailing operator where the argument isn't parenthesized to avoid possible precedence issues. Signed-off-by: Joe Perches --- V2: Fix silly comment typo scripts/checkpatch.pl | 9 - 1 file changed, 8

[PATCH V2] checkpatch: Add --strict test for precedence challenged macro arguments

Add a test for macro arguents that have a non-comma leading or trailing operator where the argument isn't parenthesized to avoid possible precedence issues. Signed-off-by: Joe Perches --- V2: Fix silly comment typo scripts/checkpatch.pl | 9 - 1 file changed, 8 insertions(+), 1

Re: [PATCH] usb: cleanup with list_first_entry_or_null()

Hi Masahiro, Masahiro Yamada writes: > The combo of list_empty() check and return list_first_entry() > can be replaced with list_first_entry_or_null(). > > Signed-off-by: Masahiro Yamada > --- Care to split this into two patches

Re: [PATCH] usb: cleanup with list_first_entry_or_null()

Hi Masahiro, Masahiro Yamada writes: > The combo of list_empty() check and return list_first_entry() > can be replaced with list_first_entry_or_null(). > > Signed-off-by: Masahiro Yamada > --- Care to split this into two patches (one for dwc2 and one for dwc3)? thanks -- balbi

Re: [PATCH 2/2] usb: dwc3: Added a property to set GFLADJ register

Hi, Rob Herring writes: >> Synopsys HW setup (HAPS DX and phy board) requires a preset to this >> register to improve interoperablitity. For example, the value for >> GFLADJ_REFCLK_LPM_SEL should be set to 0 with ref_clk period of 50. > > This sounds like it should be handled

Re: [PATCH 2/2] usb: dwc3: Added a property to set GFLADJ register

Hi, Rob Herring writes: >> Synopsys HW setup (HAPS DX and phy board) requires a preset to this >> register to improve interoperablitity. For example, the value for >> GFLADJ_REFCLK_LPM_SEL should be set to 0 with ref_clk period of 50. > > This sounds like it should be handled in the driver. Is

[PATCH 0/2] checkpatch: Add --strict macro argument tests

This is rather better than the first submission. I think this is acceptable and doesn't need to be RFC. Joe Perches (2): checkpatch: Add --strict test for macro argument reuse checkpatch: Add --strict test for precedence challenged macro arguments scripts/checkpatch.pl | 50

[PATCH 1/2] checkpatch: Add --strict test for macro argument reuse

If a macro argument is used multiple times in the macro definition, the macro argument may have an unexpected side-effect. Add a test (MACRO_ARG_REUSE) for that condition which is only emitted with command-line option --strict. Signed-off-by: Joe Perches ---

[PATCH 2/2] checkpatch: Add --strict test for precedence challenged macro arguments

Add a test for macro arguents that have a non-comma leading or trailing operator where the argument isn't parenthesized to avoid possible precedence issues. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff

[PATCH 0/2] checkpatch: Add --strict macro argument tests

This is rather better than the first submission. I think this is acceptable and doesn't need to be RFC. Joe Perches (2): checkpatch: Add --strict test for macro argument reuse checkpatch: Add --strict test for precedence challenged macro arguments scripts/checkpatch.pl | 50

[PATCH 1/2] checkpatch: Add --strict test for macro argument reuse

If a macro argument is used multiple times in the macro definition, the macro argument may have an unexpected side-effect. Add a test (MACRO_ARG_REUSE) for that condition which is only emitted with command-line option --strict. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 43

[PATCH 2/2] checkpatch: Add --strict test for precedence challenged macro arguments

Add a test for macro arguents that have a non-comma leading or trailing operator where the argument isn't parenthesized to avoid possible precedence issues. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git

Re: [RFC PATCH 2/3] tracing/syscalls: add handling for compat tasks

Hi Andy, Thanks for your review and the comments, I'll address them in a next iteration. Do you have any other comments on the complete patchset? On 12.09.2016 19:35, Andy Lutomirski wrote: On Sep 9, 2016 1:04 AM, "Marcin Nowakowski" wrote: Extend the syscall

Re: [RFC PATCH 2/3] tracing/syscalls: add handling for compat tasks

Hi Andy, Thanks for your review and the comments, I'll address them in a next iteration. Do you have any other comments on the complete patchset? On 12.09.2016 19:35, Andy Lutomirski wrote: On Sep 9, 2016 1:04 AM, "Marcin Nowakowski" wrote: Extend the syscall tracing subsystem by adding a

Re: DAX mapping detection (was: Re: [PATCH] Fix region lost in /proc/self/smaps)

On Mon, 12 Sep 2016 21:06:49 -0700 Dan Williams wrote: > On Mon, Sep 12, 2016 at 6:31 PM, Nicholas Piggin wrote: > > On Mon, 12 Sep 2016 08:01:48 -0700 > [..] > > That said, a noop system call is on the order of 100 cycles nowadays, > > so rushing

Re: DAX mapping detection (was: Re: [PATCH] Fix region lost in /proc/self/smaps)

On Mon, 12 Sep 2016 21:06:49 -0700 Dan Williams wrote: > On Mon, Sep 12, 2016 at 6:31 PM, Nicholas Piggin wrote: > > On Mon, 12 Sep 2016 08:01:48 -0700 > [..] > > That said, a noop system call is on the order of 100 cycles nowadays, > > so rushing to implement these APIs without seeing good

Re: Question about suspend/resume clock handling in dwc3-of-simple.c

Hi, Guenter Roeck writes: >> > Should it be clk_disable_unprepare(), or maybe something like the >> > following >> > >> >if (!pm_runtime_status_suspended(dev)) >> >clk_disable_unprepare(); >> >else >> >clk_unprepare(); >> >> I'm not sure how

Re: Question about suspend/resume clock handling in dwc3-of-simple.c

Hi, Guenter Roeck writes: >> > Should it be clk_disable_unprepare(), or maybe something like the >> > following >> > >> >if (!pm_runtime_status_suspended(dev)) >> >clk_disable_unprepare(); >> >else >> >clk_unprepare(); >> >> I'm not sure how balanced those calls

Re: [PATCH v7 9/9] drm/mediatek: add support for Mediatek SoC MT2701

Hi, YT: On Mon, 2016-09-12 at 18:16 +0800, YT Shen wrote: > Hi CK, > > On Wed, 2016-09-07 at 13:37 +0800, CK Hu wrote: > > Hi, YT: > > > > On Fri, 2016-09-02 at 19:24 +0800, YT Shen wrote: > > > This patch add support for the Mediatek MT2701 DISP subsystem. > > > There is only one OVL engine in

Re: [PATCH v7 9/9] drm/mediatek: add support for Mediatek SoC MT2701

Hi, YT: On Mon, 2016-09-12 at 18:16 +0800, YT Shen wrote: > Hi CK, > > On Wed, 2016-09-07 at 13:37 +0800, CK Hu wrote: > > Hi, YT: > > > > On Fri, 2016-09-02 at 19:24 +0800, YT Shen wrote: > > > This patch add support for the Mediatek MT2701 DISP subsystem. > > > There is only one OVL engine in

Re: [PATCH v15 1/5] extcon: Introduce EXTCON_PROP_DISP_HPD property

Dear all, On 2016년 09월 10일 11:15, Chris Zhong wrote: > EXTCON_PROP_DISP_HPD is need by display port, if the system has no hpd > interrupt, this property can be used. > > Signed-off-by: Chris Zhong > --- > > Changes in v15: None > Changes in v14: None > Changes in v13: None

Re: [PATCH v15 1/5] extcon: Introduce EXTCON_PROP_DISP_HPD property

Dear all, On 2016년 09월 10일 11:15, Chris Zhong wrote: > EXTCON_PROP_DISP_HPD is need by display port, if the system has no hpd > interrupt, this property can be used. > > Signed-off-by: Chris Zhong > --- > > Changes in v15: None > Changes in v14: None > Changes in v13: None > Changes in v12:

[PATCH v5 1/3] arm/dts: add pcie aer interrupt-name property in the dts

NXP arm aer interrupt was not MSI/MSI-X/INTx but using interrupt line independently. This patch add a "aer" interrupt-names for aer interrupt. With the interrupt-names "aer", code could probe aer interrupt line for pcie root port, replace the aer interrupt service irq. This patch is intend to

[PATCH v5 1/3] arm/dts: add pcie aer interrupt-name property in the dts

NXP arm aer interrupt was not MSI/MSI-X/INTx but using interrupt line independently. This patch add a "aer" interrupt-names for aer interrupt. With the interrupt-names "aer", code could probe aer interrupt line for pcie root port, replace the aer interrupt service irq. This patch is intend to

[PATCH v5 3/3] pci:aer: add support aer interrupt with none MSI/MSI-X/INTx mode

On some platforms, root port doesn't support MSI/MSI-X/INTx in RC mode. When chip support the aer interrupt with none MSI/MSI-X/INTx mode, maybe there is interrupt line for aer pme etc. Search the interrupt number in the fdt file. Then fixup the dev->irq with it. Signed-off-by: Po Liu

[PATCH v5 3/3] pci:aer: add support aer interrupt with none MSI/MSI-X/INTx mode

On some platforms, root port doesn't support MSI/MSI-X/INTx in RC mode. When chip support the aer interrupt with none MSI/MSI-X/INTx mode, maybe there is interrupt line for aer pme etc. Search the interrupt number in the fdt file. Then fixup the dev->irq with it. Signed-off-by: Po Liu ---

[PATCH v5 2/3] arm64/dts: add pcie aer interrupt-name property in the dts

Some platforms(NXP Layerscape for example) aer interrupt was not MSI/MSI-X/INTx but using interrupt line independently. This patch add a "aer" interrupt-names for aer interrupt. With the interrupt-names "aer", code could probe aer interrupt line for pcie root port, replace the aer interrupt

[PATCH v5 2/3] arm64/dts: add pcie aer interrupt-name property in the dts

Some platforms(NXP Layerscape for example) aer interrupt was not MSI/MSI-X/INTx but using interrupt line independently. This patch add a "aer" interrupt-names for aer interrupt. With the interrupt-names "aer", code could probe aer interrupt line for pcie root port, replace the aer interrupt

Re: [PATCH 2/3] ARM64: dts: amlogic: Add basic support for Amlogic S905X

On Mon, Sep 12, 2016 at 2:43 PM, Andreas Färber wrote: > Am 12.09.2016 um 22:43 schrieb Kevin Hilman: >> Carlo Caione writes: >>> On Mon, Sep 12, 2016 at 6:28 PM, Andreas Färber wrote: >>> > +Boards with the Amlogic Meson GXL SoC shall

Re: [PATCH 2/3] ARM64: dts: amlogic: Add basic support for Amlogic S905X

On Mon, Sep 12, 2016 at 2:43 PM, Andreas Färber wrote: > Am 12.09.2016 um 22:43 schrieb Kevin Hilman: >> Carlo Caione writes: >>> On Mon, Sep 12, 2016 at 6:28 PM, Andreas Färber wrote: >>> > +Boards with the Amlogic Meson GXL SoC shall have the following > properties: > + Required

[PATCH] gpio: aspeed: Fix missing licence warning in modpost

Stephen Rothwell wrote: > After merging the gpio tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-aspeed.o > > Introduced by commit > > 361b79119a4b ("gpio: Add

[PATCH] gpio: aspeed: Fix missing licence warning in modpost

Stephen Rothwell wrote: > After merging the gpio tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-aspeed.o > > Introduced by commit > > 361b79119a4b ("gpio: Add Aspeed driver") Fix it by

linux-next: Tree for Sep 13

Hi all, Changes since 20160912: The v4l-dvb tree lost its build failure. The netfilter-next tree gained a conflict against the net tree. The kbuild tree gained a conflict against Linus' tree and still had its build warnings for PowerPC, for which I reverted a commit. The gpio tree lost its

linux-next: Tree for Sep 13

Hi all, Changes since 20160912: The v4l-dvb tree lost its build failure. The netfilter-next tree gained a conflict against the net tree. The kbuild tree gained a conflict against Linus' tree and still had its build warnings for PowerPC, for which I reverted a commit. The gpio tree lost its

Re: [PATCH 1/5] ipc/sem: do not call wake_sem_queue_do() prematurely

Hi Davidlohr, On 09/12/2016 01:53 PM, Davidlohr Bueso wrote: ... as this call should obviously be paired with its _prepare() counterpart. At least whenever possible, as there is no harm in calling it bogusly as we do now in a few places. I would define the interface differently: WAKE_Q creates

Re: [PATCH 1/5] ipc/sem: do not call wake_sem_queue_do() prematurely

Hi Davidlohr, On 09/12/2016 01:53 PM, Davidlohr Bueso wrote: ... as this call should obviously be paired with its _prepare() counterpart. At least whenever possible, as there is no harm in calling it bogusly as we do now in a few places. I would define the interface differently: WAKE_Q creates

linux-next: build warning after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc allyesconfig) produced this warning: drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c: In function 'ibmvscsis_rdma': drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c:3190:20: warning: unused variable 'srp' [-Wunused-variable] struct

linux-next: build warning after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc allyesconfig) produced this warning: drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c: In function 'ibmvscsis_rdma': drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c:3190:20: warning: unused variable 'srp' [-Wunused-variable] struct

Re: linux-next: manual merge of the kbuild tree with Linus' tree

On Tue, 13 Sep 2016 14:02:57 +1000 Stephen Rothwell wrote: > Hi Michal, > > [For the new cc's, we are discussing the "thin archives" and "link dead > code/data elimination" patches in the kbuild tree.] > > On Tue, 13 Sep 2016 09:39:45 +1000 Stephen Rothwell

Re: linux-next: manual merge of the kbuild tree with Linus' tree

On Tue, 13 Sep 2016 14:02:57 +1000 Stephen Rothwell wrote: > Hi Michal, > > [For the new cc's, we are discussing the "thin archives" and "link dead > code/data elimination" patches in the kbuild tree.] > > On Tue, 13 Sep 2016 09:39:45 +1000 Stephen Rothwell > wrote: > > > > On Mon, 12 Sep

Re: DAX mapping detection (was: Re: [PATCH] Fix region lost in /proc/self/smaps)

On Mon, Sep 12, 2016 at 6:31 PM, Nicholas Piggin wrote: > On Mon, 12 Sep 2016 08:01:48 -0700 [..] > That said, a noop system call is on the order of 100 cycles nowadays, > so rushing to implement these APIs without seeing good numbers and > actual users ready to go seems

Re: DAX mapping detection (was: Re: [PATCH] Fix region lost in /proc/self/smaps)

On Mon, Sep 12, 2016 at 6:31 PM, Nicholas Piggin wrote: > On Mon, 12 Sep 2016 08:01:48 -0700 [..] > That said, a noop system call is on the order of 100 cycles nowadays, > so rushing to implement these APIs without seeing good numbers and > actual users ready to go seems premature. *This* is the

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

Peter, thank you. on 09/12/2016 07:41 PM, Peter Zijlstra wrote: > On Mon, Sep 12, 2016 at 01:37:27PM +0200, Peter Zijlstra wrote: >> So what you're saying is that migration_stop_cpu() doesn't work because >> wait_for_completion() dequeues the task. >> >> True I suppose. Not sure I like your

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

Peter, thank you. on 09/12/2016 07:41 PM, Peter Zijlstra wrote: > On Mon, Sep 12, 2016 at 01:37:27PM +0200, Peter Zijlstra wrote: >> So what you're saying is that migration_stop_cpu() doesn't work because >> wait_for_completion() dequeues the task. >> >> True I suppose. Not sure I like your

Re: [PATCH] gpio: pca953x: initialize ret to zero to avoid returning garbage

On 12/09/2016 21:40, Linus Walleij wrote: On Fri, Sep 9, 2016 at 10:31 AM, Colin King wrote: From: Colin Ian King ret is not initialized so it contains garbage. Ensure garbage is not returned in the case that pdata && pdata->teardown is

Re: [PATCH] gpio: pca953x: initialize ret to zero to avoid returning garbage

On 12/09/2016 21:40, Linus Walleij wrote: On Fri, Sep 9, 2016 at 10:31 AM, Colin King wrote: From: Colin Ian King ret is not initialized so it contains garbage. Ensure garbage is not returned in the case that pdata && pdata->teardown is false by initializing ret to 0. Signed-off-by: Colin

Re: linux-next: manual merge of the kbuild tree with Linus' tree

Hi Michal, [For the new cc's, we are discussing the "thin archives" and "link dead code/data elimination" patches in the kbuild tree.] On Tue, 13 Sep 2016 09:39:45 +1000 Stephen Rothwell wrote: > > On Mon, 12 Sep 2016 11:03:08 +0200 Michal Marek wrote: >

Re: linux-next: manual merge of the kbuild tree with Linus' tree

Hi Michal, [For the new cc's, we are discussing the "thin archives" and "link dead code/data elimination" patches in the kbuild tree.] On Tue, 13 Sep 2016 09:39:45 +1000 Stephen Rothwell wrote: > > On Mon, 12 Sep 2016 11:03:08 +0200 Michal Marek wrote: > > > > On 2016-09-12 04:53, Nicholas

Re: [PATCH] crypto: qce: Initialize core src clock @100Mhz

On Sat 03 Sep 09:45 PDT 2016, Iaroslav Gridin wrote: > Without that, QCE performance is about 2x less. > > Signed-off-by: Iaroslav Gridin > --- > drivers/crypto/qce/core.c | 18 +- > drivers/crypto/qce/core.h | 2 +- > 2 files changed, 18 insertions(+), 2

Re: [PATCH] crypto: qce: Initialize core src clock @100Mhz

On Sat 03 Sep 09:45 PDT 2016, Iaroslav Gridin wrote: > Without that, QCE performance is about 2x less. > > Signed-off-by: Iaroslav Gridin > --- > drivers/crypto/qce/core.c | 18 +- > drivers/crypto/qce/core.h | 2 +- > 2 files changed, 18 insertions(+), 2 deletions(-) > >

Re: [PATCH 1/1] staging: slicoss: slicoss.c: fix different address space sparse warnings

Hi Peng, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20160912] [cannot apply to v4.8-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=a

Re: [PATCH 1/1] staging: slicoss: slicoss.c: fix different address space sparse warnings

Hi Peng, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20160912] [cannot apply to v4.8-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=a

Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'

On Mon, 12 Sep 2016 20:17:30 -0700 Guenter Roeck wrote: > Hi Nicholas, > > On 09/12/2016 07:00 PM, Nicholas Piggin wrote: > > On Mon, 12 Sep 2016 15:24:43 -0700 > > Guenter Roeck wrote: > > > >> Hi, > >> > >> your commit 'kbuild: allow archs to select

Re: [PATCH] ARM: dts: msm8974: Add definitions for QCE & cryptobam

On Tue 30 Aug 08:37 PDT 2016, Iaroslav Gridin wrote: > From: Voker57 > > Add device tree definitions for Qualcomm Cryptography engine and its BAM > Signed-off-by: Iaroslav Gridin > --- > arch/arm/boot/dts/qcom-msm8974.dtsi | 42 >

Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'

On Mon, 12 Sep 2016 20:17:30 -0700 Guenter Roeck wrote: > Hi Nicholas, > > On 09/12/2016 07:00 PM, Nicholas Piggin wrote: > > On Mon, 12 Sep 2016 15:24:43 -0700 > > Guenter Roeck wrote: > > > >> Hi, > >> > >> your commit 'kbuild: allow archs to select link dead code/data elimination' > >> is

Re: [PATCH] ARM: dts: msm8974: Add definitions for QCE & cryptobam

On Tue 30 Aug 08:37 PDT 2016, Iaroslav Gridin wrote: > From: Voker57 > > Add device tree definitions for Qualcomm Cryptography engine and its BAM > Signed-off-by: Iaroslav Gridin > --- > arch/arm/boot/dts/qcom-msm8974.dtsi | 42 > + > 1 file changed, 42

Re: [RFC PATCH 1/2] mm, mincore2(): retrieve dax and tlb-size attributes of an address range

On Mon, Sep 12, 2016 at 7:16 PM, Nicholas Piggin wrote: > On Mon, 12 Sep 2016 10:29:17 -0700 [..] >> Certainly one of the new request flags can indicate that the vector is >> made up of larger entries. > > Hmm. Changing prototype depending on flags. I thought I was having > a

Re: [RFC PATCH 1/2] mm, mincore2(): retrieve dax and tlb-size attributes of an address range

On Mon, Sep 12, 2016 at 7:16 PM, Nicholas Piggin wrote: > On Mon, 12 Sep 2016 10:29:17 -0700 [..] >> Certainly one of the new request flags can indicate that the vector is >> made up of larger entries. > > Hmm. Changing prototype depending on flags. I thought I was having > a nightmare about

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Sat, Sep 10, 2016 at 10:28 AM, Greg Kroah-Hartman wrote: > On Sat, Sep 10, 2016 at 06:37:29PM +0200, Thomas Gleixner wrote: >> On Sat, 10 Sep 2016, Peter Zijlstra wrote: >> >> > On Sat, Sep 10, 2016 at 09:16:59AM -0700, Christoph Hellwig wrote: >> > > On Thu, Sep

Re: [PATCH] android: binder: Disable preemption while holding the global binder lock

On Sat, Sep 10, 2016 at 10:28 AM, Greg Kroah-Hartman wrote: > On Sat, Sep 10, 2016 at 06:37:29PM +0200, Thomas Gleixner wrote: >> On Sat, 10 Sep 2016, Peter Zijlstra wrote: >> >> > On Sat, Sep 10, 2016 at 09:16:59AM -0700, Christoph Hellwig wrote: >> > > On Thu, Sep 08, 2016 at 09:12:50AM -0700,

Re: [PATCH 00/15] drivers: net: use IS_ENABLED() instead of checking for built-in or module

From: Javier Martinez Canillas Date: Mon, 12 Sep 2016 10:03:31 -0400 > This trivial series is similar to [0] for net/ that you already merged, but > for drivers/net. The patches replaces the open coding to check for a Kconfig > symbol being built-in or module, with

Re: [PATCH 00/15] drivers: net: use IS_ENABLED() instead of checking for built-in or module

From: Javier Martinez Canillas Date: Mon, 12 Sep 2016 10:03:31 -0400 > This trivial series is similar to [0] for net/ that you already merged, but > for drivers/net. The patches replaces the open coding to check for a Kconfig > symbol being built-in or module, with IS_ENABLED() macro that does

RE: [PATCH for-next 02/10] IB/hns: Register add_gid and del_gid for GID Table management

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Monday, September 12, 2016 1:40 PM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen); > mehta.salil@gmail.com; linux-r...@vger.kernel.org; linux- >

RE: [PATCH for-next 02/10] IB/hns: Register add_gid and del_gid for GID Table management

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Monday, September 12, 2016 1:40 PM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen); > mehta.salil@gmail.com; linux-r...@vger.kernel.org; linux- >

Re: [PATCH 6/6] mfd: twl-core: Make it explicitly non-modular

* Paul Gortmaker [160912 07:41]: > The Kconfig currently controlling compilation of this code is: > > drivers/mfd/Kconfig:config TWL4030_CORE > drivers/mfd/Kconfig:bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support" > > ...meaning that it currently is not being

Re: [PATCH 6/6] mfd: twl-core: Make it explicitly non-modular

* Paul Gortmaker [160912 07:41]: > The Kconfig currently controlling compilation of this code is: > > drivers/mfd/Kconfig:config TWL4030_CORE > drivers/mfd/Kconfig:bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support" > > ...meaning that it currently is not being built as a module by anyone. >

[PATCH 0/1] staging: slicoss: slicoss: fix sparse warnings

linux-next next-20160909, commit-id d221eb9f Peng Sun (1): staging: slicoss: slicoss.c: fix different address space sparse warnings drivers/staging/slicoss/slicoss.c | 125 +++--- 1 file changed, 91 insertions(+), 34 deletions(-) -- 2.7.4

[PATCH 1/1] staging: slicoss: slicoss.c: fix different address space sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 125 +++--- 1 file changed, 91 insertions(+), 34 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 21280a3..6996143

[PATCH 0/1] staging: slicoss: slicoss: fix sparse warnings

linux-next next-20160909, commit-id d221eb9f Peng Sun (1): staging: slicoss: slicoss.c: fix different address space sparse warnings drivers/staging/slicoss/slicoss.c | 125 +++--- 1 file changed, 91 insertions(+), 34 deletions(-) -- 2.7.4

[PATCH 1/1] staging: slicoss: slicoss.c: fix different address space sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 125 +++--- 1 file changed, 91 insertions(+), 34 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 21280a3..6996143 100644 ---

linux-next: build warning after merge of the gpio tree

Hi Linus, After merging the gpio tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-aspeed.o Introduced by commit 361b79119a4b ("gpio: Add Aspeed driver") -- Cheers, Stephen Rothwell

linux-next: build warning after merge of the gpio tree

Hi Linus, After merging the gpio tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-aspeed.o Introduced by commit 361b79119a4b ("gpio: Add Aspeed driver") -- Cheers, Stephen Rothwell

Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'

Hi Nicholas, On 09/12/2016 07:00 PM, Nicholas Piggin wrote: On Mon, 12 Sep 2016 15:24:43 -0700 Guenter Roeck wrote: Hi, your commit 'kbuild: allow archs to select link dead code/data elimination' is causing the following build failure in -next when building

Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'

Hi Nicholas, On 09/12/2016 07:00 PM, Nicholas Piggin wrote: On Mon, 12 Sep 2016 15:24:43 -0700 Guenter Roeck wrote: Hi, your commit 'kbuild: allow archs to select link dead code/data elimination' is causing the following build failure in -next when building score:defconfig.

linux-next: manual merge of the gpio tree with the pinctrl tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: drivers/gpio/gpio-mxc.c between commit: e188cbf7564f ("gpio: mxc: shift gpio_mxc_init() to subsys_initcall level") from the pinctrl tree and commit: 2c8d6c869feb ("gpio: mxc: drop unused MODULE_ tags from

linux-next: manual merge of the gpio tree with the pinctrl tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: drivers/gpio/gpio-mxc.c between commit: e188cbf7564f ("gpio: mxc: shift gpio_mxc_init() to subsys_initcall level") from the pinctrl tree and commit: 2c8d6c869feb ("gpio: mxc: drop unused MODULE_ tags from

Re: [PATCH 4.7 00/59] 4.7.4-stable review

On 09/12/2016 08:29 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.7.4 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 should be

Re: [PATCH 4.7 00/59] 4.7.4-stable review

On 09/12/2016 08:29 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.7.4 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 should be

Re: [PATCH v2] mm, proc: Fix region lost in /proc/self/smaps

On 09/13/2016 03:10 AM, Michal Hocko wrote: On Mon 12-09-16 08:01:06, Dave Hansen wrote: On 09/12/2016 05:54 AM, Michal Hocko wrote: In order to fix this bug, we make 'file->version' indicate the end address of current VMA Doesn't this open doors to another weird cases. Say B would be

Re: [PATCH v2] mm, proc: Fix region lost in /proc/self/smaps

On 09/13/2016 03:10 AM, Michal Hocko wrote: On Mon 12-09-16 08:01:06, Dave Hansen wrote: On 09/12/2016 05:54 AM, Michal Hocko wrote: In order to fix this bug, we make 'file->version' indicate the end address of current VMA Doesn't this open doors to another weird cases. Say B would be

Re: [PATCH 4.4 000/192] 4.4.21-stable review

On 09/12/2016 09:58 AM, Greg Kroah-Hartman wrote: Many thanks for the majority of these patches to Sasha Levin, who dug them out of Canonical's 4.4 kernel tree. I have no idea why they never sent them in for inclusion on their own :( This is the start of the stable review cycle for the 4.4.21

Re: [PATCH 4.4 000/192] 4.4.21-stable review

On 09/12/2016 09:58 AM, Greg Kroah-Hartman wrote: Many thanks for the majority of these patches to Sasha Levin, who dug them out of Canonical's 4.4 kernel tree. I have no idea why they never sent them in for inclusion on their own :( This is the start of the stable review cycle for the 4.4.21

Re: [PATCH v2 05/20] docs-rst: CodingStyle.rst: Convert to ReST markup

On Mon, 2016-09-12 at 23:17 -0300, Mauro Carvalho Chehab wrote: > - Fix all chapter identation; > - add c blocks where needed; Assuming this is really useful and people agree with simple conversions of .txt to .rst (and it does have some use), there are a couple funky conversions if

Re: [PATCH v2 05/20] docs-rst: CodingStyle.rst: Convert to ReST markup

On Mon, 2016-09-12 at 23:17 -0300, Mauro Carvalho Chehab wrote: > - Fix all chapter identation; > - add c blocks where needed; Assuming this is really useful and people agree with simple conversions of .txt to .rst (and it does have some use), there are a couple funky conversions if

Re: Panic when insmod nfit_test.ko

On Mon, Sep 12, 2016 at 7:30 PM, ryan chen wrote: > Hi all, > Recently I'm trying to check the testing suite of nfit_test for nvdimm > on 4.8-rc5, and system got panic once insmod nfit_test.ko , > I've checked the RIP, I guess it panics due to NULL > nvdimm_map pointer,

Re: Panic when insmod nfit_test.ko

On Mon, Sep 12, 2016 at 7:30 PM, ryan chen wrote: > Hi all, > Recently I'm trying to check the testing suite of nfit_test for nvdimm > on 4.8-rc5, and system got panic once insmod nfit_test.ko , > I've checked the RIP, I guess it panics due to NULL > nvdimm_map pointer, i.e., accessing

Re: [PATCH] clk: hisilicon: add CRG driver for Hi3798CV200 SoC

Hi all, Sorry. I'll fixed this compiling error in the next version. Regards, Jiancheng On 2016/9/12 21:55, kbuild test robot wrote: > Hi Jiancheng, > > [auto build test ERROR on clk/clk-next] > [also build test ERROR on v4.8-rc6 next-20160912] > [if your patch is applied to the

Re: [PATCH] clk: hisilicon: add CRG driver for Hi3798CV200 SoC

Hi all, Sorry. I'll fixed this compiling error in the next version. Regards, Jiancheng On 2016/9/12 21:55, kbuild test robot wrote: > Hi Jiancheng, > > [auto build test ERROR on clk/clk-next] > [also build test ERROR on v4.8-rc6 next-20160912] > [if your patch is applied to the

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

on 09/12/2016 07:03 PM, Oleg Nesterov wrote: > On 09/10, Cheng Chao wrote: >> >> @@ -126,6 +126,17 @@ int stop_one_cpu(unsigned int cpu, cpu_stop_fn_t fn, >> void *arg) >> cpu_stop_init_done(, 1); >> if (!cpu_stop_queue_work(cpu, )) >> return -ENOENT; >> + >> +#if

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

on 09/12/2016 07:03 PM, Oleg Nesterov wrote: > On 09/10, Cheng Chao wrote: >> >> @@ -126,6 +126,17 @@ int stop_one_cpu(unsigned int cpu, cpu_stop_fn_t fn, >> void *arg) >> cpu_stop_init_done(, 1); >> if (!cpu_stop_queue_work(cpu, )) >> return -ENOENT; >> + >> +#if

Re: [PATCH V6 2/5] PCI/ACPI: Check platform specific ECAM quirks

Hi Tomasz 在 2016/9/10 3:24, Tomasz Nowicki 写道: Some platforms may not be fully compliant with generic set of PCI config accessors. For these cases we implement the way to overwrite CFG accessors set and configuration space range. In first place pci_mcfg_parse() saves machine's IDs and revision

Re: [PATCH V6 2/5] PCI/ACPI: Check platform specific ECAM quirks

Hi Tomasz 在 2016/9/10 3:24, Tomasz Nowicki 写道: Some platforms may not be fully compliant with generic set of PCI config accessors. For these cases we implement the way to overwrite CFG accessors set and configuration space range. In first place pci_mcfg_parse() saves machine's IDs and revision

[RFC][PATCH v1 2/2] libsas: Fix hotplug issue in libsas

Now the libsas hotplug has some issues, Dan Williams report a similar bug here: https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html The root cause of the issues is we use one workqueue(shost->work_q) to process libsas event, and we divide a hot-on or hot-remove flow to several

[RFC][PATCH v1 2/2] libsas: Fix hotplug issue in libsas

Now the libsas hotplug has some issues, Dan Williams report a similar bug here: https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html The root cause of the issues is we use one workqueue(shost->work_q) to process libsas event, and we divide a hot-on or hot-remove flow to several

[RFC][PATCH v1 1/2] libsas: Alloc dynamic work to avoid missing sas events

Now libsas hotplug work is static, LLDD driver queue the hotplug work into shost->work_q. If LLDD driver burst post lots hotplug event to libsas, the hotplug events may pending in the workqueue like shost->workq tail | PHYE_LOSS_OF_SIGNAL | PORTE_BYTES_DMAED | head In this case, if a new

[RFC][PATCH v1 1/2] libsas: Alloc dynamic work to avoid missing sas events

Now libsas hotplug work is static, LLDD driver queue the hotplug work into shost->work_q. If LLDD driver burst post lots hotplug event to libsas, the hotplug events may pending in the workqueue like shost->workq tail | PHYE_LOSS_OF_SIGNAL | PORTE_BYTES_DMAED | head In this case, if a new

[PATCH v2 10/20] ManagementStyle.rst: convert it to ReST markup

- Convert document name to ReST; - Convert footnotes; - Convert sections to ReST format; - Don't use _foo_, as Sphinx doesn't support underline. Instead, use bold; - While here, remove whitespaces at the end of lines. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH v2 10/20] ManagementStyle.rst: convert it to ReST markup

- Convert document name to ReST; - Convert footnotes; - Convert sections to ReST format; - Don't use _foo_, as Sphinx doesn't support underline. Instead, use bold; - While here, remove whitespaces at the end of lines. Signed-off-by: Mauro Carvalho Chehab ---

  1   2   3   4   5   6   7   8   9   10   >