Re: [PATCH v3 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack

* Peter Ujfalusi [160603 06:10]: > On 06/03/16 14:03, Peter Ujfalusi wrote: > > > > I have prepared two branches on top of v4.7-rc1: > > [1] https://github.com/omap-audio/linux-audio.git > > peter/for-4.8_omapdss_part1 > > > > containing: > > ARM: OMAP: rx51-video: Do

Re: [PATCH] dmaengine: do not allow access outside of unmap_pool

On Tue, May 17, 2016 at 01:00:46PM +0100, Colin King wrote: > From: Colin Ian King > > When CONFIG_DMA_ENGINE_RAID is defined, unmap_pool[] is just 1 > element in size, however, allows orders of 2..8 to access > outside unmap_pool and returns an invalid address. Ensure

Re: [PATCH v3 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack

* Peter Ujfalusi [160603 06:10]: > On 06/03/16 14:03, Peter Ujfalusi wrote: > > > > I have prepared two branches on top of v4.7-rc1: > > [1] https://github.com/omap-audio/linux-audio.git > > peter/for-4.8_omapdss_part1 > > > > containing: > > ARM: OMAP: rx51-video: Do not set TV

Re: [PATCH] dmaengine: do not allow access outside of unmap_pool

On Tue, May 17, 2016 at 01:00:46PM +0100, Colin King wrote: > From: Colin Ian King > > When CONFIG_DMA_ENGINE_RAID is defined, unmap_pool[] is just 1 > element in size, however, allows orders of 2..8 to access > outside unmap_pool and returns an invalid address. Ensure > we fall into the default

[ANNOUNCE] Git v2.9.0-rc2

A release candidate Git v2.9.0-rc2 is now available for testing at the usual places. It is comprised of 477 non-merge commits since v2.8.0, contributed by 67 people, 27 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/testing/ The following

[ANNOUNCE] Git v2.8.4

The latest maintenance release Git v2.8.4 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.8.4' tag and the 'maint' branch that the tag points at: url =

[ANNOUNCE] Git v2.9.0-rc2

A release candidate Git v2.9.0-rc2 is now available for testing at the usual places. It is comprised of 477 non-merge commits since v2.8.0, contributed by 67 people, 27 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/testing/ The following

[ANNOUNCE] Git v2.8.4

The latest maintenance release Git v2.8.4 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.8.4' tag and the 'maint' branch that the tag points at: url =

[PATCH v2] cpu/hotplug: handle unbalanced hotplug enable/disable

Currently it just print a warning message but did not reset cpu_hotplug_disabled when the enable/disable is unbalanced. The unbalanced enable/disable will lead the cpu hotplug work abnormally. Do nothing if an unablanced hotplug enable detected. Signed-off-by: Lianwei Wang

[PATCH v2] cpu/hotplug: handle unbalanced hotplug enable/disable

Currently it just print a warning message but did not reset cpu_hotplug_disabled when the enable/disable is unbalanced. The unbalanced enable/disable will lead the cpu hotplug work abnormally. Do nothing if an unablanced hotplug enable detected. Signed-off-by: Lianwei Wang --- kernel/cpu.c |

Re: [PATCH v2 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack

* Tomi Valkeinen [160603 03:53]: > > > On 02/06/16 18:23, Tony Lindgren wrote: > > * Tomi Valkeinen [160602 05:28]: > >> > >> Tony, can you have a look at the arch/arm parts here and give your ack > >> if they're fine? They should be quite small

Re: [PATCH v2 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack

* Tomi Valkeinen [160603 03:53]: > > > On 02/06/16 18:23, Tony Lindgren wrote: > > * Tomi Valkeinen [160602 05:28]: > >> > >> Tony, can you have a look at the arch/arm parts here and give your ack > >> if they're fine? They should be quite small and display specific, so I > >> don't see much

Re: [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids table

On Mon, 6 Jun 2016 22:31:38 +0200 Boris Brezillon wrote: > On Mon, 6 Jun 2016 22:59:03 +0300 > Aleksei Mamlin wrote: > > > On Mon, 6 Jun 2016 20:55:49 +0200 > > Boris Brezillon wrote: > > > > > On

Re: [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids table

On Mon, 6 Jun 2016 22:31:38 +0200 Boris Brezillon wrote: > On Mon, 6 Jun 2016 22:59:03 +0300 > Aleksei Mamlin wrote: > > > On Mon, 6 Jun 2016 20:55:49 +0200 > > Boris Brezillon wrote: > > > > > On Mon, 6 Jun 2016 13:24:22 +0300 > > > Aleksei Mamlin wrote: > > > > > > > Add the full

Re: [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids table

On Tue, 7 Jun 2016 00:06:45 +0300 Aleksei Mamlin wrote: > On Mon, 6 Jun 2016 22:31:38 +0200 > Boris Brezillon wrote: > > > On Mon, 6 Jun 2016 22:59:03 +0300 > > Aleksei Mamlin wrote: > > > > > On Mon, 6 Jun 2016

Re: [PATCH 5/7] mtd: nand: Add Hynix H27UBG8T2BTR-BC to nand_ids table

On Tue, 7 Jun 2016 00:06:45 +0300 Aleksei Mamlin wrote: > On Mon, 6 Jun 2016 22:31:38 +0200 > Boris Brezillon wrote: > > > On Mon, 6 Jun 2016 22:59:03 +0300 > > Aleksei Mamlin wrote: > > > > > On Mon, 6 Jun 2016 20:55:49 +0200 > > > Boris Brezillon wrote: > > > > > > > On Mon, 6 Jun

Re: [PATCH v1] PM / sleep: make pm notifier called symmetrically

On Wed, May 18, 2016 at 11:06 PM, Lianwei Wang wrote: > On Wed, May 18, 2016 at 1:34 PM, Rafael J. Wysocki wrote: >> On Wed, May 18, 2016 at 8:07 AM, Lianwei Wang wrote: >>> This makes pm notifier PREPARE/POST symmetrical: if

Re: [PATCH v1] PM / sleep: make pm notifier called symmetrically

On Wed, May 18, 2016 at 11:06 PM, Lianwei Wang wrote: > On Wed, May 18, 2016 at 1:34 PM, Rafael J. Wysocki wrote: >> On Wed, May 18, 2016 at 8:07 AM, Lianwei Wang wrote: >>> This makes pm notifier PREPARE/POST symmetrical: if PREPARE >>> fails, we will only undo what ever happened on PREPARE.

Re: [PATCH] cpu/hotplug: handle unbalanced hotplug enable/disable

On Thu, May 12, 2016 at 1:06 AM, Lianwei Wang wrote: > I have come up a patch to make the pm notifier called symmetrically > and currently being tested. I will send it out after pass the test. > > On Fri, May 6, 2016 at 12:18 AM, Thomas Gleixner wrote:

Re: [PATCH] cpu/hotplug: handle unbalanced hotplug enable/disable

On Thu, May 12, 2016 at 1:06 AM, Lianwei Wang wrote: > I have come up a patch to make the pm notifier called symmetrically > and currently being tested. I will send it out after pass the test. > > On Fri, May 6, 2016 at 12:18 AM, Thomas Gleixner wrote: >> On Fri, 6 May 2016, Lianwei Wang wrote:

Re: [PATCH] dmaengine: dmatest: Add support for scatter-gather DMA mode

On Mon, Apr 25, 2016 at 02:18:05PM +0530, Kedareswara rao Appana wrote: > This patch updates the dmatest client to support > scatter-gather dma mode. > > Signed-off-by: Kedareswara rao Appana > --- > drivers/dma/dmatest.c | 38 -- > 1 file

Re: [PATCH] dmaengine: dmatest: Add support for scatter-gather DMA mode

On Mon, Apr 25, 2016 at 02:18:05PM +0530, Kedareswara rao Appana wrote: > This patch updates the dmatest client to support > scatter-gather dma mode. > > Signed-off-by: Kedareswara rao Appana > --- > drivers/dma/dmatest.c | 38 -- > 1 file changed, 36

Re: powerpc/nvram: Fix an incorrect partition merge

xinhui writes: >> Has it always been broken? >> > > no. after nvram partition corruption hit, all nvram partitions will be > erased and re-alloc after the second machine reboot. > I don't know who does it but i guess it is the firmware. :) It is. PAPR says we

Re: powerpc/nvram: Fix an incorrect partition merge

xinhui writes: >> Has it always been broken? >> > > no. after nvram partition corruption hit, all nvram partitions will be > erased and re-alloc after the second machine reboot. > I don't know who does it but i guess it is the firmware. :) It is. PAPR says we format NVRAM when it's corrupted.

Re: [PATCH] iio: light: tcs3472: use iio helper function to guarantee direct mode

On Mon, 6 Jun 2016, Alison Schofield wrote: > Replace the code that guarantees the device stays in direct mode > with iio_device_claim_direct_mode() which does same. This allows > removal of an unused lock in the device private global data. Acked-by: Peter Meerwald-Stadler

Re: [PATCH] iio: light: tcs3472: use iio helper function to guarantee direct mode

On Mon, 6 Jun 2016, Alison Schofield wrote: > Replace the code that guarantees the device stays in direct mode > with iio_device_claim_direct_mode() which does same. This allows > removal of an unused lock in the device private global data. Acked-by: Peter Meerwald-Stadler > Signed-off-by:

[PATCH net-next v2 4/4] arm64: bpf: optimize LD_ABS, LD_IND

Remove superfluous stack frame, saving us 3 instructions for every LD_ABS or LD_IND. Signed-off-by: Zi Shen Lim --- arch/arm64/net/bpf_jit_comp.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/arm64/net/bpf_jit_comp.c index

[PATCH net-next v2 1/4] bpf: fix missing header inclusion

Commit 0fc174dea545 ("ebpf: make internal bpf API independent of CONFIG_BPF_SYSCALL ifdefs") introduced usage of ERR_PTR() in bpf_prog_get(), however did not include linux/err.h. Without this patch, when compiling arm64 BPF without CONFIG_BPF_SYSCALL: ... In file included from

[PATCH net-next v2 4/4] arm64: bpf: optimize LD_ABS, LD_IND

Remove superfluous stack frame, saving us 3 instructions for every LD_ABS or LD_IND. Signed-off-by: Zi Shen Lim --- arch/arm64/net/bpf_jit_comp.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/arm64/net/bpf_jit_comp.c index 7ae304e..b2fc97a 100644 ---

[PATCH net-next v2 1/4] bpf: fix missing header inclusion

Commit 0fc174dea545 ("ebpf: make internal bpf API independent of CONFIG_BPF_SYSCALL ifdefs") introduced usage of ERR_PTR() in bpf_prog_get(), however did not include linux/err.h. Without this patch, when compiling arm64 BPF without CONFIG_BPF_SYSCALL: ... In file included from

Re: [PATCH] iio: light: isl29125: use iio helper function to guarantee direct mode

> Replace the code that guarantees the device stays in direct mode > with iio_device_claim_direct_mode() which does same. This allows > removal of an unused lock in the device private global data. nice! Acked-by: Peter Meerwald-Stadler > Signed-off-by: Alison Schofield

Re: [PATCH] iio: light: isl29125: use iio helper function to guarantee direct mode

> Replace the code that guarantees the device stays in direct mode > with iio_device_claim_direct_mode() which does same. This allows > removal of an unused lock in the device private global data. nice! Acked-by: Peter Meerwald-Stadler > Signed-off-by: Alison Schofield > Cc: Daniel Baluta >

[PATCH net-next v2 0/4] arm64 BPF JIT updates

Updates for arm64 eBPF JIT. The main addition here is implementation of bpf_tail_call. #1: Fix missing header inclusion in linux/bpf.h. #2: Add bpf_tail_call for arm64. #3,4: Optimizations to reduce instruction count for jitted code. Changes since v1: - Added patch #1 to address build error due

[PATCH net-next v2 3/4] arm64: bpf: optimize JMP_CALL

Remove superfluous stack frame, saving us 3 instructions for every JMP_CALL. Signed-off-by: Zi Shen Lim --- arch/arm64/net/bpf_jit_comp.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/arm64/net/bpf_jit_comp.c index

Re: [PATCH] iio: light: tcs3414: use iio helper function to guarantee direct mode

> Replace the code that guarantees the device stays in direct mode > with iio_device_claim_direct_mode() which does same. This allows > removal of an unused lock in the device private global data. Acked-by: Peter Meerwald-Stadler > Signed-off-by: Alison Schofield

[PATCH net-next v2 0/4] arm64 BPF JIT updates

Updates for arm64 eBPF JIT. The main addition here is implementation of bpf_tail_call. #1: Fix missing header inclusion in linux/bpf.h. #2: Add bpf_tail_call for arm64. #3,4: Optimizations to reduce instruction count for jitted code. Changes since v1: - Added patch #1 to address build error due

[PATCH net-next v2 3/4] arm64: bpf: optimize JMP_CALL

Remove superfluous stack frame, saving us 3 instructions for every JMP_CALL. Signed-off-by: Zi Shen Lim --- arch/arm64/net/bpf_jit_comp.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/arm64/net/bpf_jit_comp.c index 51abc97..7ae304e 100644 ---

Re: [PATCH] iio: light: tcs3414: use iio helper function to guarantee direct mode

> Replace the code that guarantees the device stays in direct mode > with iio_device_claim_direct_mode() which does same. This allows > removal of an unused lock in the device private global data. Acked-by: Peter Meerwald-Stadler > Signed-off-by: Alison Schofield > Cc: Daniel Baluta > ---

Re: [PATCH] dmaengine: dmatest: Add support for scatter-gather DMA mode

On Mon, Apr 25, 2016 at 02:01:59PM +, Ramon Fried wrote: > Wow. Thanks a lot ! care to give tested-by ? -- ~Vinod

Re: [PATCH] dmaengine: dmatest: Add support for scatter-gather DMA mode

On Mon, Apr 25, 2016 at 02:01:59PM +, Ramon Fried wrote: > Wow. Thanks a lot ! care to give tested-by ? -- ~Vinod

Re: [PATCH 3.10 000/143] 3.10.102-stable review

On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: > > > Do you have a repository, either with the patch > > > series or with the to-be-tested branch, where the builder could > > > pick it up ? > > > > I don't but I can set something up for you. Would you be OK with a > > branch in my

Re: [PATCH 3.10 000/143] 3.10.102-stable review

On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: > > > Do you have a repository, either with the patch > > > series or with the to-be-tested branch, where the builder could > > > pick it up ? > > > > I don't but I can set something up for you. Would you be OK with a > > branch in my

[PATCH] kbuild: do not append NOSTDINC_FLAGS to avoid rebuild in package targets

For package building, the scripts/package/Makefile invokes "$(MAKE) KBUILD_SRC=", so the top Makefile is invoked recursively. Notice NOSTDINC_FLAGS is exported and assigned with "+=", not ":=". It means, NOSTDINC_FLAGS is accumulated in the call loop of package build: top Makefile ->

[PATCH] kbuild: do not append NOSTDINC_FLAGS to avoid rebuild in package targets

For package building, the scripts/package/Makefile invokes "$(MAKE) KBUILD_SRC=", so the top Makefile is invoked recursively. Notice NOSTDINC_FLAGS is exported and assigned with "+=", not ":=". It means, NOSTDINC_FLAGS is accumulated in the call loop of package build: top Makefile ->

Re: [PATCH] dmaengine: bcm2835: Fix polling for completion of DMA with interrupts masked.

On Mon, Jun 06, 2016 at 10:33:18AM -0700, Eric Anholt wrote: > Vinod Koul writes: > > > On Fri, Jun 03, 2016 at 07:29:11PM -0700, Eric Anholt wrote: > >> The tx_status hook is supposed to be safe to call from interrupt > >> context, but it wouldn't ever return completion

Re: [PATCH] dmaengine: bcm2835: Fix polling for completion of DMA with interrupts masked.

On Mon, Jun 06, 2016 at 10:33:18AM -0700, Eric Anholt wrote: > Vinod Koul writes: > > > On Fri, Jun 03, 2016 at 07:29:11PM -0700, Eric Anholt wrote: > >> The tx_status hook is supposed to be safe to call from interrupt > >> context, but it wouldn't ever return completion for the last transfer, >

Re: linux-next: Tree for Jun 6 (mm/slub.c)

On 06/05/16 21:20, Stephen Rothwell wrote: > Hi all, > > Changes since 20160603: > on i386: mm/built-in.o: In function `init_cache_random_seq': slub.c:(.text+0x76921): undefined reference to `cache_random_seq_create' mm/built-in.o: In function `__kmem_cache_release': (.text+0x80525): undefined

Re: linux-next: Tree for Jun 6 (mm/slub.c)

On 06/05/16 21:20, Stephen Rothwell wrote: > Hi all, > > Changes since 20160603: > on i386: mm/built-in.o: In function `init_cache_random_seq': slub.c:(.text+0x76921): undefined reference to `cache_random_seq_create' mm/built-in.o: In function `__kmem_cache_release': (.text+0x80525): undefined

[PATCH] iio: light: tcs3472: use iio helper function to guarantee direct mode

Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. This allows removal of an unused lock in the device private global data. Signed-off-by: Alison Schofield Cc: Daniel Baluta ---

[PATCH] iio: light: tcs3472: use iio helper function to guarantee direct mode

Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. This allows removal of an unused lock in the device private global data. Signed-off-by: Alison Schofield Cc: Daniel Baluta --- drivers/iio/light/tcs3472.c | 13 +

[PATCH] iio: light: tcs3414: use iio helper function to guarantee direct mode

Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. This allows removal of an unused lock in the device private global data. Signed-off-by: Alison Schofield Cc: Daniel Baluta ---

[PATCH] iio: light: tcs3414: use iio helper function to guarantee direct mode

Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. This allows removal of an unused lock in the device private global data. Signed-off-by: Alison Schofield Cc: Daniel Baluta --- drivers/iio/light/tcs3414.c | 12 +--- 1

[PATCH] iio: light: isl29125: use iio helper function to guarantee direct mode

Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. This allows removal of an unused lock in the device private global data. Signed-off-by: Alison Schofield Cc: Daniel Baluta ---

[PATCH] iio: light: isl29125: use iio helper function to guarantee direct mode

Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. This allows removal of an unused lock in the device private global data. Signed-off-by: Alison Schofield Cc: Daniel Baluta --- drivers/iio/light/isl29125.c | 10 -- 1

linux-next: Tree for Jun 7

Hi all, Changes since 20160606: New tree: bcm2835 Removed trees: devicetree, devicetree-current (maintainer change) bcm2835-dt, bcm2835-soc, bcm2835-drivers, bcm2835-defconfig (merged into bcm2835 tree) Renamed tree: dt-rh to devicetree Dropped tree: amlogic (build

linux-next: Tree for Jun 7

Hi all, Changes since 20160606: New tree: bcm2835 Removed trees: devicetree, devicetree-current (maintainer change) bcm2835-dt, bcm2835-soc, bcm2835-drivers, bcm2835-defconfig (merged into bcm2835 tree) Renamed tree: dt-rh to devicetree Dropped tree: amlogic (build

[PATCH v2 4/4] arm64: dts: rockchip: add rktimer device node for rk3399

From: Huang Tao Select rktimer0 as broadcast timer. Signed-off-by: Huang Tao Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: Heiko Stuebner Tested-by: Jianqun Xu

[PATCH v2 4/4] arm64: dts: rockchip: add rktimer device node for rk3399

From: Huang Tao Select rktimer0 as broadcast timer. Signed-off-by: Huang Tao Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: Heiko Stuebner Tested-by: Jianqun Xu Signed-off-by: Caesar Wang --- Changes in v2: - %s/ARM64/arm64. arch/arm64/boot/dts/rockchip/rk3399.dtsi | 8 1 file

[PATCH v2 2/4] clocksource: rockchip: add dynamic irq flag to the timer

From: "Huang, Tao" The rockchip timer is broadcast timer. Add CLOCK_EVT_FEAT_DYNIRQ flag and set cpumask to all possible cpus to save power by avoid unnecessary wakeups and IPIs. Signed-off-by: Huang Tao Cc: Daniel Lezcano

[PATCH v2 2/4] clocksource: rockchip: add dynamic irq flag to the timer

From: "Huang, Tao" The rockchip timer is broadcast timer. Add CLOCK_EVT_FEAT_DYNIRQ flag and set cpumask to all possible cpus to save power by avoid unnecessary wakeups and IPIs. Signed-off-by: Huang Tao Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: Heiko Stuebner Tested-by: Jianqun Xu

[PATCH v2 3/4] clocksource: rockchip: add support for rk3399 SoC

From: "Huang, Tao" The CONTROL register offset is different from old SoCs. For Linux driver, there are not functional changes at all. So add dedicated mapping for the CONTROL register. Signed-off-by: Huang Tao Cc: Daniel Lezcano

[PATCH v2 1/4] dt-bindings: document rk3399 rk-timer bindings

From: Huang Tao Add compatible string for rk3399 because which timer is a little different from older SoCs. So rename the file name from rockchip,rk3288-timer.txt to rockchip,rk-timer.txt. Clarify rockchip,rk3288-timer supported SoCs. Signed-off-by: Huang Tao

[PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399

This series patches had been tested on rockchip inside kernel. In order to support the rk3399 SoC timer and turn off interrupts and IPIs to save power in idle. Okay, it still works bootup on rk3288/other SoCs, even though many socs hasn't used the broadcast timer. History version: v1:

[PATCH v2 3/4] clocksource: rockchip: add support for rk3399 SoC

From: "Huang, Tao" The CONTROL register offset is different from old SoCs. For Linux driver, there are not functional changes at all. So add dedicated mapping for the CONTROL register. Signed-off-by: Huang Tao Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: Heiko Stuebner Tested-by: Jianqun Xu

[PATCH v2 1/4] dt-bindings: document rk3399 rk-timer bindings

From: Huang Tao Add compatible string for rk3399 because which timer is a little different from older SoCs. So rename the file name from rockchip,rk3288-timer.txt to rockchip,rk-timer.txt. Clarify rockchip,rk3288-timer supported SoCs. Signed-off-by: Huang Tao Cc: Rob Herring Cc: Daniel

[PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399

This series patches had been tested on rockchip inside kernel. In order to support the rk3399 SoC timer and turn off interrupts and IPIs to save power in idle. Okay, it still works bootup on rk3288/other SoCs, even though many socs hasn't used the broadcast timer. History version: v1:

Re: [PATCH V2] block: correctly fallback for zeroout

On Mon, Jun 06, 2016 at 03:33:58PM -0700, Shaohua Li wrote: > blkdev_issue_zeroout try discard/writesame first, if they fail, zeroout > fallback to regular write. The problem is discard/writesame doesn't > return error for -EOPNOTSUPP, then zeroout can't do fallback and leave > disk data not

Re: [PATCH V2] block: correctly fallback for zeroout

On Mon, Jun 06, 2016 at 03:33:58PM -0700, Shaohua Li wrote: > blkdev_issue_zeroout try discard/writesame first, if they fail, zeroout > fallback to regular write. The problem is discard/writesame doesn't > return error for -EOPNOTSUPP, then zeroout can't do fallback and leave > disk data not

Re: [LKP] [lkp] [mm] 795ae7a0de: pixz.throughput -9.1% regression

On Mon, Jun 06, 2016 at 04:53:07PM +0800, Ye Xiaolong wrote: >On Fri, Jun 03, 2016 at 06:21:09PM -0400, Johannes Weiner wrote: >>On Thu, Jun 02, 2016 at 12:07:06PM -0400, Johannes Weiner wrote: >>> Hi, >>> >>> On Thu, Jun 02, 2016 at 02:45:07PM +0800, kernel test robot wrote: >>> > FYI, we

Re: [LKP] [lkp] [mm] 795ae7a0de: pixz.throughput -9.1% regression

On Mon, Jun 06, 2016 at 04:53:07PM +0800, Ye Xiaolong wrote: >On Fri, Jun 03, 2016 at 06:21:09PM -0400, Johannes Weiner wrote: >>On Thu, Jun 02, 2016 at 12:07:06PM -0400, Johannes Weiner wrote: >>> Hi, >>> >>> On Thu, Jun 02, 2016 at 02:45:07PM +0800, kernel test robot wrote: >>> > FYI, we

RE: Re: Re: Re: [PATCH] usb: core: fix a double free in the usb driver

>On Fri, 3 Jun 2016, Chung-Geol Kim wrote: > >> Yes, you are right, The presentational errors in order to obtain an >> understanding of the process. >> Therefore, I will be happy to explain again the diagrammatic representation >> as shown below. >> If using usb 3.0 storage(OTG), you can see as

RE: Re: Re: Re: [PATCH] usb: core: fix a double free in the usb driver

>On Fri, 3 Jun 2016, Chung-Geol Kim wrote: > >> Yes, you are right, The presentational errors in order to obtain an >> understanding of the process. >> Therefore, I will be happy to explain again the diagrammatic representation >> as shown below. >> If using usb 3.0 storage(OTG), you can see as

Re: [PATCH net-next 2/3] arm64: bpf: optimize JMP_CALL

Hi Will, On Mon, Jun 6, 2016 at 10:05 AM, Will Deacon wrote: > On Sat, Jun 04, 2016 at 03:00:29PM -0700, Zi Shen Lim wrote: >> Remove superfluous stack frame, saving us 3 instructions for >> every JMP_CALL. >> >> Signed-off-by: Zi Shen Lim >> --- >>

Re: [PATCH net-next 2/3] arm64: bpf: optimize JMP_CALL

Hi Will, On Mon, Jun 6, 2016 at 10:05 AM, Will Deacon wrote: > On Sat, Jun 04, 2016 at 03:00:29PM -0700, Zi Shen Lim wrote: >> Remove superfluous stack frame, saving us 3 instructions for >> every JMP_CALL. >> >> Signed-off-by: Zi Shen Lim >> --- >> arch/arm64/net/bpf_jit_comp.c | 3 --- >> 1

Re: [PATCH 3.10 000/143] 3.10.102-stable review

Hi Willy, On 06/06/2016 09:09 PM, Willy Tarreau wrote: Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: The whole patch series can be found in one patch at :

Re: [PATCH 3.10 000/143] 3.10.102-stable review

Hi Willy, On 06/06/2016 09:09 PM, Willy Tarreau wrote: Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: The whole patch series can be found in one patch at :

Re: [PATCH] ARM: Keystone: Introduce Kconfig option to compile in typical Keystone features

* Nishanth Menon [160601 15:51]: > On 06/01/2016 05:31 PM, Arnd Bergmann wrote: > > On Wednesday, June 1, 2016 4:31:54 PM CEST Nishanth Menon wrote: > >> > >> Hence the "KEYSTONE_TYPICAL" option is designed similar to commit > >> 8d9166b519fd > >> ("omap2/3/4: Add Kconfig option to

Re: [PATCH] ARM: Keystone: Introduce Kconfig option to compile in typical Keystone features

* Nishanth Menon [160601 15:51]: > On 06/01/2016 05:31 PM, Arnd Bergmann wrote: > > On Wednesday, June 1, 2016 4:31:54 PM CEST Nishanth Menon wrote: > >> > >> Hence the "KEYSTONE_TYPICAL" option is designed similar to commit > >> 8d9166b519fd > >> ("omap2/3/4: Add Kconfig option to compile in

Re: [PATCH V3 8/9] cpufreq: Keep policy->freq_table sorted in ascending order

On 06-06-16, 23:56, Rafael J. Wysocki wrote: > Since you are adding new code, you can write it so it doesn't do > unnecessary checks from the start. Hmm, I will do all that in this series only now. > While at it, the "if ((freq < policy->min) || (freq > policy->max))" > checks in

Re: [PATCH V3 8/9] cpufreq: Keep policy->freq_table sorted in ascending order

On 06-06-16, 23:56, Rafael J. Wysocki wrote: > Since you are adding new code, you can write it so it doesn't do > unnecessary checks from the start. Hmm, I will do all that in this series only now. > While at it, the "if ((freq < policy->min) || (freq > policy->max))" > checks in

[patch rfc] locking/rwsem: Add down_write_killable/killable_nested()

v4.7 added down_write_killable/killable_nested(), add them to -rt. Signed-off-by: Mike Galbraith --- include/linux/rwsem_rt.h | 12 kernel/locking/rt.c | 24 2 files changed, 36 insertions(+) --- a/include/linux/rwsem_rt.h +++

[patch rfc] locking/rwsem: Add down_write_killable/killable_nested()

v4.7 added down_write_killable/killable_nested(), add them to -rt. Signed-off-by: Mike Galbraith --- include/linux/rwsem_rt.h | 12 kernel/locking/rt.c | 24 2 files changed, 36 insertions(+) --- a/include/linux/rwsem_rt.h +++

Re: [PATCH 3.10 000/143] 3.10.102-stable review

Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: > On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: > > The whole patch series can be found in one patch at : > > > > https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz > > > >

Re: [PATCH 3.10 000/143] 3.10.102-stable review

Hi Guenter, On Mon, Jun 06, 2016 at 08:46:57PM -0700, Guenter Roeck wrote: > On Sun, Jun 05, 2016 at 12:18:23PM +0200, Willy Tarreau wrote: > > The whole patch series can be found in one patch at : > > > > https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.102-rc1.gz > > > >

Re: [PATCH 4.4 00/99] 4.4.13-stable review

On 06/05/2016 02:40 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.13 release. There are 99 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.4 00/99] 4.4.13-stable review

On 06/05/2016 02:40 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.13 release. There are 99 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch")

On 06/06/2016 11:12 AM, Catalin Marinas wrote: On Mon, Jun 06, 2016 at 04:13:34PM +0200, Christoph Hellwig wrote: I've got a few reports of this over the weekend, but it still doesn't make much sense to me. Could it be that kmemleak can't deal with the bio_batch logic? I've tried to look at

Re: kmemleak report after 9082e87bfbf8 ("block: remove struct bio_batch")

On 06/06/2016 11:12 AM, Catalin Marinas wrote: On Mon, Jun 06, 2016 at 04:13:34PM +0200, Christoph Hellwig wrote: I've got a few reports of this over the weekend, but it still doesn't make much sense to me. Could it be that kmemleak can't deal with the bio_batch logic? I've tried to look at

Re: [PATCH V3 1/2] thermal: max77620: Add DT binding doc for thermal driver

On Monday 06 June 2016 05:14 PM, Laxman Dewangan wrote: Maxim Semiconductor MAX77620 supports alarm interrupts when its die temperature crosses 120C and 140C. These threshold temperatures are not configurable. Add DT binding document to details out the DT property related to MAX77620 thermal

Re: [PATCH V3 1/2] thermal: max77620: Add DT binding doc for thermal driver

On Monday 06 June 2016 05:14 PM, Laxman Dewangan wrote: Maxim Semiconductor MAX77620 supports alarm interrupts when its die temperature crosses 120C and 140C. These threshold temperatures are not configurable. Add DT binding document to details out the DT property related to MAX77620 thermal

[PATCH] perf tools: Fix crash in build_id_cache__kallsyms_path()

build_id_cache__kallsyms_path() accept string buffer but also alloc buffer by itself using asnprintf. Unfortunately, the only user of it passes it a stack-allocated buffer. Freeing it causes crash like this: $ perf script *** Error in `/home/wangnan/perf': free(): invalid pointer:

[PATCH] perf tools: Fix crash in build_id_cache__kallsyms_path()

build_id_cache__kallsyms_path() accept string buffer but also alloc buffer by itself using asnprintf. Unfortunately, the only user of it passes it a stack-allocated buffer. Freeing it causes crash like this: $ perf script *** Error in `/home/wangnan/perf': free(): invalid pointer:

Re: [PATCH v13 04/10] arm64: Blacklist non-kprobe-able symbol

On 06/03/2016 11:40 PM, Masami Hiramatsu wrote: Hi David, On Thu, 2 Jun 2016 23:26:18 -0400 David Long wrote: From: Pratyush Anand Add all function symbols which are called from do_debug_exception under NOKPROBE_SYMBOL, as they can not kprobed. I

Re: [PATCH v13 04/10] arm64: Blacklist non-kprobe-able symbol

On 06/03/2016 11:40 PM, Masami Hiramatsu wrote: Hi David, On Thu, 2 Jun 2016 23:26:18 -0400 David Long wrote: From: Pratyush Anand Add all function symbols which are called from do_debug_exception under NOKPROBE_SYMBOL, as they can not kprobed. I see, but this patch should be applied

Re: [PATCH 08/14] drm/amdgpu: use drm_crtc_vblank_{get,put}()

On 06.06.2016 23:41, Gustavo Padovan wrote: > From: Gustavo Padovan > > Replace the legacy drm_vblank_{get,put}() with the new helper functions. > > Signed-off-by: Gustavo Padovan [...] > @@ -268,7 +268,7 @@ int

Re: [PATCH 08/14] drm/amdgpu: use drm_crtc_vblank_{get,put}()

On 06.06.2016 23:41, Gustavo Padovan wrote: > From: Gustavo Padovan > > Replace the legacy drm_vblank_{get,put}() with the new helper functions. > > Signed-off-by: Gustavo Padovan [...] > @@ -268,7 +268,7 @@ int amdgpu_crtc_page_flip(struct drm_crtc *crtc, > return 0; > >

[PATCH 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48

From: Magnus Damm Bump up the maximum numbers of micro-TLBS to 48. Each IPMMU device instance get micro-TLB assignment via the "iommus" property in DT. Older SoCs tend to use a maximum number of 32 micro-TLBd per IPMMU instance however newer SoCs such as r8a7796 make

[PATCH 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48

From: Magnus Damm Bump up the maximum numbers of micro-TLBS to 48. Each IPMMU device instance get micro-TLB assignment via the "iommus" property in DT. Older SoCs tend to use a maximum number of 32 micro-TLBd per IPMMU instance however newer SoCs such as r8a7796 make use of up to 48 micro-TLBs.

[PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code

From: Magnus Damm Support the r8a7796 IPMMU by sharing feature flags between r8a7795 and r8a7796. Also update IOMMU_OF_DECLARE to hook up the updated compat string. Signed-off-by: Magnus Damm --- drivers/iommu/ipmmu-vmsa.c |9

[PATCH 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code

From: Magnus Damm Support the r8a7796 IPMMU by sharing feature flags between r8a7795 and r8a7796. Also update IOMMU_OF_DECLARE to hook up the updated compat string. Signed-off-by: Magnus Damm --- drivers/iommu/ipmmu-vmsa.c |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-)

  1   2   3   4   5   6   7   8   9   10   >