Re: [PATCH 3/3] mm/page_owner: track page free call chain

On (07/03/16 01:16), Sergey Senozhatsky wrote: [..] > +#ifdef CONFIG_PAGE_OWNER_TRACK_FREE > +void __page_owner_free_pages(struct page *page, unsigned int order) > +{ > + int i; > + depot_stack_handle_t handle; > + struct page_ext *page_ext = lookup_page_ext(page); > + > + if

[PATCH] phy: fix error handling

This is likely that checking 'phy->hsic_clk' instead of 'phy->clk' is expected here. Signed-off-by: Christophe JAILLET --- drivers/phy/phy-sun9i-usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/phy/phy-sun9i-usb.c

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On (07/03/16 01:16), Sergey Senozhatsky wrote: [..] > +#ifdef CONFIG_PAGE_OWNER_TRACK_FREE > +void __page_owner_free_pages(struct page *page, unsigned int order) > +{ > + int i; > + depot_stack_handle_t handle; > + struct page_ext *page_ext = lookup_page_ext(page); > + > + if

[PATCH] phy: fix error handling

This is likely that checking 'phy->hsic_clk' instead of 'phy->clk' is expected here. Signed-off-by: Christophe JAILLET --- drivers/phy/phy-sun9i-usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/phy/phy-sun9i-usb.c b/drivers/phy/phy-sun9i-usb.c index

Re: [PATCH] drm/mediatek: fix error handling

On 07/03/2016 07:37 AM, Christophe JAILLET wrote: This is likely that checking 'phy_provider' instead of 'phy' is expected here. Signed-off-by: Christophe JAILLET --- drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH] drm/mediatek: fix error handling

On 07/03/2016 07:37 AM, Christophe JAILLET wrote: This is likely that checking 'phy_provider' instead of 'phy' is expected here. Signed-off-by: Christophe JAILLET --- drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] drm/mediatek: fix error handling

This is likely that checking 'phy_provider' instead of 'phy' is expected here. Signed-off-by: Christophe JAILLET --- drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_mipi_tx.c

[PATCH] drm/mediatek: fix error handling

This is likely that checking 'phy_provider' instead of 'phy' is expected here. Signed-off-by: Christophe JAILLET --- drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_mipi_tx.c

Re: [PATCH v2 1/2] arm64: implement FTRACE_WITH_REGS

Hi, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 1/2] arm64: implement FTRACE_WITH_REGS

Hi, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

0192688ec6: BUG: unable to handle kernel NULL pointer dereference at (null)

FYI, we noticed the following commit: https://github.com/0day-ci/linux frowand-list-gmail-com/Portable-Device-Tree-Connector-conceptual/20160703-081931 commit 0192688ec6f2161c0f2b99d38cc459f39285398f ("device tree connectors, using plugs and sockets.") in testcase: boot on test machine: 2

0192688ec6: BUG: unable to handle kernel NULL pointer dereference at (null)

FYI, we noticed the following commit: https://github.com/0day-ci/linux frowand-list-gmail-com/Portable-Device-Tree-Connector-conceptual/20160703-081931 commit 0192688ec6f2161c0f2b99d38cc459f39285398f ("device tree connectors, using plugs and sockets.") in testcase: boot on test machine: 2

[PATCH] fs: btrfs: Replace -ENOENT by -ERANGE in btrfs_get_acl()

size contains the value returned by posix_acl_from_xattr(), which returns -ERANGE, -ENODATA, zero, or an integer greater than zero. So replace -ENOENT by -ERANGE. Signed-off-by: Salah Triki --- fs/btrfs/acl.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff

[PATCH] fs: btrfs: Replace -ENOENT by -ERANGE in btrfs_get_acl()

size contains the value returned by posix_acl_from_xattr(), which returns -ERANGE, -ENODATA, zero, or an integer greater than zero. So replace -ENOENT by -ERANGE. Signed-off-by: Salah Triki --- fs/btrfs/acl.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/fs/btrfs/acl.c

[PATCH] Staging: rtl8712: Fixed brace and comment style issue

