Re: [PATCH v7 2/2] perf/core: add mux switch to skip to the current CPU's events list on mux interrupt

On 23.08.2017 14:54, Alexander Shishkin wrote: > Alexey Budankov writes: > >> This patch implements mux switch that triggers skipping to the >> current CPU's events list at mulitplexing hrtimer interrupt >> handler as well as adoption of the switch in the

Re: [PATCH v7 2/2] perf/core: add mux switch to skip to the current CPU's events list on mux interrupt

On 23.08.2017 14:54, Alexander Shishkin wrote: > Alexey Budankov writes: > >> This patch implements mux switch that triggers skipping to the >> current CPU's events list at mulitplexing hrtimer interrupt >> handler as well as adoption of the switch in the existing >> implementation. >> >>

Re: [PATCH] c6x: Convert to using %pOF instead of full_name

On Wed, Jul 19, 2017 at 12:42 PM, Mark Salter wrote: > On Tue, 2017-07-18 at 16:42 -0500, Rob Herring wrote: >> Now that we have a custom printf format specifier, convert users of >> full_name to use %pOF instead. This is preparation to remove storing >> of the full path

Re: [PATCH] c6x: Convert to using %pOF instead of full_name

On Wed, Jul 19, 2017 at 12:42 PM, Mark Salter wrote: > On Tue, 2017-07-18 at 16:42 -0500, Rob Herring wrote: >> Now that we have a custom printf format specifier, convert users of >> full_name to use %pOF instead. This is preparation to remove storing >> of the full path string for each node. >>

[PATCH] input/xen-kbdfront: Enable auto repeat for xen keyboard frontend driver

Long pressed key could not show right in XEN vncviewer after tigervnc client changed the way how to send repeat keys, from "Down Up Down Up ..." to "Down Down ... Up". By enable EV_REP bit here, XEN keyboard device will trigger default auto repeat process from input subsystem, and make auto repeat

[PATCH] input/xen-kbdfront: Enable auto repeat for xen keyboard frontend driver

Long pressed key could not show right in XEN vncviewer after tigervnc client changed the way how to send repeat keys, from "Down Up Down Up ..." to "Down Down ... Up". By enable EV_REP bit here, XEN keyboard device will trigger default auto repeat process from input subsystem, and make auto repeat

Re: Re: [PATCH] devfreq: Convert to using %pOF instead of full_name

On Thu, Jul 20, 2017 at 12:25 AM, MyungJoo Ham wrote: >> On 2017년 07월 19일 06:42, Rob Herring wrote: >> > Now that we have a custom printf format specifier, convert users of >> > full_name to use %pOF instead. This is preparation to remove storing >> > of the full path

Re: Re: [PATCH] devfreq: Convert to using %pOF instead of full_name

On Thu, Jul 20, 2017 at 12:25 AM, MyungJoo Ham wrote: >> On 2017년 07월 19일 06:42, Rob Herring wrote: >> > Now that we have a custom printf format specifier, convert users of >> > full_name to use %pOF instead. This is preparation to remove storing >> > of the full path string for each node. >> >

RE: [Patch v2 13/19] CIFS: SMBD: Use registered memory RDMA read for SMB write

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Wednesday, August 23, 2017 6:52 AM > To: Long Li > Cc: Steve French ; linux-c...@vger.kernel.org; samba- > techni...@lists.samba.org; linux-kernel@vger.kernel.org;

RE: [Patch v2 13/19] CIFS: SMBD: Use registered memory RDMA read for SMB write

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Wednesday, August 23, 2017 6:52 AM > To: Long Li > Cc: Steve French ; linux-c...@vger.kernel.org; samba- > techni...@lists.samba.org; linux-kernel@vger.kernel.org; linux- > r...@vger.kernel.org; Christoph

Re: Stable apply request

