Re: [RFC v2 PATCH] mm/hotplug: enable memory hotplug for non-lru movable pages

hi Michal, Thank you for reviewing and sorry for late reply. On 01/26/2017 05:43 PM, Michal Hocko wrote: > On Wed 25-01-17 14:59:45, Yisheng Xie wrote: > > static unsigned long scan_movable_pages(unsigned long start, unsigned long > end) > { > @@ -1531,6 +1531,16 @@ static unsigned long

Re: [RFC v2 PATCH] mm/hotplug: enable memory hotplug for non-lru movable pages

hi Michal, Thank you for reviewing and sorry for late reply. On 01/26/2017 05:43 PM, Michal Hocko wrote: > On Wed 25-01-17 14:59:45, Yisheng Xie wrote: > > static unsigned long scan_movable_pages(unsigned long start, unsigned long > end) > { > @@ -1531,6 +1531,16 @@ static unsigned long

[PATCH v4 0/2] prctl: make PR_SET_CHILD_SUBREAPER deterministic

Oleg Nesterov (1): introduce the walk_process_tree() helper Pavel Tikhomirov (1): prctl: propagate has_child_subreaper flag to every descendant include/linux/sched.h | 3 +++ kernel/fork.c | 42 +++--- kernel/sys.c | 22

[PATCH v4 0/2] prctl: make PR_SET_CHILD_SUBREAPER deterministic

Oleg Nesterov (1): introduce the walk_process_tree() helper Pavel Tikhomirov (1): prctl: propagate has_child_subreaper flag to every descendant include/linux/sched.h | 3 +++ kernel/fork.c | 42 +++--- kernel/sys.c | 22

[PATCH v3 0/2] prctl: make PR_SET_CHILD_SUBREAPER deterministic

Oleg Nesterov (1): introduce the walk_process_tree() helper Pavel Tikhomirov (1): prctl: propagate has_child_subreaper flag to every descendant include/linux/sched.h | 3 +++ kernel/fork.c | 42 +++--- kernel/sys.c | 22

[PATCH] PCI/ASPM: Handle PCI-to-PCIe bridges as roots of PCIe hierarchies

In a struct pcie_link_state, link->root points to the pcie_link_state of the root of the PCIe hierarchy. For the topmost link, this points to itself (link->root = link). For others, we copy the pointer from the parent (link->root = link->parent->root). Previously we recognized that Root Ports

[PATCH v3 0/2] prctl: make PR_SET_CHILD_SUBREAPER deterministic

Oleg Nesterov (1): introduce the walk_process_tree() helper Pavel Tikhomirov (1): prctl: propagate has_child_subreaper flag to every descendant include/linux/sched.h | 3 +++ kernel/fork.c | 42 +++--- kernel/sys.c | 22

[PATCH] PCI/ASPM: Handle PCI-to-PCIe bridges as roots of PCIe hierarchies

In a struct pcie_link_state, link->root points to the pcie_link_state of the root of the PCIe hierarchy. For the topmost link, this points to itself (link->root = link). For others, we copy the pointer from the parent (link->root = link->parent->root). Previously we recognized that Root Ports

Re: [PATCH 4/9] ila: simplify a strange allocation pattern

On 01/30/2017 10:49 AM, Michal Hocko wrote: From: Michal Hocko alloc_ila_locks seemed to c from alloc_bucket_locks allocation pattern which is quite unusual. The default allocation size is 320 * sizeof(spinlock_t) which is sub page unless lockdep is enabled when the

Re: [PATCH 4/9] ila: simplify a strange allocation pattern

On 01/30/2017 10:49 AM, Michal Hocko wrote: From: Michal Hocko alloc_ila_locks seemed to c from alloc_bucket_locks allocation pattern which is quite unusual. The default allocation size is 320 * sizeof(spinlock_t) which is sub page unless lockdep is enabled when the performance benefit is

Re: [PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu

Hi Ashok, On Fri, Jan 27, 2017 at 08:32:39AM -0800, Ashok Raj wrote: > From: CQ Tang > > Some of the macros are incorrect with wrong bit-shifts resulting in picking > the incorrect invalidation granularity. Incorrect Source-ID in extended > devtlb invalidation caused device

Re: [PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu

Hi Ashok, On Fri, Jan 27, 2017 at 08:32:39AM -0800, Ashok Raj wrote: > From: CQ Tang > > Some of the macros are incorrect with wrong bit-shifts resulting in picking > the incorrect invalidation granularity. Incorrect Source-ID in extended > devtlb invalidation caused device side errors. > >

Re: [PATCH v8] perf: add qcom l2 cache perf events driver

Hi Neil, Apologies for the delay in getting to this. This is largely looking good now. I have a couple of concerns with the hotplug logic, but I think we can solve those without too much pain. More on that below. On Mon, Jan 16, 2017 at 01:52:47PM -0500, Neil Leeder wrote: > +#define

Re: [PATCH 2/8] pinctrl: stm32: use gpio-ranges to declare bank range

On Fri, Jan 27, 2017 at 5:15 PM, Alexandre TORGUE wrote: > Use device tree entries to declare gpio range. It will allow to use > no contiguous gpio bank and holes inside a bank. > > Signed-off-by: Alexandre TORGUE (...) > +

Re: [PATCH 2/8] pinctrl: stm32: use gpio-ranges to declare bank range

On Fri, Jan 27, 2017 at 5:15 PM, Alexandre TORGUE wrote: > Use device tree entries to declare gpio range. It will allow to use > no contiguous gpio bank and holes inside a bank. > > Signed-off-by: Alexandre TORGUE (...) > + of_property_read_string(np, "st,bank-name", >gpio_chip.label); >

Re: [PATCH v8] perf: add qcom l2 cache perf events driver

Hi Neil, Apologies for the delay in getting to this. This is largely looking good now. I have a couple of concerns with the hotplug logic, but I think we can solve those without too much pain. More on that below. On Mon, Jan 16, 2017 at 01:52:47PM -0500, Neil Leeder wrote: > +#define

Re: [PATCH REPOST 2/2] cgroup, perf_event: make perf_event controller work on cgroup2 hierarchy

Hello, On Mon, Jan 30, 2017 at 11:05:41AM -0300, Arnaldo Carvalho de Melo wrote: > > This was posted months ago and acked by Peter. I thought it was > > applied but apparently wasn't. Peter asked Arnaldo whether the > > userspace part looked which didn't get replied and that probably was > >

Re: [PATCH REPOST 2/2] cgroup, perf_event: make perf_event controller work on cgroup2 hierarchy

Hello, On Mon, Jan 30, 2017 at 11:05:41AM -0300, Arnaldo Carvalho de Melo wrote: > > This was posted months ago and acked by Peter. I thought it was > > applied but apparently wasn't. Peter asked Arnaldo whether the > > userspace part looked which didn't get replied and that probably was > >

Re: [PATCH v4 2/2] HWPOISON: soft offlining for non-lru movable page

Hi, Michal, Sorry for late reply. On 01/26/2017 05:27 PM, Michal Hocko wrote: > On Wed 25-01-17 23:05:38, ys...@foxmail.com wrote: >> From: Yisheng Xie >> >> This patch is to extends soft offlining framework to support >> non-lru page, which already support migration

Re: [PATCH v4 2/2] HWPOISON: soft offlining for non-lru movable page

Hi, Michal, Sorry for late reply. On 01/26/2017 05:27 PM, Michal Hocko wrote: > On Wed 25-01-17 23:05:38, ys...@foxmail.com wrote: >> From: Yisheng Xie >> >> This patch is to extends soft offlining framework to support >> non-lru page, which already support migration after >> commit bda807d44454

Re: [PATCH 1/8] pinctrl: stm32: fix bad location of gpiochip_lock_as_irq

On Fri, Jan 27, 2017 at 5:15 PM, Alexandre TORGUE wrote: > Move gpio lock as irq from "domain alloc" callback to "domain activate" > callback. It will allow to use gpiolib sysfs correctly. > > Signed-off-by: Alexandre TORGUE Patch applied.

Re: [PATCH v2 1/9] drivers: pinctrl: add driver for Allwinner H5 SoC

On Thu, Jan 26, 2017 at 4:48 PM, Icenowy Zheng wrote: > Based on the Allwinner H5 datasheet and the pinctrl driver of the > backward-compatible H3 this introduces the pin multiplex assignments for > the H5 SoC. > > H5 introduced some more pin functions (e.g. three more groups

Re: [PATCH 1/8] pinctrl: stm32: fix bad location of gpiochip_lock_as_irq

On Fri, Jan 27, 2017 at 5:15 PM, Alexandre TORGUE wrote: > Move gpio lock as irq from "domain alloc" callback to "domain activate" > callback. It will allow to use gpiolib sysfs correctly. > > Signed-off-by: Alexandre TORGUE Patch applied. Yours, Linus Walleij

Re: [PATCH v2 1/9] drivers: pinctrl: add driver for Allwinner H5 SoC

On Thu, Jan 26, 2017 at 4:48 PM, Icenowy Zheng wrote: > Based on the Allwinner H5 datasheet and the pinctrl driver of the > backward-compatible H3 this introduces the pin multiplex assignments for > the H5 SoC. > > H5 introduced some more pin functions (e.g. three more groups of TS > pins, and

Re: [PATCH v4] add u64 number parser

Hello James, Your commit a317178 2016-12-06 parser: add u64 number parser was merged into v4.10-rc1. Good. I have a very similar function and used for a long time. Here I'd suggest you a tiny optimization based on my version. If you think another value is more apropriate as the size of

Re: [PATCH v4] add u64 number parser

Hello James, Your commit a317178 2016-12-06 parser: add u64 number parser was merged into v4.10-rc1. Good. I have a very similar function and used for a long time. Here I'd suggest you a tiny optimization based on my version. If you think another value is more apropriate as the size of

Re: [PATCH net] net: ethtool: add support for 2500BaseT and 5000BaseT link modes

From: Pavel Belous Date: Sat, 28 Jan 2017 22:53:28 +0300 > This patch introduce support for 2500BaseT and 5000BaseT link modes. > These modes are included in the new IEEE 802.3bz standard. > > Signed-off-by: Pavel Belous Applied.

Re: [PATCH net] net: ethtool: add support for 2500BaseT and 5000BaseT link modes

From: Pavel Belous Date: Sat, 28 Jan 2017 22:53:28 +0300 > This patch introduce support for 2500BaseT and 5000BaseT link modes. > These modes are included in the new IEEE 802.3bz standard. > > Signed-off-by: Pavel Belous Applied.

[PATCH v3] xen,input: try to read screen resolution for xen-kbdfront

Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device. Use the default as fallback only. Signed-off-by: Juergen Gross --- V3: add case of late framebuffer registration (Oleksandr

[PATCH v3] xen,input: try to read screen resolution for xen-kbdfront

Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device. Use the default as fallback only. Signed-off-by: Juergen Gross --- V3: add case of late framebuffer registration (Oleksandr Andrushchenko)

Re: [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

ping On 14.01.2017 17:15, Kirill Tkhai wrote: > For correct checkpointing/restoring of a task from userspace > it's need to know the task's pid_ns_for_children. Currently, > there is no a sane way to do that (the only possible trick > is to force the task create a new child and to analize the >

Re: [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

ping On 14.01.2017 17:15, Kirill Tkhai wrote: > For correct checkpointing/restoring of a task from userspace > it's need to know the task's pid_ns_for_children. Currently, > there is no a sane way to do that (the only possible trick > is to force the task create a new child and to analize the >

Re: [PATCH v2 0/2] drm: Add support for tiny LCD displays

Den 30.01.2017 09.44, skrev Daniel Vetter: Hi Noralf, On Fri, Jan 27, 2017 at 08:56:29PM +0100, Noralf Trønnes wrote: This is an attempt at providing a DRM version of drivers/staging/fbtft. The tinydrm library provides a very simplified view of DRM in particular for tiny displays that has

Re: [PATCH v2 0/2] drm: Add support for tiny LCD displays

Den 30.01.2017 09.44, skrev Daniel Vetter: Hi Noralf, On Fri, Jan 27, 2017 at 08:56:29PM +0100, Noralf Trønnes wrote: This is an attempt at providing a DRM version of drivers/staging/fbtft. The tinydrm library provides a very simplified view of DRM in particular for tiny displays that has

Re: [PATCH] tools/headers: Sync {tools/,}arch/powerpc/include/uapi/asm/kvm.h, {tools/,}arch/x86/include/asm/cpufeatures.h and {tools/,}arch/arm/include/uapi/asm/kvm.h

Em Mon, Jan 30, 2017 at 09:11:31AM +0100, Ingo Molnar escreveu: > > The following upstream headers were updated: > > - The x86 cpufeatures.h file picked up a couple of new feature entries > - The PowerPC and ARM KVM headers picked up new features > > None of which requires changes to perf

Re: [PATCH] tools/headers: Sync {tools/,}arch/powerpc/include/uapi/asm/kvm.h, {tools/,}arch/x86/include/asm/cpufeatures.h and {tools/,}arch/arm/include/uapi/asm/kvm.h

Em Mon, Jan 30, 2017 at 09:11:31AM +0100, Ingo Molnar escreveu: > > The following upstream headers were updated: > > - The x86 cpufeatures.h file picked up a couple of new feature entries > - The PowerPC and ARM KVM headers picked up new features > > None of which requires changes to perf

[PATCH v3 4/4] arm64: dts: msm8996: Add SLPI SMP2P dt node.

Add smp2p support to communicate with slpi processor. Signed-off-by: Avaneesh Kumar Dwivedi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 24 1 file changed, 24 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi

[PATCH v3 4/4] arm64: dts: msm8996: Add SLPI SMP2P dt node.

Add smp2p support to communicate with slpi processor. Signed-off-by: Avaneesh Kumar Dwivedi --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 24 1 file changed, 24 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi

Re: [PATCH 0/8] Add STM32F469 pinctrl and fix issues in STM32 pinctrl

Hi, On 01/27/2017 05:15 PM, Alexandre TORGUE wrote: This series adds support of a dedicated driver for STM32F469 MCU pinctroller. This add generates some changes inside STM32 pinctrl driver and inside STM32 device tree. Changes in STM32 pinctrl driver: ---

[PATCH v3 1/4] remoteproc: qcom: Compatible string based resource initialization.

This patch initialize certain driver related data based on compatible string. This enable driver to handle more than one similar device in by differentiating in probe their private data. Signed-off-by: Avaneesh Kumar Dwivedi --- drivers/remoteproc/qcom_adsp_pil.c | 47

Re: [PATCH 0/8] Add STM32F469 pinctrl and fix issues in STM32 pinctrl

Hi, On 01/27/2017 05:15 PM, Alexandre TORGUE wrote: This series adds support of a dedicated driver for STM32F469 MCU pinctroller. This add generates some changes inside STM32 pinctrl driver and inside STM32 device tree. Changes in STM32 pinctrl driver: ---

[PATCH v3 1/4] remoteproc: qcom: Compatible string based resource initialization.

This patch initialize certain driver related data based on compatible string. This enable driver to handle more than one similar device in by differentiating in probe their private data. Signed-off-by: Avaneesh Kumar Dwivedi --- drivers/remoteproc/qcom_adsp_pil.c | 47

[PATCH v3 3/4] remoteproc: qcom: Add SLPI rproc support to load and boot slpi proc.

This patch add slpi remoteproc support in existing adsp rproc driver. Signed-off-by: Avaneesh Kumar Dwivedi --- .../devicetree/bindings/remoteproc/qcom,adsp.txt | 28 ++ drivers/remoteproc/qcom_adsp_pil.c | 10 +++- 2 files

[PATCH v3 0/4]remoteproc: qcom: Add support for Qualcomm low pass sensor peripheral loader.

This patchset has changed from last patchset in below respect 1- Generic regulator and clock resource handling is dropped. 2- Introdused additional px supply and aggre2 clock initialization. 3- Add SLPI boot support in existing ADSP driver. 4- Address other minor

[PATCH v3 3/4] remoteproc: qcom: Add SLPI rproc support to load and boot slpi proc.

This patch add slpi remoteproc support in existing adsp rproc driver. Signed-off-by: Avaneesh Kumar Dwivedi --- .../devicetree/bindings/remoteproc/qcom,adsp.txt | 28 ++ drivers/remoteproc/qcom_adsp_pil.c | 10 +++- 2 files changed, 37 insertions(+), 1

[PATCH v3 0/4]remoteproc: qcom: Add support for Qualcomm low pass sensor peripheral loader.

This patchset has changed from last patchset in below respect 1- Generic regulator and clock resource handling is dropped. 2- Introdused additional px supply and aggre2 clock initialization. 3- Add SLPI boot support in existing ADSP driver. 4- Address other minor

[PATCH v3 2/4] remoteproc: qcom: Add additional agree2_clk and px regulator resource.

This patch add additional clock and regulator resource which are initialized based on compatible and has no impact on existing driver working. This resourse addition enable the existing driver to handle. low pass sensor processor device also. Signed-off-by: Avaneesh Kumar Dwivedi

[PATCH v3 2/4] remoteproc: qcom: Add additional agree2_clk and px regulator resource.

This patch add additional clock and regulator resource which are initialized based on compatible and has no impact on existing driver working. This resourse addition enable the existing driver to handle. low pass sensor processor device also. Signed-off-by: Avaneesh Kumar Dwivedi ---

Re: [GIT PULL] cputime: Convert core use of cputime_t to nsecs

On Mon, Jan 30, 2017 at 03:32:24PM +0100, Stanislaw Gruszka wrote: > On Mon, Jan 30, 2017 at 05:46:43AM +0100, Frederic Weisbecker wrote: > > Now lets admit one drawback: s390 and powerpc with > > CONFIG_VIRT_CPU_ACCOUNTING_NATIVE have new cputime_t to nsecs conversion > > on cputime accounting

Re: [GIT PULL] cputime: Convert core use of cputime_t to nsecs

On Mon, Jan 30, 2017 at 03:32:24PM +0100, Stanislaw Gruszka wrote: > On Mon, Jan 30, 2017 at 05:46:43AM +0100, Frederic Weisbecker wrote: > > Now lets admit one drawback: s390 and powerpc with > > CONFIG_VIRT_CPU_ACCOUNTING_NATIVE have new cputime_t to nsecs conversion > > on cputime accounting

Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response

On 01/25/2017 06:06 PM, Takashi Iwai wrote: The code path is related with the runtime PM, so it's likely depending on the device state, e.g. long-time pause or such. I don't think Win 10 plays a role, but who knows. In anyway, let me know if this helps. Basically I can merge it even for now,

Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response

On 01/25/2017 06:06 PM, Takashi Iwai wrote: The code path is related with the runtime PM, so it's likely depending on the device state, e.g. long-time pause or such. I don't think Win 10 plays a role, but who knows. In anyway, let me know if this helps. Basically I can merge it even for now,

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim > wrote: > > Now that we maintain the EL1 physical timer register states of VMs, > > update the physical timer interrupt level along with the virtual one. > >

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim > wrote: > > Now that we maintain the EL1 physical timer register states of VMs, > > update the physical timer interrupt level along with the virtual one. > > > > Note that the

Re: [PATCH v4 1/2] mm/migration: make isolate_movable_page always defined

Hi， Michal， Sorry for late reply. On 01/26/2017 05:18 PM, Michal Hocko wrote: > On Wed 25-01-17 23:05:37, ys...@foxmail.com wrote: >> From: Yisheng Xie >> >> Define isolate_movable_page as a static inline function when >> CONFIG_MIGRATION is not enable. It should return

Re: [PATCH v4 1/2] mm/migration: make isolate_movable_page always defined

Hi， Michal， Sorry for late reply. On 01/26/2017 05:18 PM, Michal Hocko wrote: > On Wed 25-01-17 23:05:37, ys...@foxmail.com wrote: >> From: Yisheng Xie >> >> Define isolate_movable_page as a static inline function when >> CONFIG_MIGRATION is not enable. It should return false >> here which means

Re: [PATCH v4 3/7] x86: put msr-index.h in uapi

On Mon, Jan 23, 2017 at 05:52:45PM +0100, Borislav Petkov wrote: > On Mon, Jan 23, 2017 at 03:58:37PM +0100, Nicolas Dichtel wrote: > > This header file is exported, thus move it to uapi. > > Why? Why is this damn thing exported in the first place? > > The moment we decide to change an MSR name

Re: [PATCH v4 3/7] x86: put msr-index.h in uapi

On Mon, Jan 23, 2017 at 05:52:45PM +0100, Borislav Petkov wrote: > On Mon, Jan 23, 2017 at 03:58:37PM +0100, Nicolas Dichtel wrote: > > This header file is exported, thus move it to uapi. > > Why? Why is this damn thing exported in the first place? > > The moment we decide to change an MSR name

Re: [PATCH 10/18] ARM64: dts: meson-gxbb: Reorder nodes

On Mon, Jan 23, 2017 at 10:52:08AM -0600, Rob Herring wrote: > On Fri, Jan 20, 2017 at 11:21:10PM +0100, Andreas Färber wrote: > > Sort nodes referenced by label alphabetically. > > Seems to be pointless churn. Depends - if, as the author of a dts file, I order the nodes alphabetically, and then

Re: [PATCH 10/18] ARM64: dts: meson-gxbb: Reorder nodes

On Mon, Jan 23, 2017 at 10:52:08AM -0600, Rob Herring wrote: > On Fri, Jan 20, 2017 at 11:21:10PM +0100, Andreas Färber wrote: > > Sort nodes referenced by label alphabetically. > > Seems to be pointless churn. Depends - if, as the author of a dts file, I order the nodes alphabetically, and then

Re: [RFC v2 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer

On Sun, Jan 29, 2017 at 12:07:48PM +, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:55 AM, Jintack Lim > wrote: > > Initialize the emulated EL1 physical timer with the default irq number. > > > > Signed-off-by: Jintack Lim > > --- > >

Re: [RFC v2 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer

On Sun, Jan 29, 2017 at 12:07:48PM +, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:55 AM, Jintack Lim > wrote: > > Initialize the emulated EL1 physical timer with the default irq number. > > > > Signed-off-by: Jintack Lim > > --- > > arch/arm/kvm/reset.c | 9 - > >

Re: [PATCH v3 0/2] prctl: make PR_SET_CHILD_SUBREAPER deterministic

please drop it, errors in commit message On 01/30/2017 05:48 PM, Pavel Tikhomirov wrote: Oleg Nesterov (1): introduce the walk_process_tree() helper Pavel Tikhomirov (1): prctl: propagate has_child_subreaper flag to every descendant include/linux/sched.h | 3 +++ kernel/fork.c |

Re: [PATCH v3 0/2] prctl: make PR_SET_CHILD_SUBREAPER deterministic

please drop it, errors in commit message On 01/30/2017 05:48 PM, Pavel Tikhomirov wrote: Oleg Nesterov (1): introduce the walk_process_tree() helper Pavel Tikhomirov (1): prctl: propagate has_child_subreaper flag to every descendant include/linux/sched.h | 3 +++ kernel/fork.c |

Re: [PATCH 1/2] gpio: mcp23s08: use regmap

On Fri, Jan 27, 2017 at 3:47 PM, Sebastian Reichel wrote: > Use regmap API to save some lines of codes and have > debugfs support for all of the MCP's registers. > > Signed-off-by: Sebastian Reichel Patch applied. Irresistible cleanup! Yours, Linus Walleij

Re: [PATCH 1/2] gpio: mcp23s08: use regmap

On Fri, Jan 27, 2017 at 3:47 PM, Sebastian Reichel wrote: > Use regmap API to save some lines of codes and have > debugfs support for all of the MCP's registers. > > Signed-off-by: Sebastian Reichel Patch applied. Irresistible cleanup! Yours, Linus Walleij

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On 30/01/17 14:45, Christoffer Dall wrote: > On Sun, Jan 29, 2017 at 11:54:05AM +, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >> wrote: >>> Make cntvoff per each timer context. This is helpful to abstract kvm >>> timer functions to work

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On 30/01/17 14:45, Christoffer Dall wrote: > On Sun, Jan 29, 2017 at 11:54:05AM +, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >> wrote: >>> Make cntvoff per each timer context. This is helpful to abstract kvm >>> timer functions to work with timer context without

Re: [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled

Hi Bjorn, On Sat, Jan 28, 2017 at 03:17:28PM -0600, Bjorn Helgaas wrote: > On Wed, Jan 11, 2017 at 12:30:55PM -0600, Bjorn Helgaas wrote: > > On Mon, Dec 12, 2016 at 11:30:20AM -0700, Jason Gunthorpe wrote: > > > The PCI core will write to the bridge window config multiple times > > > while they

Re: [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled

Hi Bjorn, On Sat, Jan 28, 2017 at 03:17:28PM -0600, Bjorn Helgaas wrote: > On Wed, Jan 11, 2017 at 12:30:55PM -0600, Bjorn Helgaas wrote: > > On Mon, Dec 12, 2016 at 11:30:20AM -0700, Jason Gunthorpe wrote: > > > The PCI core will write to the bridge window config multiple times > > > while they

[PATCH 5/5] gpio: ws16c48: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the ws16c48_remove function. Now that the ws16c48_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray ---

[PATCH 5/5] gpio: ws16c48: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the ws16c48_remove function. Now that the ws16c48_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-ws16c48.c | 2 -- 1 file

[PATCH 4/5] gpio: gpio-mm: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the gpiomm_remove function. Now that the gpiomm_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-gpio-mm.c

[PATCH 4/5] gpio: gpio-mm: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the gpiomm_remove function. Now that the gpiomm_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-gpio-mm.c | 2 -- 1 file changed,

Re: [PATCHv5 0/5] Support for Marvell switches with integrated CPUs

Hi Chris, On dim., janv. 29 2017, Chris Packham wrote: > On 28/01/17 07:47, Stephen Boyd wrote: >> On 01/27, Gregory CLEMENT wrote: >>> Hi all, >>> >>> On ven., janv. 27 2017, Chris Packham >>> wrote: >>> The

Re: [PATCHv5 0/5] Support for Marvell switches with integrated CPUs

Hi Chris, On dim., janv. 29 2017, Chris Packham wrote: > On 28/01/17 07:47, Stephen Boyd wrote: >> On 01/27, Gregory CLEMENT wrote: >>> Hi all, >>> >>> On ven., janv. 27 2017, Chris Packham >>> wrote: >>> The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Sun, Jan 29, 2017 at 11:54:05AM +, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim > wrote: > > Make cntvoff per each timer context. This is helpful to abstract kvm > > timer functions to work with timer context without considering timer > >

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Sun, Jan 29, 2017 at 11:54:05AM +, Marc Zyngier wrote: > On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim > wrote: > > Make cntvoff per each timer context. This is helpful to abstract kvm > > timer functions to work with timer context without considering timer > > types (e.g. physical

[PATCH 1/2] dts: arm64: add LS1043A DPAA support

Signed-off-by: Madalin Bucur --- arch/arm64/boot/dts/freescale/fsl-ls1043-post.dtsi | 33 +++ arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts | 2 + arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts | 75 +++

[PATCH 1/2] dts: arm64: add LS1043A DPAA support

Signed-off-by: Madalin Bucur --- arch/arm64/boot/dts/freescale/fsl-ls1043-post.dtsi | 33 +++ arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts | 2 + arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts | 75 +++ arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 73

[PATCH 0/2] dts: arm64: add DPAA 1 support for ARM based SoCs

Add DPAA 1 nodes for LS1043A/LS1046A and networking support for RDB and QDS boards with these SoCs. Madalin Bucur (2): dts: arm64: add LS1043A DPAA support dts: arm64: add LS1046A DPAA support arch/arm64/boot/dts/freescale/fsl-ls1043-post.dtsi | 33 +++

[PATCH 0/2] dts: arm64: add DPAA 1 support for ARM based SoCs

Add DPAA 1 nodes for LS1043A/LS1046A and networking support for RDB and QDS boards with these SoCs. Madalin Bucur (2): dts: arm64: add LS1043A DPAA support dts: arm64: add LS1046A DPAA support arch/arm64/boot/dts/freescale/fsl-ls1043-post.dtsi | 33 +++

[PATCH 2/2] dts: arm64: add LS1046A DPAA support

Signed-off-by: Madalin Bucur --- arch/arm64/boot/dts/freescale/fsl-ls1046-post.dtsi | 37 arch/arm64/boot/dts/freescale/fsl-ls1046a-qds.dts | 2 + arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts | 62

[PATCH 2/2] dts: arm64: add LS1046A DPAA support

Signed-off-by: Madalin Bucur --- arch/arm64/boot/dts/freescale/fsl-ls1046-post.dtsi | 37 arch/arm64/boot/dts/freescale/fsl-ls1046a-qds.dts | 2 + arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts | 62 arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 66

[tip:irq/urgent] irqdomain: Avoid activating interrupts more than once

Commit-ID: 08d85f3ea99f1eeafc4e8507936190e86a16ee8c Gitweb: http://git.kernel.org/tip/08d85f3ea99f1eeafc4e8507936190e86a16ee8c Author: Marc Zyngier AuthorDate: Tue, 17 Jan 2017 16:00:48 + Committer: Thomas Gleixner CommitDate: Mon, 30 Jan

[tip:irq/urgent] irqdomain: Avoid activating interrupts more than once

Commit-ID: 08d85f3ea99f1eeafc4e8507936190e86a16ee8c Gitweb: http://git.kernel.org/tip/08d85f3ea99f1eeafc4e8507936190e86a16ee8c Author: Marc Zyngier AuthorDate: Tue, 17 Jan 2017 16:00:48 + Committer: Thomas Gleixner CommitDate: Mon, 30 Jan 2017 15:18:56 +0100 irqdomain: Avoid

RE: ibmvtpm byteswapping inconsistency

From: Tyrel Datwyler > Sent: 27 January 2017 18:03 > On 01/26/2017 05:50 PM, Benjamin Herrenschmidt wrote: > > On Thu, 2017-01-26 at 17:42 -0800, Tyrel Datwyler wrote: > >> On 01/26/2017 12:22 PM, Michal Suchnek wrote: > >>> Hello, > >>> > >>> building ibmvtpm I noticed gcc warning complaining

RE: ibmvtpm byteswapping inconsistency

From: Tyrel Datwyler > Sent: 27 January 2017 18:03 > On 01/26/2017 05:50 PM, Benjamin Herrenschmidt wrote: > > On Thu, 2017-01-26 at 17:42 -0800, Tyrel Datwyler wrote: > >> On 01/26/2017 12:22 PM, Michal Suchnek wrote: > >>> Hello, > >>> > >>> building ibmvtpm I noticed gcc warning complaining

[PATCH 3/5] Documentation: dt: iio: document stm32 exti trigger

Add dt documentation for st,stm32-exti-trigger. EXTi gpio signal can be routed internally as trigger source for various IPs (e.g. for ADC or DAC conversions). Signed-off-by: Fabrice Gasnier --- .../bindings/iio/trigger/st,stm32-exti-trigger.txt | 17

[PATCH 3/5] Documentation: dt: iio: document stm32 exti trigger

Add dt documentation for st,stm32-exti-trigger. EXTi gpio signal can be routed internally as trigger source for various IPs (e.g. for ADC or DAC conversions). Signed-off-by: Fabrice Gasnier --- .../bindings/iio/trigger/st,stm32-exti-trigger.txt | 17 + 1 file changed, 17

[PATCH 3/5] gpio: 104-idio-16: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the idio_16_remove function. Now that the idio_16_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray ---

[PATCH 3/5] gpio: 104-idio-16: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the idio_16_remove function. Now that the idio_16_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-idio-16.c | 2 -- 1 file

[PATCH 2/5] gpio: 104-idi-48: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the idi_48_remove function. Now that the idi_48_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray ---

[PATCH 2/5] gpio: 104-idi-48: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the idi_48_remove function. Now that the idi_48_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-idi-48.c | 2 -- 1 file

[PATCH 1/5] gpio: 104-dio-48e: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the dio48e_remove function. Now that the dio48e_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray ---

[PATCH 1/5] gpio: 104-dio-48e: Remove unnecessary driver_data set

Setting driver_data was necessary to access private data in the dio48e_remove function. Now that the dio48e_remove function is gone, driver_data is no longer used. This patch removes the relevant code. Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-dio-48e.c | 2 -- 1 file

[PATCH 0/5] gpio: Remove unnecessary driver_data set operations

In a previous patchset ("gpio: Utilize devm_ functions in driver probe callbacks") the device remove functions for several drivers were removed as no longer necessary due to the patchset changes within. Setting driver_data had been necessary in these drivers in order to access private data in the

[PATCH 0/5] gpio: Remove unnecessary driver_data set operations

In a previous patchset ("gpio: Utilize devm_ functions in driver probe callbacks") the device remove functions for several drivers were removed as no longer necessary due to the patchset changes within. Setting driver_data had been necessary in these drivers in order to access private data in the

[PATCH v2 1/5] Documentation: dt: iio: document stm32 adc trigger polarity

STM32 ADC trigger polarity can be set to either rising, falling or both edges. Allow to configure it from dt. Signed-off-by: Fabrice Gasnier --- Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH v2 1/5] Documentation: dt: iio: document stm32 adc trigger polarity

STM32 ADC trigger polarity can be set to either rising, falling or both edges. Allow to configure it from dt. Signed-off-by: Fabrice Gasnier --- Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git

<    9   10   11   12   13   14   15   16   17   18   >