Fixed issues with coding style. Signed-off-by: Anuradha Weeraman --- drivers/staging/rtl8712/xmit_linux.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/staging/rtl8712/xmit_linux.c b/drivers/staging/rtl8712/xmit_linux.c index

[PATCH] Staging: rtl8712: Fixed brace and comment style issue

Fixed issues with coding style. Signed-off-by: Anuradha Weeraman --- drivers/staging/rtl8712/xmit_linux.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/staging/rtl8712/xmit_linux.c b/drivers/staging/rtl8712/xmit_linux.c index 695f9b9..1e86133

fs/xfs/xfs_ondisk.h:86:2: error: call to '__compiletime_assert_86' declared with attribute error: XFS: sizeof(xfs_dir2_data_unused_t) is wrong, expected 6

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 4 months ago

fs/xfs/xfs_ondisk.h:86:2: error: call to '__compiletime_assert_86' declared with attribute error: XFS: sizeof(xfs_dir2_data_unused_t) is wrong, expected 6

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 4 months ago

Re: [PATCH] thermal: rcar-thermal: enable hwmon when thermal_zone

Hi, [auto build test ERROR on thermal/next] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] thermal: rcar-thermal: enable hwmon when thermal_zone

Hi, [auto build test ERROR on thermal/next] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] Crypto:Add HMAC-SHA3 test modes and test vectors

On Fri, Jul 01, 2016 at 11:16:54AM +0530, Raveendra Padasalagi wrote: > This patch adds HMAC-SHA3 test modes in tcrypt module > and related test vectors. > > Signed-off-by: Raveendra Padasalagi Patch applied. Thanks. -- Email: Herbert Xu

Re: [PATCH] Crypto:Add HMAC-SHA3 test modes and test vectors

On Fri, Jul 01, 2016 at 11:16:54AM +0530, Raveendra Padasalagi wrote: > This patch adds HMAC-SHA3 test modes in tcrypt module > and related test vectors. > > Signed-off-by: Raveendra Padasalagi Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP

Re: [PATCH] crypto: omap-sham - increase cra_proirity to 400

On Wed, Jun 29, 2016 at 11:11:36AM -0500, Bin Liu wrote: > Some software alg has cra_priority as higher as 300, so increase > omap-sham priority to 400 to ensure it is on top of any software alg. > > Signed-off-by: Bin Liu Patch applied. Thanks. -- Email: Herbert Xu

Re: [PATCH] crypto: omap-sham - increase cra_proirity to 400

On Wed, Jun 29, 2016 at 11:11:36AM -0500, Bin Liu wrote: > Some software alg has cra_priority as higher as 300, so increase > omap-sham priority to 400 to ensure it is on top of any software alg. > > Signed-off-by: Bin Liu Patch applied. Thanks. -- Email: Herbert Xu Home Page:

include/linux/kprobes.h:332:2: error: invalid use of undefined type 'struct kprobe_ctlblk'

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: abec1a806e0c3cf168999667d5fb6218398ef12a percpu: Make __verify_pcu_ptr handle per cpu pointers to arrays date:

include/linux/kprobes.h:332:2: error: invalid use of undefined type 'struct kprobe_ctlblk'

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: abec1a806e0c3cf168999667d5fb6218398ef12a percpu: Make __verify_pcu_ptr handle per cpu pointers to arrays date:

(.init.text+0x2b8): multiple definition of `plat_irq_setup'

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: 7480e0aabd5f9e6c3e3b72ed206e89284e90f11f sh: add device tree support and generic board using device tree date:

(.init.text+0x2b8): multiple definition of `plat_irq_setup'

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: 7480e0aabd5f9e6c3e3b72ed206e89284e90f11f sh: add device tree support and generic board using device tree date:

[PATCH 1/1] irqdomain: Fix irq_domain_alloc_irqs_recursive() error handling

If an irq_domain is auto-recursive and irq_domain_alloc_irqs_recursive() for its parent has returned an error, then do return and avoid calling irq_domain_free_irqs_recursive() uselessly, because: - if domain->ops->alloc() had failed for an auto-recursive irq_domain, then

