Re: [PATCH] ARM: dts: qcom: msm8974: Add Sony Xperia Z1 Compact

On Sat 02 Dec 20:09 PST 2017, Attila Sz?ll??si wrote: > This patch adds a DTS file for Sony Xperia Z1 Compact with support for > regulators, serial UART, eMMC/SD-card, USB, charger, backlight, > coincell and buttons. > > Work based on arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts. > >

[PATCH v2] PCI: dwc: Use {upper,lower}_32_bits() macros for clarity

We have macros for getting the upper or lower 32 bits of a number. Use them here to shave a couple lines off the code and provide clarity. Signed-off-by: Stephen Boyd --- Changes from v1: * Update dw_msi_setup_msg() too * Reword commit text slightly drivers/pci/dwc/pcie-designware-host.c |

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

On Wed, Dec 27, 2017 at 11:42:52PM +0100, Antoine Tenart wrote: > Hi Russell, > > On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > > > > > +_eth2 { > > > + /* CPS Lane 5 */ > > > + status = "okay";

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

On Wed, Dec 27, 2017 at 11:42:52PM +0100, Antoine Tenart wrote: > Hi Russell, > > On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > > > > > +_eth2 { > > > + /* CPS Lane 5 */ > > > + status = "okay";

Re: [PATCH] pinctrl: msm: Delete an error message for a failed memory allocation in msm_pinctrl_probe()

On Wed 27 Dec 13:10 PST 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 27 Dec 2017 22:04:22 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > >

Re: [PATCH] pinctrl: msm: Delete an error message for a failed memory allocation in msm_pinctrl_probe()

On Wed 27 Dec 13:10 PST 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 27 Dec 2017 22:04:22 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring

[tip:x86/urgent] x86-32: Fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)

Commit-ID: ac461122c88a10b7d775de2f56467f097c9e627a Gitweb: https://git.kernel.org/tip/ac461122c88a10b7d775de2f56467f097c9e627a Author: Linus Torvalds AuthorDate: Wed, 27 Dec 2017 11:48:50 -0800 Committer: Thomas Gleixner CommitDate:

[tip:x86/urgent] x86-32: Fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)

Commit-ID: ac461122c88a10b7d775de2f56467f097c9e627a Gitweb: https://git.kernel.org/tip/ac461122c88a10b7d775de2f56467f097c9e627a Author: Linus Torvalds AuthorDate: Wed, 27 Dec 2017 11:48:50 -0800 Committer: Thomas Gleixner CommitDate: Wed, 27 Dec 2017 20:59:41 +0100 x86-32: Fix kexec

[tip:smp/urgent] cpu/hotplug: Move inline keyword at the beginning of declaration

Commit-ID: 76dc6c097d581ad8eeedf8e1a000423a3d742445 Gitweb: https://git.kernel.org/tip/76dc6c097d581ad8eeedf8e1a000423a3d742445 Author: Mathieu Malaterre AuthorDate: Tue, 26 Dec 2017 15:08:53 +0100 Committer: Thomas Gleixner CommitDate: Wed, 27 Dec

[tip:x86/urgent] x86: Remove unused parameter of prepare_switch_to

Commit-ID: 7ac139eaa6bbdb07c547b6916a808eab3897e0e3 Gitweb: https://git.kernel.org/tip/7ac139eaa6bbdb07c547b6916a808eab3897e0e3 Author: rodrigosiqueira AuthorDate: Fri, 15 Dec 2017 11:15:33 -0200 Committer: Thomas Gleixner CommitDate:

[tip:smp/urgent] cpu/hotplug: Move inline keyword at the beginning of declaration

Commit-ID: 76dc6c097d581ad8eeedf8e1a000423a3d742445 Gitweb: https://git.kernel.org/tip/76dc6c097d581ad8eeedf8e1a000423a3d742445 Author: Mathieu Malaterre AuthorDate: Tue, 26 Dec 2017 15:08:53 +0100 Committer: Thomas Gleixner CommitDate: Wed, 27 Dec 2017 19:41:04 +0100 cpu/hotplug:

[tip:x86/urgent] x86: Remove unused parameter of prepare_switch_to