From: Jiri Slaby Date: Wed, 23 Aug 2017 09:29:44 +0200 > On 06/27/2017, 07:32 PM, Marcel Holtmann wrote: >>> It looks like bnep_session has same pattern as the issue reported in >>> old rfcomm: >>> >>> while (1) { >>> set_current_state(TASK_INTERRUPTIBLE); >>>

Re: Stable apply request

From: Jiri Slaby Date: Wed, 23 Aug 2017 09:29:44 +0200 > On 06/27/2017, 07:32 PM, Marcel Holtmann wrote: >>> It looks like bnep_session has same pattern as the issue reported in >>> old rfcomm: >>> >>> while (1) { >>> set_current_state(TASK_INTERRUPTIBLE); >>> if

Re: [v5 2/4] mm, oom: cgroup-aware OOM killer

On Wed, Aug 23, 2017 at 01:24:41PM -0400, Johannes Weiner wrote: > Hi, > > On Wed, Aug 23, 2017 at 05:20:31PM +0100, Roman Gushchin wrote: > > On Tue, Aug 22, 2017 at 01:03:44PM -0400, Johannes Weiner wrote: > > > > + css_task_iter_start(>css, 0, ); > > > > + while ((task =

Re: [v5 2/4] mm, oom: cgroup-aware OOM killer

On Wed, Aug 23, 2017 at 01:24:41PM -0400, Johannes Weiner wrote: > Hi, > > On Wed, Aug 23, 2017 at 05:20:31PM +0100, Roman Gushchin wrote: > > On Tue, Aug 22, 2017 at 01:03:44PM -0400, Johannes Weiner wrote: > > > > + css_task_iter_start(>css, 0, ); > > > > + while ((task =

Re: [patch v5 1/3] drivers: jtag: Add JTAG core driver

Hi Oleksandr, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc6 next-20170823] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Oleksandr-Shamray/JTAG-driver

Re: [patch v5 1/3] drivers: jtag: Add JTAG core driver

Hi Oleksandr, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc6 next-20170823] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Oleksandr-Shamray/JTAG-driver

[PATCH v1 1/1] mm: Reversed logic in memblock_discard

In recently introduced memblock_discard() there is a reversed logic bug. Memory is freed of static array instead of dynamically allocated one. Fixes: 3010f876500f ("mm: discard memblock data later") Reported-and-tested-by: Woody Suwalski Signed-off-by: Pavel Tatashin

[PATCH v1 1/1] mm: Reversed logic in memblock_discard

In recently introduced memblock_discard() there is a reversed logic bug. Memory is freed of static array instead of dynamically allocated one. Fixes: 3010f876500f ("mm: discard memblock data later") Reported-and-tested-by: Woody Suwalski Signed-off-by: Pavel Tatashin --- mm/memblock.c | 2 +-

[PATCH v1 0/1] Reversed logic in memblock_discard

One line fix for reversed logic where static array is freed instead of allocated one Pavel Tatashin (1): mm: Reversed logic in memblock_discard mm/memblock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.14.1

[PATCH v1 0/1] Reversed logic in memblock_discard

One line fix for reversed logic where static array is freed instead of allocated one Pavel Tatashin (1): mm: Reversed logic in memblock_discard mm/memblock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.14.1

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

On Wed, Aug 23, 2017 at 09:32:06PM +0530, Oza Oza wrote: > On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya wrote: > > Hi Oza, > > > >> In working Enumuration case I get following: > >> [9.125976] pci :00:00.0: bridge configuration invalid ([bus > >> 00-00]),

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

On Wed, Aug 23, 2017 at 09:32:06PM +0530, Oza Oza wrote: > On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya wrote: > > Hi Oza, > > > >> In working Enumuration case I get following: > >> [9.125976] pci :00:00.0: bridge configuration invalid ([bus > >> 00-00]), re-configuring > >> [9.134267]

[PATCH] Arm: mm: ftrace: Only set text back to ro after kernel has been marked ro

ftrace needs to modify the kernel text in order to enable function tracing. For security reasons, the kernel text is marked to read-only (ro) at the end of system bootup. When enabling function tracing after that, ftrace calls arch specific code that needs to enable the modification of kernel

[PATCH] Arm: mm: ftrace: Only set text back to ro after kernel has been marked ro

ftrace needs to modify the kernel text in order to enable function tracing. For security reasons, the kernel text is marked to read-only (ro) at the end of system bootup. When enabling function tracing after that, ftrace calls arch specific code that needs to enable the modification of kernel

Re: [PATCH 2/2] fpga: altera-cvp: register attribute groups using ops

On Tue, Aug 22, 2017 at 3:23 PM, Alan Tull wrote: > On Tue, Aug 22, 2017 at 10:53 AM, Alan Tull wrote: On second thought, this patch is probably not really helpful as it changes the path of the existing sysfs file from /sys/bus/pci/drivers/altera-cvp/chkcfg

Re: [PATCH 2/2] fpga: altera-cvp: register attribute groups using ops

On Tue, Aug 22, 2017 at 3:23 PM, Alan Tull wrote: > On Tue, Aug 22, 2017 at 10:53 AM, Alan Tull wrote: On second thought, this patch is probably not really helpful as it changes the path of the existing sysfs file from /sys/bus/pci/drivers/altera-cvp/chkcfg to

Re: [PATCH v3 1/3] lockdep: Make LOCKDEP_CROSSRELEASE configs all part of PROVE_LOCKING

On Wed, Aug 23, 2017 at 06:39:03PM +0200, Oleg Nesterov wrote: > Peter, I am all confused and I am still trying to understand your email. > In particular, because I no longer understand the lockdep annotations in > workqueue.c, it turns out I forgot everything... Yeah, that happens :/ > On

Re: [PATCH v3 1/3] lockdep: Make LOCKDEP_CROSSRELEASE configs all part of PROVE_LOCKING

On Wed, Aug 23, 2017 at 06:39:03PM +0200, Oleg Nesterov wrote: > Peter, I am all confused and I am still trying to understand your email. > In particular, because I no longer understand the lockdep annotations in > workqueue.c, it turns out I forgot everything... Yeah, that happens :/ > On

Re: [PATCH v2] ARM: vdso: Define vdso_{start,end} as array

Arnd Bergmann writes: > gcc-8 correctly points out that reading four bytes from a pointer to a > 'char' variable is wrong > > arch/arm/kernel/vdso.c: In function 'vdso_init': > arch/arm/kernel/vdso.c:200:6: error: '__builtin_memcmp_eq' reading 4 bytes > from a region of size 1

Re: [PATCH v2] ARM: vdso: Define vdso_{start,end} as array

Arnd Bergmann writes: > gcc-8 correctly points out that reading four bytes from a pointer to a > 'char' variable is wrong > > arch/arm/kernel/vdso.c: In function 'vdso_init': > arch/arm/kernel/vdso.c:200:6: error: '__builtin_memcmp_eq' reading 4 bytes > from a region of size 1

Re: [RESEND PATCH 1/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts

Hello, Thank you very much for the tips. I have updated the documentation and schematics of our web site. I also tried to implement all other fixes, but seems that I cannot file the git you are talking about. The patches i sent were done to:

Re: [RESEND PATCH 1/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts

Hello, Thank you very much for the tips. I have updated the documentation and schematics of our web site. I also tried to implement all other fixes, but seems that I cannot file the git you are talking about. The patches i sent were done to:

Re: [PATCH v2 08/19] perf, tools: Expression parser enhancements for metrics

On Fri, Aug 11, 2017 at 04:26:23PM -0700, Andi Kleen wrote: > From: Andi Kleen > > Enhance the expression parser for more complex metric formulas. > > - Support python style IF ELSE operators > - Add an #SMT_On magic variable for formulas that depend on the SMT > status. >

Re: [PATCH v2 08/19] perf, tools: Expression parser enhancements for metrics

On Fri, Aug 11, 2017 at 04:26:23PM -0700, Andi Kleen wrote: > From: Andi Kleen > > Enhance the expression parser for more complex metric formulas. > > - Support python style IF ELSE operators > - Add an #SMT_On magic variable for formulas that depend on the SMT > status. > > Example: 4 *(

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > Not all devices with ACPI and this combination of sound devices will > > have the required information provided via ACPI.  Reintroduce the I2C > > device ID to restore sound

Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs

On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote: > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote: > > Not all devices with ACPI and this combination of sound devices will > > have the required information provided via ACPI.  Reintroduce the I2C > > device ID to restore sound

Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

2017-08-24 0:51 GMT+08:00 Andy Lutomirski : > To avoid further wasting time solving this wrong: NAK. pt_regs is the actual > interrupted state, not some oddly sanitized version thereof. NMI isn't even > the only way you can have a weird pt_regs like this. > > It seems that

Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

2017-08-24 0:51 GMT+08:00 Andy Lutomirski : > To avoid further wasting time solving this wrong: NAK. pt_regs is the actual > interrupted state, not some oddly sanitized version thereof. NMI isn't even > the only way you can have a weird pt_regs like this. > > It seems that some older kernels

[PATCH] ALSA: aaci: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/arm/aaci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/arm/aaci.c

[PATCH] ALSA: aaci: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/arm/aaci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/arm/aaci.c b/sound/arm/aaci.c index

Re: [PATCH v2 1/2] fault-inject: Restore support for task-independent fault injection

On Wed, 2017-08-23 at 09:10 +0900, Akinobu Mita wrote: > 2017-08-23 8:00 GMT+09:00 Bart Van Assche : > > Certain faults should be injected independent of the context > > in which these occur. Commit e41d58185f14 made it impossible to > > inject faults independent of their

Re: [PATCH v2 1/2] fault-inject: Restore support for task-independent fault injection

On Wed, 2017-08-23 at 09:10 +0900, Akinobu Mita wrote: > 2017-08-23 8:00 GMT+09:00 Bart Van Assche : > > Certain faults should be injected independent of the context > > in which these occur. Commit e41d58185f14 made it impossible to > > inject faults independent of their context. Restore support

[PATCH v2] fbdev: vgastate: fix line over 80 character and remove unnecessary space

Fixes the following checkpatch warnings: WARNING: line over 80 characters WARNING: space prohibited between function name and open parenthesis '(' WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable Signed-off-by: Himanshu Jha ---

[PATCH v2] fbdev: vgastate: fix line over 80 character and remove unnecessary space

Fixes the following checkpatch warnings: WARNING: line over 80 characters WARNING: space prohibited between function name and open parenthesis '(' WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable Signed-off-by: Himanshu Jha --- drivers/video/vgastate.c | 10

Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

2017-08-23 23:20 GMT+08:00 Josh Poimboeuf : > On Wed, Aug 23, 2017 at 10:19:02PM +0800, oliver yang wrote: >> 2017-08-23 1:51 GMT+08:00 Josh Poimboeuf : >> > On Tue, Aug 22, 2017 at 05:09:19PM +, yang oliver wrote: >> >> From: Yong Yang

Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

2017-08-23 23:20 GMT+08:00 Josh Poimboeuf : > On Wed, Aug 23, 2017 at 10:19:02PM +0800, oliver yang wrote: >> 2017-08-23 1:51 GMT+08:00 Josh Poimboeuf : >> > On Tue, Aug 22, 2017 at 05:09:19PM +, yang oliver wrote: >> >> From: Yong Yang >> >> >> >> While NMI interrupts the very beginning of

Re: [PATCH 2/2] mmc: sdhci-msm: Enable delay circuit calibration clocks

On Tue 22 Aug 03:45 PDT 2017, Ulf Hansson wrote: > [...] > > > diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c > > index 71e01cbc38b6..7b47906ba447 100644 > > --- a/drivers/mmc/host/sdhci-msm.c > > +++ b/drivers/mmc/host/sdhci-msm.c > > @@ -131,7 +131,7 @@ struct

Re: [PATCH 2/2] mmc: sdhci-msm: Enable delay circuit calibration clocks

On Tue 22 Aug 03:45 PDT 2017, Ulf Hansson wrote: > [...] > > > diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c > > index 71e01cbc38b6..7b47906ba447 100644 > > --- a/drivers/mmc/host/sdhci-msm.c > > +++ b/drivers/mmc/host/sdhci-msm.c > > @@ -131,7 +131,7 @@ struct

[PATCH] video: ARM CLCD: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/video/fbdev/amba-clcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] video: ARM CLCD: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/video/fbdev/amba-clcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/amba-clcd.c

Re: [v5 2/4] mm, oom: cgroup-aware OOM killer

Hi, On Wed, Aug 23, 2017 at 05:20:31PM +0100, Roman Gushchin wrote: > On Tue, Aug 22, 2017 at 01:03:44PM -0400, Johannes Weiner wrote: > > > + css_task_iter_start(>css, 0, ); > > > + while ((task = css_task_iter_next())) { > > > + /* > > > + * If there are no tasks, or all tasks

Re: [v5 2/4] mm, oom: cgroup-aware OOM killer

Hi, On Wed, Aug 23, 2017 at 05:20:31PM +0100, Roman Gushchin wrote: > On Tue, Aug 22, 2017 at 01:03:44PM -0400, Johannes Weiner wrote: > > > + css_task_iter_start(>css, 0, ); > > > + while ((task = css_task_iter_next())) { > > > + /* > > > + * If there are no tasks, or all tasks

[PATCH v7 2/5] dt-bindings: List devicetree binding for the CCU of Allwinner A20

Allwinner A20 is now driven by sunxi-ng CCU driver. Add devicetree binding for it. Acked-by: Rob Herring Reviewed-by: Chen-Yu Tsai Signed-off-by: Priit Laes --- Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 + 1 file changed, 1

[PATCH v7 2/5] dt-bindings: List devicetree binding for the CCU of Allwinner A20

Allwinner A20 is now driven by sunxi-ng CCU driver. Add devicetree binding for it. Acked-by: Rob Herring Reviewed-by: Chen-Yu Tsai Signed-off-by: Priit Laes --- Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v7 5/5] ARM: sun4i: Convert to CCU

Convert sun4i-a10.dtsi to new CCU driver. Tested on Gemei G9 tablet. Signed-off-by: Priit Laes --- arch/arm/boot/dts/sun4i-a10.dtsi | 646 +++- 1 file changed, 73 insertions(+), 573 deletions(-) diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi

[PATCH v7 5/5] ARM: sun4i: Convert to CCU

Convert sun4i-a10.dtsi to new CCU driver. Tested on Gemei G9 tablet. Signed-off-by: Priit Laes --- arch/arm/boot/dts/sun4i-a10.dtsi | 646 +++- 1 file changed, 73 insertions(+), 573 deletions(-) diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi

[PATCH v7 4/5] ARM: sun7i: Convert to CCU

Convert sun7i-a20.dtsi to new CCU driver. Tested on Cubietruck. Signed-off-by: Priit Laes --- arch/arm/boot/dts/sun7i-a20.dtsi | 719 +++- 1 file changed, 84 insertions(+), 635 deletions(-) diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi

[PATCH v7 4/5] ARM: sun7i: Convert to CCU

Convert sun7i-a20.dtsi to new CCU driver. Tested on Cubietruck. Signed-off-by: Priit Laes --- arch/arm/boot/dts/sun7i-a20.dtsi | 719 +++- 1 file changed, 84 insertions(+), 635 deletions(-) diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi

[PATCH v7 0/5] ARM: sunxi: Convert sun4i/sun7i series SoCs to sunxi-ng CCU

Hi, This serie brings A10 (sun4i) and A20 (sun7i) SoCs into the sunxi-ng world. With this patchset we now support all the clocks in sun4i/sun7i SoCs. In order to make cross-tree merges bisectable, changes to device trees are currently using clock index as numbers instead of defines. Changes

[PATCH v7 0/5] ARM: sunxi: Convert sun4i/sun7i series SoCs to sunxi-ng CCU

Hi, This serie brings A10 (sun4i) and A20 (sun7i) SoCs into the sunxi-ng world. With this patchset we now support all the clocks in sun4i/sun7i SoCs. In order to make cross-tree merges bisectable, changes to device trees are currently using clock index as numbers instead of defines. Changes

[PATCH v7 1/5] clk: sunxi-ng: Add sun4i/sun7i CCU driver

Introduce a clock controller driver for sun4i A10 and sun7i A20 series SoCs. Signed-off-by: Priit Laes --- drivers/clk/sunxi-ng/Kconfig | 13 +- drivers/clk/sunxi-ng/Makefile |1 +- drivers/clk/sunxi-ng/ccu-sun4i-a10.c | 1456

[PATCH v7 1/5] clk: sunxi-ng: Add sun4i/sun7i CCU driver

Introduce a clock controller driver for sun4i A10 and sun7i A20 series SoCs. Signed-off-by: Priit Laes --- drivers/clk/sunxi-ng/Kconfig | 13 +- drivers/clk/sunxi-ng/Makefile |1 +- drivers/clk/sunxi-ng/ccu-sun4i-a10.c | 1456 ++-

[PATCH v7 3/5] dt-bindings: List devicetree binding for the CCU of Allwinner A10

Allwinner A10 is now driven by sunxi-ng CCU driver. Add devicetree binding for it. Acked-by: Rob Herring Reviewed-by: Chen-Yu Tsai Signed-off-by: Priit Laes --- Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 + 1 file changed, 1

[PATCH v7 3/5] dt-bindings: List devicetree binding for the CCU of Allwinner A10

Allwinner A10 is now driven by sunxi-ng CCU driver. Add devicetree binding for it. Acked-by: Rob Herring Reviewed-by: Chen-Yu Tsai Signed-off-by: Priit Laes --- Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH v7 1/2] perf/core: use rb trees for pinned/flexible groups

On 23.08.2017 14:17, Alexander Shishkin wrote: > Alexey Budankov writes: > >> @@ -3091,61 +3231,55 @@ static void cpu_ctx_sched_out(struct >> perf_cpu_context *cpuctx, >> } >> >> static void >> -ctx_pinned_sched_in(struct perf_event_context *ctx, >> -

Re: [PATCH v7 1/2] perf/core: use rb trees for pinned/flexible groups

On 23.08.2017 14:17, Alexander Shishkin wrote: > Alexey Budankov writes: > >> @@ -3091,61 +3231,55 @@ static void cpu_ctx_sched_out(struct >> perf_cpu_context *cpuctx, >> } >> >> static void >> -ctx_pinned_sched_in(struct perf_event_context *ctx, >> -struct perf_cpu_context

[PATCH] i2c: nomadik: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/i2c/busses/i2c-nomadik.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] i2c: nomadik: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/i2c/busses/i2c-nomadik.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/i2c/busses/i2c-nomadik.c

[PATCH] vfio: platform: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/vfio/platform/vfio_amba.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] vfio: platform: constify amba_id

amba_id are not supposed to change at runtime. All functions working with const amba_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/vfio/platform/vfio_amba.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 0/2] net: Fix crashes due to activity during suspend

On 08/23/2017 04:45 AM, Geert Uytterhoeven wrote: > Hi Florian, > > On Tue, Aug 22, 2017 at 8:49 PM, Florian Fainelli > wrote: >> On 08/22/2017 11:37 AM, Geert Uytterhoeven wrote: >>> If an Ethernet device is used while the device is suspended, the system may >>> crash.

Re: [PATCH 0/2] net: Fix crashes due to activity during suspend

On 08/23/2017 04:45 AM, Geert Uytterhoeven wrote: > Hi Florian, > > On Tue, Aug 22, 2017 at 8:49 PM, Florian Fainelli > wrote: >> On 08/22/2017 11:37 AM, Geert Uytterhoeven wrote: >>> If an Ethernet device is used while the device is suspended, the system may >>> crash. >>> >>> E.g. on

Re: [kernel-hardening] [PATCH v5 04/10] arm64: Add __flush_tlb_one()

On Wed, Aug 23, 2017 at 06:04:43PM +0100, Mark Rutland wrote: > On Wed, Aug 23, 2017 at 10:58:42AM -0600, Tycho Andersen wrote: > > Hi Mark, > > > > On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote: > > > That said, is there any reason not to use flush_tlb_kernel_range() > > >

Re: [kernel-hardening] [PATCH v5 04/10] arm64: Add __flush_tlb_one()

On Wed, Aug 23, 2017 at 06:04:43PM +0100, Mark Rutland wrote: > On Wed, Aug 23, 2017 at 10:58:42AM -0600, Tycho Andersen wrote: > > Hi Mark, > > > > On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote: > > > That said, is there any reason not to use flush_tlb_kernel_range() > > >

Re: [PATCH net] sctp: Avoid out-of-bounds reads from address storage

On Wed, Aug 23, 2017 at 01:27:13PM +0200, Stefano Brivio wrote: > inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() copy > sizeof(sockaddr_storage) bytes to fill in sockaddr structs used > to export diagnostic information to userspace. > > However, the memory allocated to store sockaddr

Re: [PATCH net] sctp: Avoid out-of-bounds reads from address storage

On Wed, Aug 23, 2017 at 01:27:13PM +0200, Stefano Brivio wrote: > inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() copy > sizeof(sockaddr_storage) bytes to fill in sockaddr structs used > to export diagnostic information to userspace. > > However, the memory allocated to store sockaddr

Upgrade Your Email Account.

Dear,Email Account User, We are closing down some Email Accounts due to recent spamming activities and no upgrade/no update on the Accounts kindly confirm your Email Account Active to avoid closing your Email Account. Please kindly click on the link http://www.smartsurvey.co.uk/s/P70AE/ and

Upgrade Your Email Account.

Dear,Email Account User, We are closing down some Email Accounts due to recent spamming activities and no upgrade/no update on the Accounts kindly confirm your Email Account Active to avoid closing your Email Account. Please kindly click on the link http://www.smartsurvey.co.uk/s/P70AE/ and

Re: [GIT PULL] workqueue fixes for v4.13-rc3

Hello, Geert. On Wed, Aug 23, 2017 at 04:47:41PM +0200, Geert Uytterhoeven wrote: > Some code is mixing up multiple memory nodes with multiple cpu nodes. > M68k uses DISCONTIGMEM, but not NUMA (no SMP): > > config NEED_MULTIPLE_NODES > def_bool y > depends on DISCONTIGMEM ||

Re: [GIT PULL] workqueue fixes for v4.13-rc3

Hello, Geert. On Wed, Aug 23, 2017 at 04:47:41PM +0200, Geert Uytterhoeven wrote: > Some code is mixing up multiple memory nodes with multiple cpu nodes. > M68k uses DISCONTIGMEM, but not NUMA (no SMP): > > config NEED_MULTIPLE_NODES > def_bool y > depends on DISCONTIGMEM ||

Re: [kernel-hardening] [PATCH v5 04/10] arm64: Add __flush_tlb_one()

On Wed, Aug 23, 2017 at 10:58:42AM -0600, Tycho Andersen wrote: > Hi Mark, > > On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote: > > That said, is there any reason not to use flush_tlb_kernel_range() > > directly? > > So it turns out that there is a difference between

Re: [kernel-hardening] [PATCH v5 04/10] arm64: Add __flush_tlb_one()

On Wed, Aug 23, 2017 at 10:58:42AM -0600, Tycho Andersen wrote: > Hi Mark, > > On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote: > > That said, is there any reason not to use flush_tlb_kernel_range() > > directly? > > So it turns out that there is a difference between

Re: [PATCH v2 1/1] cavium: Add firmware for CNN55XX crypto driver.

On Fri, Jun 23, 2017 at 04:22:54PM +0530, Srikanth Jampala wrote: > This patchset adds the firmware for CNN55XX cryto driver, > supports Symmetric crypto operations. > > The version of the firmware is v07. > > Signed-off-by: Srikanth Jampala applied, sorry for the

Re: [PATCH v2 1/1] cavium: Add firmware for CNN55XX crypto driver.

On Fri, Jun 23, 2017 at 04:22:54PM +0530, Srikanth Jampala wrote: > This patchset adds the firmware for CNN55XX cryto driver, > supports Symmetric crypto operations. > > The version of the firmware is v07. > > Signed-off-by: Srikanth Jampala applied, sorry for the delay, i was on holidays.

Re: [PATCH V6] perf: Add PERF_SAMPLE_PHYS_ADDR

On Wed, Aug 23, 2017 at 7:39 AM, Peter Zijlstra wrote: > On Wed, Aug 23, 2017 at 04:33:08PM +0200, Peter Zijlstra wrote: >> > @@ -6145,6 +6183,9 @@ void perf_prepare_sample(struct perf_event_header >> > *header, >> > >> > header->size += size; >> > } >> > +

Re: [PATCH V6] perf: Add PERF_SAMPLE_PHYS_ADDR

On Wed, Aug 23, 2017 at 7:39 AM, Peter Zijlstra wrote: > On Wed, Aug 23, 2017 at 04:33:08PM +0200, Peter Zijlstra wrote: >> > @@ -6145,6 +6183,9 @@ void perf_prepare_sample(struct perf_event_header >> > *header, >> > >> > header->size += size; >> > } >> > + >> > + if

Re: [kernel-hardening] [PATCH v5 04/10] arm64: Add __flush_tlb_one()

Hi Mark, On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote: > That said, is there any reason not to use flush_tlb_kernel_range() > directly? So it turns out that there is a difference between __flush_tlb_one() and flush_tlb_kernel_range() on x86: flush_tlb_kernel_range() flushes all

Re: [kernel-hardening] [PATCH v5 04/10] arm64: Add __flush_tlb_one()

Hi Mark, On Mon, Aug 14, 2017 at 05:50:47PM +0100, Mark Rutland wrote: > That said, is there any reason not to use flush_tlb_kernel_range() > directly? So it turns out that there is a difference between __flush_tlb_one() and flush_tlb_kernel_range() on x86: flush_tlb_kernel_range() flushes all

[v6 0/4] cgroup-aware OOM killer

This patchset makes the OOM killer cgroup-aware. v6: - Renamed oom_control.chosen to oom_control.chosen_task - Renamed oom_kill_all_tasks to oom_kill_all - Per-node NR_SLAB_UNRECLAIMABLE accounting - Several minor fixes and cleanups - Docs updated v5: - Rebased on top of Michal

[v6 0/4] cgroup-aware OOM killer

This patchset makes the OOM killer cgroup-aware. v6: - Renamed oom_control.chosen to oom_control.chosen_task - Renamed oom_kill_all_tasks to oom_kill_all - Per-node NR_SLAB_UNRECLAIMABLE accounting - Several minor fixes and cleanups - Docs updated v5: - Rebased on top of Michal

[v6 4/4] mm, oom, docs: describe the cgroup-aware OOM killer

Update cgroups v2 docs. Signed-off-by: Roman Gushchin Cc: Michal Hocko Cc: Vladimir Davydov Cc: Johannes Weiner Cc: Tetsuo Handa Cc: David Rientjes Cc: Tejun

[v6 4/4] mm, oom, docs: describe the cgroup-aware OOM killer

Update cgroups v2 docs. Signed-off-by: Roman Gushchin Cc: Michal Hocko Cc: Vladimir Davydov Cc: Johannes Weiner Cc: Tetsuo Handa Cc: David Rientjes Cc: Tejun Heo Cc: kernel-t...@fb.com Cc: cgro...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc:

[v6 2/4] mm, oom: cgroup-aware OOM killer

Traditionally, the OOM killer is operating on a process level. Under oom conditions, it finds a process with the highest oom score and kills it. This behavior doesn't suit well the system with many running containers: 1) There is no fairness between containers. A small container with few large

[v6 2/4] mm, oom: cgroup-aware OOM killer

Traditionally, the OOM killer is operating on a process level. Under oom conditions, it finds a process with the highest oom score and kills it. This behavior doesn't suit well the system with many running containers: 1) There is no fairness between containers. A small container with few large

[v6 1/4] mm, oom: refactor the oom_kill_process() function

The oom_kill_process() function consists of two logical parts: the first one is responsible for considering task's children as a potential victim and printing the debug information. The second half is responsible for sending SIGKILL to all tasks sharing the mm struct with the given victim. This

[v6 1/4] mm, oom: refactor the oom_kill_process() function

The oom_kill_process() function consists of two logical parts: the first one is responsible for considering task's children as a potential victim and printing the debug information. The second half is responsible for sending SIGKILL to all tasks sharing the mm struct with the given victim. This

[v6 3/4] mm, oom: introduce oom_priority for memory cgroups

Introduce a per-memory-cgroup oom_priority setting: an integer number within the [-1, 1] range, which defines the order in which the OOM killer selects victim memory cgroups. OOM killer prefers memory cgroups with larger priority if they are populated with eligible tasks. The

[v6 3/4] mm, oom: introduce oom_priority for memory cgroups

Introduce a per-memory-cgroup oom_priority setting: an integer number within the [-1, 1] range, which defines the order in which the OOM killer selects victim memory cgroups. OOM killer prefers memory cgroups with larger priority if they are populated with eligible tasks. The

Re: [PATCH 2/2] tracing: Fix kmemleak in set_trigger_filter

On Wed, 23 Aug 2017 10:41:55 -0400 Steven Rostedt wrote: > * On success, returns 0 and *@filterp points to the new filter. On > * failure, returns -errno and *@filterp may point to %NULL or to a new > * filter. In the latter case, the returned filter contains error > *

Re: [PATCH 2/2] tracing: Fix kmemleak in set_trigger_filter

On Wed, 23 Aug 2017 10:41:55 -0400 Steven Rostedt wrote: > * On success, returns 0 and *@filterp points to the new filter. On > * failure, returns -errno and *@filterp may point to %NULL or to a new > * filter. In the latter case, the returned filter contains error > * information if

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