[PATCH 1/1] irqdomain: Fix irq_domain_alloc_irqs_recursive() error handling

If an irq_domain is auto-recursive and irq_domain_alloc_irqs_recursive() for its parent has returned an error, then do return and avoid calling irq_domain_free_irqs_recursive() uselessly, because: - if domain->ops->alloc() had failed for an auto-recursive irq_domain, then

Re: [RFC 0/1] ARM: print MHz in /proc/cpuinfo

Hi Russell, Jon, On 06/07/2016 06:18 PM, Russell King - ARM Linux wrote: > On Tue, Jun 07, 2016 at 05:08:32PM -0400, Jon Mason wrote: >> Many users (and some applications) are expecting the CPU clock speed to >> be output in /proc/cpuinfo (as is done in x86, avr32, c6x, tile, parisc, >> ia64, and

Re: [RFC 0/1] ARM: print MHz in /proc/cpuinfo

Hi Russell, Jon, On 06/07/2016 06:18 PM, Russell King - ARM Linux wrote: > On Tue, Jun 07, 2016 at 05:08:32PM -0400, Jon Mason wrote: >> Many users (and some applications) are expecting the CPU clock speed to >> be output in /proc/cpuinfo (as is done in x86, avr32, c6x, tile, parisc, >> ia64, and

[RFC PATCH 1/1] device tree connectors, using plugs and sockets.

From: Frank Rowand This patch has been compiled but has not been booted. It is likely to contain bugs. Problem: mother boards may contain multiple connectors that daughter boards may be attached to. If two of the daughter boards can be described by the same .dtsi

[RFC PATCH 1/1] device tree connectors, using plugs and sockets.

From: Frank Rowand This patch has been compiled but has not been booted. It is likely to contain bugs. Problem: mother boards may contain multiple connectors that daughter boards may be attached to. If two of the daughter boards can be described by the same .dtsi file, then it should be

[RFC PATCH 0/1] Portable Device Tree Connector -- conceptual

From: Frank Rowand Hi All, This is version 2 of this email. Changes from version 1: - some rewording of the text - removed new (theoretical) dtc directive "/connector/" - added compatibility between mother board and daughter board - added info on applying a

[RFC PATCH 0/1] Portable Device Tree Connector -- conceptual

From: Frank Rowand Hi All, This is version 2 of this email. Changes from version 1: - some rewording of the text - removed new (theoretical) dtc directive "/connector/" - added compatibility between mother board and daughter board - added info on applying a single .dtbo to different

{standard input}:122: Error: number (0x9000000080000000) larger than 32 bits

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: 71458cfc782eafe4b27656e078d379a34e472adf kernel: add support for gcc 5 date: 1 year, 9 months ago config:

{standard input}:122: Error: number (0x9000000080000000) larger than 32 bits

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 99b0f54e6a3a4012aacfaada5644a8e520447d80 commit: 71458cfc782eafe4b27656e078d379a34e472adf kernel: add support for gcc 5 date: 1 year, 9 months ago config:

[PATCH] staging: fsl-mc: make bus/mc-bus explicitly non-modular

The Kconfig currently controlling compilation of this code is: config FSL_MC_BUS bool "Freescale Management Complex (MC) bus driver" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading the

[PATCH] staging: fsl-mc: make bus/mc-bus explicitly non-modular

The Kconfig currently controlling compilation of this code is: config FSL_MC_BUS bool "Freescale Management Complex (MC) bus driver" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading the

Re: [PATCH 0/4] sh: fix up modular use in non-modular code

[Re: [PATCH 0/4] sh: fix up modular use in non-modular code] On 02/06/2016 (Thu 15:54) Yoshinori Sato wrote: > On Fri, 27 May 2016 01:53:34 +0900, > Rich Felker wrote: > > > > On Thu, May 26, 2016 at 12:45:57PM -0400, Paul Gortmaker wrote: > > > [[PATCH 0/4] sh: fix up modular use in

Re: [PATCH 0/4] sh: fix up modular use in non-modular code

[Re: [PATCH 0/4] sh: fix up modular use in non-modular code] On 02/06/2016 (Thu 15:54) Yoshinori Sato wrote: > On Fri, 27 May 2016 01:53:34 +0900, > Rich Felker wrote: > > > > On Thu, May 26, 2016 at 12:45:57PM -0400, Paul Gortmaker wrote: > > > [[PATCH 0/4] sh: fix up modular use in

[GIT PULL] Please pull powerpc/linux.git powerpc-4.7-5 tag

Hi Linus, Please pull some more powerpc fixes for 4.7: The following changes since commit 844e3be47693f92a108cb1fb3b0606bf25e9c7a6:   powerpc/bpf/jit: Disable classic BPF JIT on ppc64le (2016-06-23 10:35:31 +1000) are available in the git repository at:  

[GIT PULL] Please pull powerpc/linux.git powerpc-4.7-5 tag

Hi Linus, Please pull some more powerpc fixes for 4.7: The following changes since commit 844e3be47693f92a108cb1fb3b0606bf25e9c7a6:   powerpc/bpf/jit: Disable classic BPF JIT on ppc64le (2016-06-23 10:35:31 +1000) are available in the git repository at:  

[PATCH][media] saa7134: fix warm Medion 7134 EEPROM read

When saa7134 module driving a Medion 7134 card is reloaded reads of this card EEPROM (required for automatic detection of tuner model) will be corrupted due to I2C gate in DVB-T demod being left closed. This sometimes also happens on first saa7134 module load after a warm reboot. Fix this by

[PATCH][media] saa7134: fix warm Medion 7134 EEPROM read

When saa7134 module driving a Medion 7134 card is reloaded reads of this card EEPROM (required for automatic detection of tuner model) will be corrupted due to I2C gate in DVB-T demod being left closed. This sometimes also happens on first saa7134 module load after a warm reboot. Fix this by

Re: [PATCH v2] tracing: Fix oops caused by graph notrace filter

Hi, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] tracing: Fix oops caused by graph notrace filter

Hi, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] tracing: Fix oops caused by graph notrace filter

Hi, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] tracing: Fix oops caused by graph notrace filter

Hi, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 00/14] PCI: trivial demodularization of builtin code