Commit-ID: 7ac139eaa6bbdb07c547b6916a808eab3897e0e3 Gitweb: https://git.kernel.org/tip/7ac139eaa6bbdb07c547b6916a808eab3897e0e3 Author: rodrigosiqueira AuthorDate: Fri, 15 Dec 2017 11:15:33 -0200 Committer: Thomas Gleixner CommitDate: Wed, 27 Dec 2017 20:37:41 +0100 x86: Remove unused

Re: [PATCH] bpf: selftest for late caller stack size increase

On 12/22/2017 07:12 PM, Jann Horn wrote: > This checks that it is not possible to bypass the total stack size check in > update_stack_depth() by calling a function that uses a large amount of > stack memory *before* using a large amount of stack memory in the caller. > > Currently, the first

Re: [PATCH] bpf: selftest for late caller stack size increase

On 12/22/2017 07:12 PM, Jann Horn wrote: > This checks that it is not possible to bypass the total stack size check in > update_stack_depth() by calling a function that uses a large amount of > stack memory *before* using a large amount of stack memory in the caller. > > Currently, the first

Re: [PATCH 3/4] libbpf: break loop earlier

On 12/27/2017 09:30 PM, Eric Leblond wrote: > On Wed, 2017-12-27 at 11:00 -0800, Alexei Starovoitov wrote: >> On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote: >>> Get out of the loop when we have a match. >>> >>> Signed-off-by: Eric Leblond >>> --- >>>

Re: [PATCH 3/4] libbpf: break loop earlier

On 12/27/2017 09:30 PM, Eric Leblond wrote: > On Wed, 2017-12-27 at 11:00 -0800, Alexei Starovoitov wrote: >> On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote: >>> Get out of the loop when we have a match. >>> >>> Signed-off-by: Eric Leblond >>> --- >>> tools/lib/bpf/libbpf.c | 1 +

[PATCH 03/20] nvmem: vf610-ocotp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 02/20] nvmem: Introduce devm_nvmem_(un)register()

Introduce devm_nvmem_register()/devm_nvmem_unregister() to make .remove() unnecessary in trivial drivers. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin

[PATCH 03/20] nvmem: vf610-ocotp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 02/20] nvmem: Introduce devm_nvmem_(un)register()

Introduce devm_nvmem_register()/devm_nvmem_unregister() to make .remove() unnecessary in trivial drivers. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc:

[PATCH 04/20] nvmem: imx-ocotp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 04/20] nvmem: imx-ocotp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 06/20] nvmem: snvs_lgpr: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 06/20] nvmem: snvs_lgpr: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 00/20] Verbatim device names and devm_nvmem_(un)register()

Srinivas, all: This patchset contains various small changes that I recently made to NVMEM, more specifically: - Patches 1 and 2 are two changes I am hoping are acceptable upstream - Patches 3 to 14 are a follow up to patch 2 - Patches 15 to 20 are just trivial fixups and I am more than

[PATCH 18/20] nvmem: rockchip-efuse: Do not use ">dev" explicitly

There's "dev" variable for this already. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger

[PATCH 10/20] nvmem: meson-mx-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 12/20] nvmem: lpc18xx_otp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 00/20] Verbatim device names and devm_nvmem_(un)register()

Srinivas, all: This patchset contains various small changes that I recently made to NVMEM, more specifically: - Patches 1 and 2 are two changes I am hoping are acceptable upstream - Patches 3 to 14 are a follow up to patch 2 - Patches 15 to 20 are just trivial fixups and I am more than

[PATCH 18/20] nvmem: rockchip-efuse: Do not use ">dev" explicitly

There's "dev" variable for this already. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc: linux-media...@lists.infradead.org Cc:

[PATCH 10/20] nvmem: meson-mx-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 12/20] nvmem: lpc18xx_otp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 11/20] nvmem: meson-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 15/20] nvmem: snvs_lpgpr: Convert commas to semicolons

Looks like commas were accidentally used where semicolons were supposed to be. Fix that. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 19/20] nvmem: imx-iim: Do not use ">dev" explicitly

There's already "dev" variable for that. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger

[PATCH 09/20] nvmem: mtk-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 01/20] nvmem: core: Allow specifying device name verbatim

Add code to allow avoid having nvmem core append a numeric suffix to the end of the name by passing config->id of -1. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione

[PATCH 14/20] nvmem: bcm-ocotp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 15/20] nvmem: snvs_lpgpr: Convert commas to semicolons

Looks like commas were accidentally used where semicolons were supposed to be. Fix that. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 19/20] nvmem: imx-iim: Do not use ">dev" explicitly

There's already "dev" variable for that. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc: linux-media...@lists.infradead.org Cc:

[PATCH 09/20] nvmem: mtk-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 01/20] nvmem: core: Allow specifying device name verbatim

Add code to allow avoid having nvmem core append a numeric suffix to the end of the name by passing config->id of -1. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc:

[PATCH 14/20] nvmem: bcm-ocotp: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 11/20] nvmem: meson-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 17/20] nvmem: vf610-ocotp: Do not use ">dev" explicitly

There already a "dev" variable for that. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger

[PATCH 20/20] nvmem: bcm-ocotp: Do not use ">dev" explicitly

There's "dev" variable for this already. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger

[PATCH 16/20] nvmem: rockchip-efuse: Make use of of_device_get_match_data()

Simplify code a bit by using of_device_get_match_data() instead of of_match_device(). Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 05/20] nvmem: uniphier-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 17/20] nvmem: vf610-ocotp: Do not use ">dev" explicitly

There already a "dev" variable for that. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc: linux-media...@lists.infradead.org Cc:

[PATCH 20/20] nvmem: bcm-ocotp: Do not use ">dev" explicitly

There's "dev" variable for this already. Use it. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc: linux-media...@lists.infradead.org Cc:

[PATCH 16/20] nvmem: rockchip-efuse: Make use of of_device_get_match_data()

Simplify code a bit by using of_device_get_match_data() instead of of_match_device(). Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 05/20] nvmem: uniphier-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 13/20] nvmem: imx-iim: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 07/20] nvmem: rockchip-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 08/20] nvmem: qfprom: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman

[PATCH 13/20] nvmem: imx-iim: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 07/20] nvmem: rockchip-efuse: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 08/20] nvmem: qfprom: Convert to use devm_nvmem_register()

Drop all of the code related to .remove hook and make use of devm_nvmem_register() instead. Cc: Srinivas Kandagatla Cc: Heiko Stuebner Cc: Masahiro Yamada Cc: Carlo Caione Cc: Kevin Hilman Cc: Matthias Brugger Cc: Joachim Eastwood Cc: cphe...@gmail.com Cc: linux-kernel@vger.kernel.org Cc:

Re: [RFC PATCH bpf-next v2 4/4] error-injection: Support fault injection framework

On 12/27/17 12:09 AM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 18:12:56 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:48:25PM +0900, Masami Hiramatsu wrote: Support in-kernel fault-injection framework via debugfs. This allows you to inject a

Re: [RFC PATCH bpf-next v2 4/4] error-injection: Support fault injection framework

On 12/27/17 12:09 AM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 18:12:56 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:48:25PM +0900, Masami Hiramatsu wrote: Support in-kernel fault-injection framework via debugfs. This allows you to inject a conditional error to specified

[PATCH] perf/x86/intel: Fix minor memleak on Skylake perf initialization

From: Andi Kleen Tommi reports: I'm seeing this kmemleak report in v4.15-rc4: unreferenced object 0x8801f3d5d720 (size 64): comm "swapper/0", pid 1, jiffies 4294667312 (age 2687.423s) hex dump (first 32 bytes): 60 d1 41 ad ff ff ff ff 20 d1 41 ad ff ff ff ff

[PATCH] perf/x86/intel: Fix minor memleak on Skylake perf initialization

From: Andi Kleen Tommi reports: I'm seeing this kmemleak report in v4.15-rc4: unreferenced object 0x8801f3d5d720 (size 64): comm "swapper/0", pid 1, jiffies 4294667312 (age 2687.423s) hex dump (first 32 bytes): 60 d1 41 ad ff ff ff ff 20 d1 41 ad ff ff ff ff `.A. .A.

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On 12/26/17 9:56 PM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 17:57:32 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:46:59PM +0900, Masami Hiramatsu wrote: Check whether error injectable event is on function entry or not. Currently it checks the

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On 12/26/17 9:56 PM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 17:57:32 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:46:59PM +0900, Masami Hiramatsu wrote: Check whether error injectable event is on function entry or not. Currently it checks the event is ftrace-based kprobes

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

Hi Russell, On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > > > +_eth2 { > > + /* CPS Lane 5 */ > > + status = "okay"; > > + phy-mode = "2500base-x"; > > + /* Generic PHY, providing serdes

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

Hi Russell, On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > > > +_eth2 { > > + /* CPS Lane 5 */ > > + status = "okay"; > > + phy-mode = "2500base-x"; > > + /* Generic PHY, providing serdes

Re: [PATCH v6 06/18] PCI: designware-ep: Add generic function for raising MSI irq

On Tue, Dec 26, 2017 at 06:20:54PM +0530, Kishon Vijay Abraham I wrote: > Hi Niklas, Hello Kishon > > On Wednesday 20 December 2017 04:59 AM, Niklas Cassel wrote: > > Add a generic function for raising MSI irqs that can be used by all > > DWC based controllers. > > > > Note that certain

Re: [PATCH v6 06/18] PCI: designware-ep: Add generic function for raising MSI irq

On Tue, Dec 26, 2017 at 06:20:54PM +0530, Kishon Vijay Abraham I wrote: > Hi Niklas, Hello Kishon > > On Wednesday 20 December 2017 04:59 AM, Niklas Cassel wrote: > > Add a generic function for raising MSI irqs that can be used by all > > DWC based controllers. > > > > Note that certain

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > This patch enables the fourth network interface on the Marvell > Macchiatobin. It is configured in the 2500Base-X PHY mode. > > Signed-off-by: Antoine Tenart > --- >

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > This patch enables the fourth network interface on the Marvell > Macchiatobin. It is configured in the 2500Base-X PHY mode. > > Signed-off-by: Antoine Tenart > --- > arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 8

[PATCH net-next 2/6] phy: cp110-comphy: 2.5G SGMII mode

This patch allow the CP100 comphy to configure some lanes in the 2.5G SGMII mode. This mode is quite close to SGMII and uses nearly the same code path. Signed-off-by: Antoine Tenart --- drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 17 ++--- 1

[PATCH net-next 4/6] net: mvpp2: 2500baseX support

This patch adds the 2500Base-X PHY mode support in the Marvell PPv2 driver. 2500Base-X is quite close to 1000Base-X and SGMII modes and uses nearly the same code path. Signed-off-by: Antoine Tenart --- drivers/net/ethernet/marvell/mvpp2.c | 40

[PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

This patch enables the fourth network interface on the Marvell Macchiatobin. It is configured in the 2500Base-X PHY mode. Signed-off-by: Antoine Tenart --- arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 8 1 file changed, 8 insertions(+) diff

[PATCH net-next 2/6] phy: cp110-comphy: 2.5G SGMII mode

This patch allow the CP100 comphy to configure some lanes in the 2.5G SGMII mode. This mode is quite close to SGMII and uses nearly the same code path. Signed-off-by: Antoine Tenart --- drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 17 ++--- 1 file changed, 14 insertions(+), 3

[PATCH net-next 4/6] net: mvpp2: 2500baseX support

This patch adds the 2500Base-X PHY mode support in the Marvell PPv2 driver. 2500Base-X is quite close to 1000Base-X and SGMII modes and uses nearly the same code path. Signed-off-by: Antoine Tenart --- drivers/net/ethernet/marvell/mvpp2.c | 40 1 file

[PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

This patch enables the fourth network interface on the Marvell Macchiatobin. It is configured in the 2500Base-X PHY mode. Signed-off-by: Antoine Tenart --- arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 8 1 file changed, 8 insertions(+) diff --git

[PATCH net-next 3/6] net: mvpp2: 1000baseX support

This patch adds the 1000Base-X PHY mode support in the Marvell PPv2 driver. 1000Base-X is quite close the SGMII and uses nearly the same code path. Signed-off-by: Antoine Tenart --- drivers/net/ethernet/marvell/mvpp2.c | 45

[PATCH net-next 3/6] net: mvpp2: 1000baseX support

This patch adds the 1000Base-X PHY mode support in the Marvell PPv2 driver. 1000Base-X is quite close the SGMII and uses nearly the same code path. Signed-off-by: Antoine Tenart --- drivers/net/ethernet/marvell/mvpp2.c | 45 1 file changed, 35 insertions(+),

[PATCH net-next 6/6] arm64: dts: marvell: add Ethernet aliases

From: Yan Markman This patch adds Ethernet aliases in the Marvell Aramada 7040 DB, 8040 DB and 8040 mcbin device trees so that the bootloader setup the MAC addresses correctly. Signed-off-by: Yan Markman [Antoine: commit message, small fixes]

[PATCH net-next 6/6] arm64: dts: marvell: add Ethernet aliases

From: Yan Markman This patch adds Ethernet aliases in the Marvell Aramada 7040 DB, 8040 DB and 8040 mcbin device trees so that the bootloader setup the MAC addresses correctly. Signed-off-by: Yan Markman [Antoine: commit message, small fixes] Signed-off-by: Antoine Tenart ---

[PATCH net-next 0/6] net: mvpp2: 1000BaseX and 2000BaseX support

Hi all, This series adds 1000BaseX and 2500BaseX support to the Marvell PPv2 driver. In order to use it, the 2.5 SGMII mode is added in the Marvell common PHY driver (cp110-comphy). Thanks to theses patches the fourth network interface can be used on the mcbin, and two patches are attached: one

[PATCH net-next 0/6] net: mvpp2: 1000BaseX and 2000BaseX support

Hi all, This series adds 1000BaseX and 2500BaseX support to the Marvell PPv2 driver. In order to use it, the 2.5 SGMII mode is added in the Marvell common PHY driver (cp110-comphy). Thanks to theses patches the fourth network interface can be used on the mcbin, and two patches are attached: one

[PATCH net-next 1/6] phy: add 2.5G SGMII mode to the phy_mode enum

This patch adds one more generic PHY mode to the phy_mode enum, to allow configuring generic PHYs to the 2.5G SGMII mode by using the set_mode callback. Signed-off-by: Antoine Tenart --- include/linux/phy/phy.h | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH net-next 1/6] phy: add 2.5G SGMII mode to the phy_mode enum

This patch adds one more generic PHY mode to the phy_mode enum, to allow configuring generic PHYs to the 2.5G SGMII mode by using the set_mode callback. Signed-off-by: Antoine Tenart --- include/linux/phy/phy.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/linux/phy/phy.h

Re: [PATCH v3 1/5] dt-bindings: at24: consistently document the compatible property

On 2017-12-27 14:50, Bartosz Golaszewski wrote: > Current description of the compatible property for at24 is quite vague. > > State explicitly that any "," pair is accepted as > long as one of the listed strings is used as fallback. > > Signed-off-by: Bartosz Golaszewski > --- >

Re: [PATCH v3 1/5] dt-bindings: at24: consistently document the compatible property

On 2017-12-27 14:50, Bartosz Golaszewski wrote: > Current description of the compatible property for at24 is quite vague. > > State explicitly that any "," pair is accepted as > long as one of the listed strings is used as fallback. > > Signed-off-by: Bartosz Golaszewski > --- >

Re: [PATCH v5 15/15] devicetree: bindings: Document qcom,pvs

On Wed, Dec 27, 2017 at 4:20 AM, Sricharan R wrote: > Hi Rob, > > On 12/26/2017 11:06 PM, Rob Herring wrote: >> On Thu, Dec 21, 2017 at 5:53 AM, Sricharan R >> wrote: >>> Hi Rob, >>> >>> On 12/21/2017 2:48 AM, Rob Herring wrote: On Wed,

Re: [PATCH v5 15/15] devicetree: bindings: Document qcom,pvs

On Wed, Dec 27, 2017 at 4:20 AM, Sricharan R wrote: > Hi Rob, > > On 12/26/2017 11:06 PM, Rob Herring wrote: >> On Thu, Dec 21, 2017 at 5:53 AM, Sricharan R >> wrote: >>> Hi Rob, >>> >>> On 12/21/2017 2:48 AM, Rob Herring wrote: On Wed, Dec 20, 2017 at 11:55:33AM +0530, Sricharan R wrote:

Re: [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On Wed, Dec 27, 2017 at 2:56 AM, Viresh Kumar wrote: > On 26-12-17, 14:29, Rob Herring wrote: >> On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote: > >> > +On some platforms the exact frequency or voltage may be hidden from the >> > OS by >> > +the firmware

Re: [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On Wed, Dec 27, 2017 at 2:56 AM, Viresh Kumar wrote: > On 26-12-17, 14:29, Rob Herring wrote: >> On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote: > >> > +On some platforms the exact frequency or voltage may be hidden from the >> > OS by >> > +the firmware and the "opp-hz" or the

Re: [PATCH v4] hwrng: exynos - add Samsung Exynos True RNG driver

Łukasz, On Wed, Dec 27, 2017 at 11:12 AM, Łukasz Stelmach wrote: > It was <2017-12-22 pią 19:30>, when Philippe Ombredanne wrote: >> On Fri, Dec 22, 2017 at 5:38 PM, Łukasz Stelmach >> wrote: >>> It was <2017-12-22 pią 14:34>, when Philippe

Re: [PATCH v4] hwrng: exynos - add Samsung Exynos True RNG driver

Łukasz, On Wed, Dec 27, 2017 at 11:12 AM, Łukasz Stelmach wrote: > It was <2017-12-22 pią 19:30>, when Philippe Ombredanne wrote: >> On Fri, Dec 22, 2017 at 5:38 PM, Łukasz Stelmach >> wrote: >>> It was <2017-12-22 pią 14:34>, when Philippe Ombredanne wrote: Łukasz, On Fri, Dec

[PATCH] pinctrl: spear: Delete an error message for a failed memory allocation in spear_pinctrl_probe()

From: Markus Elfring Date: Wed, 27 Dec 2017 22:44:04 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] pinctrl: spear: Delete an error message for a failed memory allocation in spear_pinctrl_probe()

From: Markus Elfring Date: Wed, 27 Dec 2017 22:44:04 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/pinctrl/spear/pinctrl-spear.c | 4 +--- 1 file changed, 1

Re: [PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Hi Yong, On Thu, Dec 21, 2017 at 10:49:35AM +0800, Yong wrote: > Hi, > > On Tue, 19 Dec 2017 13:53:28 +0200 > Sakari Ailus wrote: > > > Hi Yong, > > > > On Thu, Jul 27, 2017 at 01:01:36PM +0800, Yong Deng wrote: > > > Add binding documentation for Allwinner V3s CSI. > > >

Re: [PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Hi Yong, On Thu, Dec 21, 2017 at 10:49:35AM +0800, Yong wrote: > Hi, > > On Tue, 19 Dec 2017 13:53:28 +0200 > Sakari Ailus wrote: > > > Hi Yong, > > > > On Thu, Jul 27, 2017 at 01:01:36PM +0800, Yong Deng wrote: > > > Add binding documentation for Allwinner V3s CSI. > > > > > >

Re: v4.15: camera problems on n900

1;2802;0cOn Wed 2017-12-27 23:17:19, Sakari Ailus wrote: > On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > > Hi! > > > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > > seconds, but then I get repeated oopses. > > > > On v4.15-rc0.5 (commit

Re: [PATCH 2/3] dt-bindings: mtd: atmel-quadspi: add an optional property 'dmacap,memcpy'

Hi Rob, + Ludovic Desroches, maintainer of the DMA controller drivers for AT91 SoCs. Le 27/12/2017 à 00:23, Rob Herring a écrit : > On Sun, Dec 24, 2017 at 05:36:05AM +0100, Cyrille Pitchen wrote: >> The optional 'dmacap,memcpy' DT property tells the Atmel QSPI controller >> driver to reserve

Re: v4.15: camera problems on n900

1;2802;0cOn Wed 2017-12-27 23:17:19, Sakari Ailus wrote: > On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > > Hi! > > > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > > seconds, but then I get repeated oopses. > > > > On v4.15-rc0.5 (commit

Re: [PATCH 2/3] dt-bindings: mtd: atmel-quadspi: add an optional property 'dmacap,memcpy'

Hi Rob, + Ludovic Desroches, maintainer of the DMA controller drivers for AT91 SoCs. Le 27/12/2017 à 00:23, Rob Herring a écrit : > On Sun, Dec 24, 2017 at 05:36:05AM +0100, Cyrille Pitchen wrote: >> The optional 'dmacap,memcpy' DT property tells the Atmel QSPI controller >> driver to reserve

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