Firstly, this group of commits was chosen for the fact that they don't change anything even at a binary object file level ; they just replace module_platform_driver with builtin_platform_driver, and remove some MODULE_ tags that are no-ops in code. So the regression risk is zero here. More

[PATCH 04/14] PCI: generic: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_HOST_GENERIC drivers/pci/host/Kconfig: bool "Generic PCI host controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular

[PATCH 00/14] PCI: trivial demodularization of builtin code

Firstly, this group of commits was chosen for the fact that they don't change anything even at a binary object file level ; they just replace module_platform_driver with builtin_platform_driver, and remove some MODULE_ tags that are no-ops in code. So the regression risk is zero here. More

[PATCH 04/14] PCI: generic: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_HOST_GENERIC drivers/pci/host/Kconfig: bool "Generic PCI host controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular

[PATCH 05/14] PCI: hisi: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: host/Kconfig:config PCI_HISI host/Kconfig:bool "HiSilicon Hip05 and Hip06 SoCs PCIe controllers" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and macros,

[PATCH 07/14] PCI: layerscape: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_LAYERSCAPE drivers/pci/host/Kconfig: bool "Freescale Layerscape PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple instances of

[PATCH 05/14] PCI: hisi: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: host/Kconfig:config PCI_HISI host/Kconfig:bool "HiSilicon Hip05 and Hip06 SoCs PCIe controllers" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and macros,

[PATCH 07/14] PCI: layerscape: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_LAYERSCAPE drivers/pci/host/Kconfig: bool "Freescale Layerscape PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple instances of

[PATCH 06/14] PCI: keystone: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_KEYSTONE drivers/pci/host/Kconfig: bool "TI Keystone PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple instances of modular code

[PATCH 02/14] PCI: artpec6: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_ARTPEC6 drivers/pci/host/Kconfig: bool "Axis ARTPEC-6 PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code

[PATCH 06/14] PCI: keystone: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_KEYSTONE drivers/pci/host/Kconfig: bool "TI Keystone PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple instances of modular code

[PATCH 02/14] PCI: artpec6: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_ARTPEC6 drivers/pci/host/Kconfig: bool "Axis ARTPEC-6 PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code

Re: [PATCH RFC 0/7] support clk setting during kernel early boot

On 2016-07-01 18:12, Stephen Boyd wrote: > On 06/29, Dong Aisheng wrote: >> Recently several people met the kernel complaining >> "bad: scheduling from the idle thread!" issue which caused by >> sleeping during kernel early booting phase by calling clk >> APIs like clk_prepare_enable. >> >> See:

Re: [PATCH RFC 0/7] support clk setting during kernel early boot

On 2016-07-01 18:12, Stephen Boyd wrote: > On 06/29, Dong Aisheng wrote: >> Recently several people met the kernel complaining >> "bad: scheduling from the idle thread!" issue which caused by >> sleeping during kernel early booting phase by calling clk >> APIs like clk_prepare_enable. >> >> See:

[PATCH 09/14] PCI: rcar: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_RCAR_GEN2_PCIE drivers/pci/host/Kconfig: bool "Renesas R-Car PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular

[PATCH 11/14] PCI: tegra: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_TEGRA drivers/pci/host/Kconfig: bool "NVIDIA Tegra PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and

[PATCH 09/14] PCI: rcar: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_RCAR_GEN2_PCIE drivers/pci/host/Kconfig: bool "Renesas R-Car PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular

[PATCH 11/14] PCI: tegra: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_TEGRA drivers/pci/host/Kconfig: bool "NVIDIA Tegra PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and

[PATCH 1/2] net: ethernet: smsc: smsc911x: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 1/2] net: ethernet: smsc: smsc911x: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 08/14] PCI: mvebu: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_MVEBU drivers/pci/host/Kconfig: bool "Marvell EBU PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and

[PATCH 14/14] PCI: xgene: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_XGENE drivers/pci/host/Kconfig: bool "X-Gene PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and

[PATCH 10/14] PCI: rcar-gen2: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_RCAR_GEN2 drivers/pci/host/Kconfig: bool "Renesas R-Car Gen2 Internal PCI controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses

[PATCH 08/14] PCI: mvebu: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_MVEBU drivers/pci/host/Kconfig: bool "Marvell EBU PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and

[PATCH 14/14] PCI: xgene: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_XGENE drivers/pci/host/Kconfig: bool "X-Gene PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular code and

[PATCH 10/14] PCI: rcar-gen2: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_RCAR_GEN2 drivers/pci/host/Kconfig: bool "Renesas R-Car Gen2 Internal PCI controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses

[PATCH 12/14] PCI: thunder-ecam: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_HOST_THUNDER_ECAM drivers/pci/host/Kconfig: bool "Cavium Thunder ECAM controller to on-chip devices on pass-1.x silicon" ...meaning that it currently is not being built as a module by

[PATCH 12/14] PCI: thunder-ecam: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_HOST_THUNDER_ECAM drivers/pci/host/Kconfig: bool "Cavium Thunder ECAM controller to on-chip devices on pass-1.x silicon" ...meaning that it currently is not being built as a module by

[PATCH 2/2] net: ethernet: smsc: smsc911x: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/smsc/smsc911x.c | 18 ++ 1 files changed, 2 insertions(+), 16

[PATCH 13/14] PCI: thunder-pem: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_HOST_THUNDER_PEM drivers/pci/host/Kconfig: bool "Cavium Thunder PCIe controller to off-chip devices" ...meaning that it currently is not being built as a module by anyone. Lets remove the

[PATCH 2/2] net: ethernet: smsc: smsc911x: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/smsc/smsc911x.c | 18 ++ 1 files changed, 2 insertions(+), 16 deletions(-) diff

[PATCH 13/14] PCI: thunder-pem: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_HOST_THUNDER_PEM drivers/pci/host/Kconfig: bool "Cavium Thunder PCIe controller to off-chip devices" ...meaning that it currently is not being built as a module by anyone. Lets remove the

[PATCH 01/14] PCI: armada8k: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_ARMADA_8K drivers/pci/host/Kconfig: bool "Marvell Armada-8K PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular

[PATCH 03/14] PCI: designware-plat: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_DW_PLAT drivers/pci/host/Kconfig: bool "Platform bus based DesignWare PCIe Controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses

[PATCH 01/14] PCI: armada8k: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_ARMADA_8K drivers/pci/host/Kconfig: bool "Marvell Armada-8K PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses of modular

[PATCH 03/14] PCI: designware-plat: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_DW_PLAT drivers/pci/host/Kconfig: bool "Platform bus based DesignWare PCIe Controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the few trace uses

Re: [PATCH 2/2] input: add ADC resistor ladder driver

On Fri, Jul 1, 2016 at 2:30 PM, Alexandre Belloni wrote: > A common way of multiplexing buttons on a single input in cheap devices is > to use a resistor ladder on an ADC. This driver supports that configuration > by polling an ADC channel provided by IIO. >

Re: [PATCH 2/2] input: add ADC resistor ladder driver

On Fri, Jul 1, 2016 at 2:30 PM, Alexandre Belloni wrote: > A common way of multiplexing buttons on a single input in cheap devices is > to use a resistor ladder on an ADC. This driver supports that configuration > by polling an ADC channel provided by IIO. > > Signed-off-by: Alexandre Belloni >

[PATCH 2/2] net: ethernet: lantiq_etop: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/lantiq_etop.c | 16 ++-- 1 files changed, 2 insertions(+), 14

[PATCH 2/2] net: ethernet: lantiq_etop: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/lantiq_etop.c | 16 ++-- 1 files changed, 2 insertions(+), 14 deletions(-) diff --git

[PATCH 1/2] net: ethernet: lantiq_etop: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 1/2] net: ethernet: lantiq_etop: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 2/2] net: ethernet: cavium: octeon: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/cavium/octeon/octeon_mgmt.c | 25 + 1 files changed, 2

[PATCH 2/2] net: ethernet: cavium: octeon: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/cavium/octeon/octeon_mgmt.c | 25 + 1 files changed, 2 insertions(+), 23

[PATCH 1/2] net: ethernet: cavium: octeon: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 1/2] net: ethernet: cavium: octeon: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

Re: master build: 0 failures 4 warnings (v4.7-rc5-347-g99b0f54)

On Saturday, July 2, 2016 8:39:38 PM CEST Build bot for Mark Brown wrote: > Warnings: > > ../drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/polaris10_hwmgr.c:1817:4: > warning: this decimal constant is unsigned only in ISO C90 > >

Re: master build: 0 failures 4 warnings (v4.7-rc5-347-g99b0f54)

On Saturday, July 2, 2016 8:39:38 PM CEST Build bot for Mark Brown wrote: > Warnings: > > ../drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/polaris10_hwmgr.c:1817:4: > warning: this decimal constant is unsigned only in ISO C90 > >

[PATCH][RESEND] pps: kc: fix non-tickless system config dependency

CONFIG_NO_HZ currently only sets the default value of dynticks config so if PPS kernel consumer needs periodic timer ticks it should depend on !CONFIG_NO_HZ_COMMON instead of !CONFIG_NO_HZ. Otherwise it is possible to enable it even on tickless system which has CONFIG_NO_HZ not set and

[PATCH][RESEND] pps: kc: fix non-tickless system config dependency

CONFIG_NO_HZ currently only sets the default value of dynticks config so if PPS kernel consumer needs periodic timer ticks it should depend on !CONFIG_NO_HZ_COMMON instead of !CONFIG_NO_HZ. Otherwise it is possible to enable it even on tickless system which has CONFIG_NO_HZ not set and

  1   2   3   4   >