Re: fs/binfmt_em86.c:73:35: error: passing argument 2 of 'copy_strings_kernel' from incompatible pointer type

> All errors (new ones prefixed by >>): > >fs/binfmt_em86.c: In function 'load_em86': >>> fs/binfmt_em86.c:73:35: error: passing argument 2 of 'copy_strings_kernel' >>> from incompatible pointer type [-Werror=incompatible-pointer-types] > retval = copy_strings_kernel(1, _arg, bprm); >

Re: fs/binfmt_em86.c:73:35: error: passing argument 2 of 'copy_strings_kernel' from incompatible pointer type

> All errors (new ones prefixed by >>): > >fs/binfmt_em86.c: In function 'load_em86': >>> fs/binfmt_em86.c:73:35: error: passing argument 2 of 'copy_strings_kernel' >>> from incompatible pointer type [-Werror=incompatible-pointer-types] > retval = copy_strings_kernel(1, _arg, bprm); >

[PATCH v2] usb: dwc3: host: Set the dma_ops for xhci device

On ARM64 platform, it will set 'dummy_dma_ops' for device dma_ops if it did not call 'arch_setup_dma_ops' at device creation time, that will cause failure when setting the dma mask for device. Thus this patch set the xhci device dma_ops from the parent device if the xhci device dma_ops is

[PATCH v2] usb: dwc3: host: Set the dma_ops for xhci device

On ARM64 platform, it will set 'dummy_dma_ops' for device dma_ops if it did not call 'arch_setup_dma_ops' at device creation time, that will cause failure when setting the dma mask for device. Thus this patch set the xhci device dma_ops from the parent device if the xhci device dma_ops is

Re: [PATCH 0/4] mtd: nand: Add support for Evatronix NANDFLASH-CTRL

On Thu, 2 Jun 2016, Boris Brezillon wrote: > Hi Ricard, > > I was not in Cc of this series, so you're either developing an old > kernel version, or you didn't check the MAINTAINERS file (or didn't run > get_maintainer.pl on your series). The patch is intended to apply to the mtd l2 tree, and I

Re: [PATCH 0/4] mtd: nand: Add support for Evatronix NANDFLASH-CTRL

On Thu, 2 Jun 2016, Boris Brezillon wrote: > Hi Ricard, > > I was not in Cc of this series, so you're either developing an old > kernel version, or you didn't check the MAINTAINERS file (or didn't run > get_maintainer.pl on your series). The patch is intended to apply to the mtd l2 tree, and I

[PATCH V4 2/5] irqchip/gicv3-its: Add a new function for parsing device table BASERn

Only the device table BASERn needs to be handled differently as compared to all other tables. So, adding a separate function for easy code maintenance and improved code readability. Signed-off-by: Shanker Donthineni --- drivers/irqchip/irq-gic-v3-its.c | 49

[PATCH V4 2/5] irqchip/gicv3-its: Add a new function for parsing device table BASERn

Only the device table BASERn needs to be handled differently as compared to all other tables. So, adding a separate function for easy code maintenance and improved code readability. Signed-off-by: Shanker Donthineni --- drivers/irqchip/irq-gic-v3-its.c | 49

[PATCH V4 0/5] Add two-level support for ITS device table

This patchset contains necessary code changes to support two-level (Indirection) table walk feature for device table. Shanker Donthineni (5): irqchip/gicv3-its: Introduce two helper functions for accessing BASERn irqchip/gicv3-its: Add a new function for parsing device table BASERn

[PATCH V4 0/5] Add two-level support for ITS device table

This patchset contains necessary code changes to support two-level (Indirection) table walk feature for device table. Shanker Donthineni (5): irqchip/gicv3-its: Introduce two helper functions for accessing BASERn irqchip/gicv3-its: Add a new function for parsing device table BASERn

[PATCH V4 4/5] irqchip/gicv3-its: Remove an unused argument 'node_name'

No references to argument 'node_name' after modifying pr_xxx() messages to include ITS base address instead of 'node_name'. Signed-off-by: Shanker Donthineni --- drivers/irqchip/irq-gic-v3-its.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH V4 5/5] irqchip/gicv3-its: Implement two-level(indirect) device table support

Since device IDs are extremely sparse, the single, a.k.a flat table is not sufficient for the following two reasons. 1) According to ARM-GIC spec, ITS hw can access maximum of 256(pages)* 64K(pageszie) bytes. In the best case, it supports upto DEVid=21 sparse with minimum device table entry

[PATCH V4 3/5] irqchip/gicv3-its: Split its_alloc_tables() into two functions

The function is getting out of control, it has too many goto statements and would be too complicated for adding a feature two-level device table. So, it is time for us to cleanup and move some of the logic to a separate function without affecting the existing functionality. Signed-off-by: Shanker

[PATCH V4 1/5] irqchip/gicv3-its: Introduce two helper functions for accessing BASERn

This patch adds the two handy helper functions for reading and writing ITS BASERn register. Signed-off-by: Shanker Donthineni --- drivers/irqchip/irq-gic-v3-its.c | 32 +--- 1 file changed, 25 insertions(+), 7 deletions(-) diff --git

[PATCH V4 4/5] irqchip/gicv3-its: Remove an unused argument 'node_name'

No references to argument 'node_name' after modifying pr_xxx() messages to include ITS base address instead of 'node_name'. Signed-off-by: Shanker Donthineni --- drivers/irqchip/irq-gic-v3-its.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH V4 5/5] irqchip/gicv3-its: Implement two-level(indirect) device table support

Since device IDs are extremely sparse, the single, a.k.a flat table is not sufficient for the following two reasons. 1) According to ARM-GIC spec, ITS hw can access maximum of 256(pages)* 64K(pageszie) bytes. In the best case, it supports upto DEVid=21 sparse with minimum device table entry

[PATCH V4 3/5] irqchip/gicv3-its: Split its_alloc_tables() into two functions

The function is getting out of control, it has too many goto statements and would be too complicated for adding a feature two-level device table. So, it is time for us to cleanup and move some of the logic to a separate function without affecting the existing functionality. Signed-off-by: Shanker

[PATCH V4 1/5] irqchip/gicv3-its: Introduce two helper functions for accessing BASERn

This patch adds the two handy helper functions for reading and writing ITS BASERn register. Signed-off-by: Shanker Donthineni --- drivers/irqchip/irq-gic-v3-its.c | 32 +--- 1 file changed, 25 insertions(+), 7 deletions(-) diff --git

Re: powerpc/nvram: Fix an incorrect partition merge

On 2016年06月03日 19:47, Michael Ellerman wrote: On Thu, 2015-10-12 at 07:30:02 UTC, xinhui wrote: From: Pan Xinhui When we merge two contiguous partitions whose signatures are marked NVRAM_SIG_FREE, We need update prev's length and checksum, then write it to

Re: powerpc/nvram: Fix an incorrect partition merge

On 2016年06月03日 19:47, Michael Ellerman wrote: On Thu, 2015-10-12 at 07:30:02 UTC, xinhui wrote: From: Pan Xinhui When we merge two contiguous partitions whose signatures are marked NVRAM_SIG_FREE, We need update prev's length and checksum, then write it to nvram, not cur's. So lets fix this

Re: [PATCH 2/3] hisi_sas: fix the inconsistent lock issue reported by CONFIG_PROVE_LOCKING

On 05/31/2016 08:38 PM, John Garry wrote: It is not necessary to surround call to notify_port_event(, PORTE_BROADCAST_RCVD) by spin_lock_irqsave(), so remove. This was causing a warn, as below: = [ INFO: inconsistent lock state ] 4.4.8+ #12 Not

Re: [PATCH 1/3] hisi_sas: add v2 hw ACPI support

On 05/31/2016 08:38 PM, John Garry wrote: Add support in v2 hw driver for ACPI. A check on whether an ACPI handle is available for the device is used to decide on whether to use ACPI reset handler or syscon for hw reset. Signed-off-by: John Garry Signed-off-by: Wei Xu

Re: [PATCH 2/3] hisi_sas: fix the inconsistent lock issue reported by CONFIG_PROVE_LOCKING

On 05/31/2016 08:38 PM, John Garry wrote: It is not necessary to surround call to notify_port_event(, PORTE_BROADCAST_RCVD) by spin_lock_irqsave(), so remove. This was causing a warn, as below: = [ INFO: inconsistent lock state ] 4.4.8+ #12 Not

Re: [PATCH 1/3] hisi_sas: add v2 hw ACPI support

On 05/31/2016 08:38 PM, John Garry wrote: Add support in v2 hw driver for ACPI. A check on whether an ACPI handle is available for the device is used to decide on whether to use ACPI reset handler or syscon for hw reset. Signed-off-by: John Garry Signed-off-by: Wei Xu Reviewed-by:

[PATCH v3 2/4] staging: r8188eu: Replace semaphore terminate_cmdthread_sema with completion

The semaphore 'terminate_cmdthread_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann Acked-by: Larry Finger --- drivers/staging/rtl8188eu/core/rtw_cmd.c|

[PATCH v3 2/4] staging: r8188eu: Replace semaphore terminate_cmdthread_sema with completion

The semaphore 'terminate_cmdthread_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann Acked-by: Larry Finger --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++--- drivers/staging/rtl8188eu/include/rtw_cmd.h | 2 +-

[PATCH v3 3/4] staging: r8188eu: pwrctrl_priv: Replace semaphore 'lock' with mutex

The semaphore 'lock' in pwrctrl_priv is a simple mutex, so it should be written as one. Semaphores are going away in the future. _enter_pwrlock was using down_interruptible(), so the lock could be broken by sending a signal. This could be a bug, because nothing checks the return code here. Hence,

[PATCH v3 1/4] staging: r8188eu: Replace semaphore cmd_queue_sema with completion

The semaphore 'cmd_queue_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann Acked-by: Larry Finger --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++---

[PATCH v3 0/4] *** staging: r8188eu: Replace semaphores with mutexes or completions ***

Hi, These are a set of patches [v3] which removes semaphores from: drivers/staging/rtl8188eu These are part of a bigger effort to eliminate all semaphores from the linux kernel. They build correctly (individually and as a whole). NB: I have not tested this as I do not have the following

[PATCH v3 4/4] staging: r8188eu: Remove unused semaphores

The semaphores xmit_sema, terminate_xmitthread_sema and tx_retevt have no users, hence remove all references to them. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann Acked-by: Larry Finger ---

[PATCH v3 3/4] staging: r8188eu: pwrctrl_priv: Replace semaphore 'lock' with mutex

The semaphore 'lock' in pwrctrl_priv is a simple mutex, so it should be written as one. Semaphores are going away in the future. _enter_pwrlock was using down_interruptible(), so the lock could be broken by sending a signal. This could be a bug, because nothing checks the return code here. Hence,

[PATCH v3 1/4] staging: r8188eu: Replace semaphore cmd_queue_sema with completion

The semaphore 'cmd_queue_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann Acked-by: Larry Finger --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++--- drivers/staging/rtl8188eu/include/rtw_cmd.h | 2 +-

[PATCH v3 0/4] *** staging: r8188eu: Replace semaphores with mutexes or completions ***

Hi, These are a set of patches [v3] which removes semaphores from: drivers/staging/rtl8188eu These are part of a bigger effort to eliminate all semaphores from the linux kernel. They build correctly (individually and as a whole). NB: I have not tested this as I do not have the following

[PATCH v3 4/4] staging: r8188eu: Remove unused semaphores

The semaphores xmit_sema, terminate_xmitthread_sema and tx_retevt have no users, hence remove all references to them. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann Acked-by: Larry Finger --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 4

Re: [PATCH 1/1 linux-next] ASoC: cs53l30: include gpio/consumer.h

On Sun, Jun 05, 2016 at 03:11:00PM +0200, Fabian Frederick wrote: > cs53l30 breaks kernel compilation when CONFIG_GPIOLIB is disabled. > > sound/soc/codecs/cs53l30.c:931:2: error: implicit declaration of > function devm_gpiod_get_optional [-Werror=implicit-function-declaration] >

Re: [PATCH 1/1 linux-next] ASoC: cs53l30: include gpio/consumer.h

On Sun, Jun 05, 2016 at 03:11:00PM +0200, Fabian Frederick wrote: > cs53l30 breaks kernel compilation when CONFIG_GPIOLIB is disabled. > > sound/soc/codecs/cs53l30.c:931:2: error: implicit declaration of > function devm_gpiod_get_optional [-Werror=implicit-function-declaration] >

Re: [RFC v2 1/3] block: Introduce blk_bio_map_sg() to map one bio

On 3 June 2016 at 22:35, Jens Axboe wrote: > On 05/27/2016 05:11 AM, Baolin Wang wrote: >> >> In dm-crypt, it need to map one bio to scatterlist for improving the >> hardware engine encryption efficiency. Thus this patch introduces the >> blk_bio_map_sg() function to map one bio

Re: [RFC v2 1/3] block: Introduce blk_bio_map_sg() to map one bio

On 3 June 2016 at 22:35, Jens Axboe wrote: > On 05/27/2016 05:11 AM, Baolin Wang wrote: >> >> In dm-crypt, it need to map one bio to scatterlist for improving the >> hardware engine encryption efficiency. Thus this patch introduces the >> blk_bio_map_sg() function to map one bio with

Re: [RFC v2 1/3] block: Introduce blk_bio_map_sg() to map one bio

On 3 June 2016 at 22:38, Jens Axboe wrote: > On 05/27/2016 05:11 AM, Baolin Wang wrote: >> >> +/* >> + * Map a bio to scatterlist, return number of sg entries setup. Caller >> must >> + * make sure sg can hold bio segments entries. >> + */ >> +int blk_bio_map_sg(struct

Re: [RFC v2 1/3] block: Introduce blk_bio_map_sg() to map one bio

On 3 June 2016 at 22:38, Jens Axboe wrote: > On 05/27/2016 05:11 AM, Baolin Wang wrote: >> >> +/* >> + * Map a bio to scatterlist, return number of sg entries setup. Caller >> must >> + * make sure sg can hold bio segments entries. >> + */ >> +int blk_bio_map_sg(struct request_queue *q, struct

undefined reference to `dma_common_mmap'

Hi, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: af8c34ce6ae32addda3788d54a7e340cad22516b commit: 420520766a796d3607639ba1e4fb1aadeadd [media] media: Kconfig: add dependency of HAS_DMA date:

undefined reference to `dma_common_mmap'

Hi, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: af8c34ce6ae32addda3788d54a7e340cad22516b commit: 420520766a796d3607639ba1e4fb1aadeadd [media] media: Kconfig: add dependency of HAS_DMA date:

Re: [v2] powerpc: spinlock: Fix spin_unlock_wait()

On Mon, Jun 06, 2016 at 02:52:05PM +1000, Michael Ellerman wrote: > On Fri, 2016-03-06 at 03:49:48 UTC, Boqun Feng wrote: > > There is an ordering issue with spin_unlock_wait() on powerpc, because > > the spin_lock primitive is an ACQUIRE and an ACQUIRE is only ordering > > the load part of the

Re: [PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

On Monday 06 June 2016 09:07 AM, Keerthy wrote: On Wednesday 25 May 2016 08:51 AM, Keerthy wrote: Hi Santosh, On Tuesday 24 May 2016 09:59 PM, Santosh Shilimkar wrote: Hi Keerthy, On 5/23/2016 8:56 PM, Keerthy wrote: On Tuesday 24 May 2016 09:07 AM, Lokesh Vutla wrote: On Monday 23

Re: [v2] powerpc: spinlock: Fix spin_unlock_wait()

On Mon, Jun 06, 2016 at 02:52:05PM +1000, Michael Ellerman wrote: > On Fri, 2016-03-06 at 03:49:48 UTC, Boqun Feng wrote: > > There is an ordering issue with spin_unlock_wait() on powerpc, because > > the spin_lock primitive is an ACQUIRE and an ACQUIRE is only ordering > > the load part of the

Re: [PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

On Monday 06 June 2016 09:07 AM, Keerthy wrote: On Wednesday 25 May 2016 08:51 AM, Keerthy wrote: Hi Santosh, On Tuesday 24 May 2016 09:59 PM, Santosh Shilimkar wrote: Hi Keerthy, On 5/23/2016 8:56 PM, Keerthy wrote: On Tuesday 24 May 2016 09:07 AM, Lokesh Vutla wrote: On Monday 23

Re: [PATCH net-next 1/3] arm64: bpf: implement bpf_tail_call() helper

ay-ci/linux/commits/Zi-Shen-Lim/arm64-bpf-implement-bpf_tail_call-helper/20160605-060435 >> config: arm64-defconfig (attached as .config) >> compiler: aarch64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205 >> reproduce: >> wget >> https://git.kernel.org/cgi

Re: [PATCH net-next 1/3] arm64: bpf: implement bpf_tail_call() helper

Hi Daniel, On Sun, Jun 5, 2016 at 12:53 AM, Daniel Borkmann wrote: > On 06/05/2016 01:46 AM, kbuild test robot wrote: >> >> Hi, >> >> [auto build test ERROR on net-next/master] >> >> url: >> https://github.com/0day-ci/linux/commits/Zi-Shen-Lim/arm6

Re: [PATCH 00/18] Add support for FDMA DMA controller and xp70 rproc found on STi chipsets

On Wed, May 25, 2016 at 05:06:33PM +0100, Peter Griffin wrote: > > Peter Griffin (18): > dmaengine: st_fdma: Add STMicroelectronics FDMA DT binding > documentation > dmaengine: st_fdma: Add STMicroelectronics FDMA driver header file > dmaengine: st_fdma: Add STMicroelectronics FDMA

Re: [PATCH 00/18] Add support for FDMA DMA controller and xp70 rproc found on STi chipsets

On Wed, May 25, 2016 at 05:06:33PM +0100, Peter Griffin wrote: > > Peter Griffin (18): > dmaengine: st_fdma: Add STMicroelectronics FDMA DT binding > documentation > dmaengine: st_fdma: Add STMicroelectronics FDMA driver header file > dmaengine: st_fdma: Add STMicroelectronics FDMA

Re: [v2] powerpc: spinlock: Fix spin_unlock_wait()

On Fri, 2016-03-06 at 03:49:48 UTC, Boqun Feng wrote: > There is an ordering issue with spin_unlock_wait() on powerpc, because > the spin_lock primitive is an ACQUIRE and an ACQUIRE is only ordering > the load part of the operation with memory operations following it. ... > diff --git

Re: [v2] powerpc: spinlock: Fix spin_unlock_wait()

On Fri, 2016-03-06 at 03:49:48 UTC, Boqun Feng wrote: > There is an ordering issue with spin_unlock_wait() on powerpc, because > the spin_lock primitive is an ACQUIRE and an ACQUIRE is only ordering > the load part of the operation with memory operations following it. ... > diff --git

Re: [v2, 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Heiko & Guenter, On 2016/6/4 5:24, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 12:59:22 schrieb Guenter Roeck: On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote: The newer SoCs (rk3366, rk3399) take a different usb-phy IP block than rk3288 and before, and most of phy-related

Re: [v2, 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Heiko & Guenter, On 2016/6/4 5:24, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 12:59:22 schrieb Guenter Roeck: On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote: The newer SoCs (rk3366, rk3399) take a different usb-phy IP block than rk3288 and before, and most of phy-related

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On 2016年06月04日 05:35, Peter Zijlstra wrote: On Fri, Jun 03, 2016 at 05:20:10PM -0400, Waiman Long wrote: On 06/03/2016 05:48 AM, Pan Xinhui wrote: queued_spin_lock_slowpath should not worry about interrupt change node->count by accident because ->count is inc and dec when we enter/leave

RE: [PATCH] net: fec: fix spelling mistake "coalesed" -> "coalesced"

From: Colin King Sent: Sunday, June 05, 2016 3:01 AM > To: Fugang Duan ; net...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Subject: [PATCH] net: fec: fix spelling mistake "coalesed" -> "coalesced" > > From: Colin Ian King

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On 2016年06月04日 05:35, Peter Zijlstra wrote: On Fri, Jun 03, 2016 at 05:20:10PM -0400, Waiman Long wrote: On 06/03/2016 05:48 AM, Pan Xinhui wrote: queued_spin_lock_slowpath should not worry about interrupt change node->count by accident because ->count is inc and dec when we enter/leave

RE: [PATCH] net: fec: fix spelling mistake "coalesed" -> "coalesced"

From: Colin King Sent: Sunday, June 05, 2016 3:01 AM > To: Fugang Duan ; net...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Subject: [PATCH] net: fec: fix spelling mistake "coalesed" -> "coalesced" > > From: Colin Ian King > > trivial fix to spelling mistake in pr_err message > >

Re: [PATCH v3] drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel

Hi Thierry, On 2 June 2016 at 08:44, Vinay Simha BN wrote: > Add support for the JDI lt070me05000 WUXGA DSI panel used in > Nexus 7 2013 devices. > > Programming sequence for the panel is was originally found in the > android-msm-flo-3.4-lollipop-release branch from: >

[PATCH 1/3] ARM: dts: keystone-k2l: Add pinctrl node

Add pinctrl node and populate the pinctrl registers with the default values. Signed-off-by: Keerthy --- arch/arm/boot/dts/keystone-k2l.dtsi | 149 1 file changed, 149 insertions(+) diff --git a/arch/arm/boot/dts/keystone-k2l.dtsi

Re: [PATCH v3] drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel

Hi Thierry, On 2 June 2016 at 08:44, Vinay Simha BN wrote: > Add support for the JDI lt070me05000 WUXGA DSI panel used in > Nexus 7 2013 devices. > > Programming sequence for the panel is was originally found in the > android-msm-flo-3.4-lollipop-release branch from: >

[PATCH 1/3] ARM: dts: keystone-k2l: Add pinctrl node

Add pinctrl node and populate the pinctrl registers with the default values. Signed-off-by: Keerthy --- arch/arm/boot/dts/keystone-k2l.dtsi | 149 1 file changed, 149 insertions(+) diff --git a/arch/arm/boot/dts/keystone-k2l.dtsi

Re: [PATCH v4 06/18] dmaengine: st_fdma: Add STMicroelectronics FDMA engine driver support

On Wed, May 25, 2016 at 05:06:40PM +0100, Peter Griffin wrote: > @@ -527,6 +527,18 @@ config ZX_DMA > help > Support the DMA engine for ZTE ZX296702 platform devices. > > +config ST_FDMA > + tristate "ST FDMA dmaengine support" > + depends on ARCH_STI || COMPILE_TEST > +

Re: [PATCH v4 06/18] dmaengine: st_fdma: Add STMicroelectronics FDMA engine driver support

On Wed, May 25, 2016 at 05:06:40PM +0100, Peter Griffin wrote: > @@ -527,6 +527,18 @@ config ZX_DMA > help > Support the DMA engine for ZTE ZX296702 platform devices. > > +config ST_FDMA > + tristate "ST FDMA dmaengine support" > + depends on ARCH_STI || COMPILE_TEST > +

[PATCH 0/3] ARM: keystone-k2l: Enable pinctrl support

The series enables pinctrl support for k2l devices. Tested on keystone-k2l-evm board. Franklin S Cooper Jr (1): ARM: configs: keystone: Enable PINCTRL_SINGLE Config Keerthy (1): ARM: dts: keystone-k2l: Add pinctrl node Lokesh Vutla (1): arm: mach-keystone: Enable PINCTRL config

[PATCH 0/3] ARM: keystone-k2l: Enable pinctrl support

The series enables pinctrl support for k2l devices. Tested on keystone-k2l-evm board. Franklin S Cooper Jr (1): ARM: configs: keystone: Enable PINCTRL_SINGLE Config Keerthy (1): ARM: dts: keystone-k2l: Add pinctrl node Lokesh Vutla (1): arm: mach-keystone: Enable PINCTRL config

[PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

From: Franklin S Cooper Jr Newer Keystone 2 devices utilize pinmuxing. Enable PINCTRL SINGLE which is used to handle pinmuxing. Signed-off-by: Franklin S Cooper Jr Signed-off-by: Keerthy --- arch/arm/configs/keystone_defconfig | 1 + 1 file

[PATCH 2/3] arm: mach-keystone: Enable PINCTRL config

From: Lokesh Vutla Some Keystone 2 devices utilize pinmuxing which requires PINCTRL to be enabled. Therefore, enable PINCTRL for all Keystone 2 devices. Signed-off-by: Lokesh Vutla Signed-off-by: Franklin S Cooper Jr Signed-off-by: Dave

[PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

From: Franklin S Cooper Jr Newer Keystone 2 devices utilize pinmuxing. Enable PINCTRL SINGLE which is used to handle pinmuxing. Signed-off-by: Franklin S Cooper Jr Signed-off-by: Keerthy --- arch/arm/configs/keystone_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 2/3] arm: mach-keystone: Enable PINCTRL config

From: Lokesh Vutla Some Keystone 2 devices utilize pinmuxing which requires PINCTRL to be enabled. Therefore, enable PINCTRL for all Keystone 2 devices. Signed-off-by: Lokesh Vutla Signed-off-by: Franklin S Cooper Jr Signed-off-by: Dave Gerlach Signed-off-by: Keerthy ---

Re: [v2, 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Guenter, On 2016/6/4 3:57, Guenter Roeck wrote: On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote: The newer SoCs (rk3366, rk3399) take a different usb-phy IP block than rk3288 and before, and most of phy-related registers are also different from the past, so a new phy driver is

Re: [v2, 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Guenter, On 2016/6/4 3:57, Guenter Roeck wrote: On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote: The newer SoCs (rk3366, rk3399) take a different usb-phy IP block than rk3288 and before, and most of phy-related registers are also different from the past, so a new phy driver is

[PATCH v2 3/4] rtl8188eu: pwrctrl_priv: Replace semaphore 'lock' with mutex

The semaphore 'lock' in pwrctrl_priv is a simple mutex, so it should be written as one. Semaphores are going away in the future. _enter_pwrlock was using down_interruptible(), so the lock could be broken by sending a signal. This could be a bug, because nothing checks the return code here. Hence,

[PATCH v2 3/4] rtl8188eu: pwrctrl_priv: Replace semaphore 'lock' with mutex

The semaphore 'lock' in pwrctrl_priv is a simple mutex, so it should be written as one. Semaphores are going away in the future. _enter_pwrlock was using down_interruptible(), so the lock could be broken by sending a signal. This could be a bug, because nothing checks the return code here. Hence,

[PATCH v2 4/4] rtl8188eu: Remove unused semaphores

The semaphores xmit_sema, terminate_xmitthread_sema and tx_retevt have no users, hence remove all references to them. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 4

[PATCH v2 0/4] *** rtl8188eu: Replace semaphores with mutexes or completions ***

Hi, These are a set of patches [v2] which removes semaphores from: drivers/staging/rtl8188eu These are part of a bigger effort to eliminate all semaphores from the linux kernel. They build correctly (individually and as a whole). NB: I have not tested this as I do not have the following

[PATCH v2 2/4] rtl8188eu: Replace semaphore terminate_cmdthread_sema with completion

The semaphore 'terminate_cmdthread_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++---

[PATCH v2 1/4] irtl8188eu: Replace semaphore cmd_queue_sema with completion

The semaphore 'cmd_queue_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++--- drivers/staging/rtl8188eu/include/rtw_cmd.h | 2 +-

[PATCH v2 4/4] rtl8188eu: Remove unused semaphores

The semaphores xmit_sema, terminate_xmitthread_sema and tx_retevt have no users, hence remove all references to them. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 4 drivers/staging/rtl8188eu/include/osdep_service.h | 1 -

[PATCH v2 0/4] *** rtl8188eu: Replace semaphores with mutexes or completions ***

Hi, These are a set of patches [v2] which removes semaphores from: drivers/staging/rtl8188eu These are part of a bigger effort to eliminate all semaphores from the linux kernel. They build correctly (individually and as a whole). NB: I have not tested this as I do not have the following

[PATCH v2 2/4] rtl8188eu: Replace semaphore terminate_cmdthread_sema with completion

The semaphore 'terminate_cmdthread_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++--- drivers/staging/rtl8188eu/include/rtw_cmd.h | 2 +-

[PATCH v2 1/4] irtl8188eu: Replace semaphore cmd_queue_sema with completion

The semaphore 'cmd_queue_sema' is used as completion, so convert it to struct completion. Signed-off-by: Binoy Jayan Reviewed-by: Arnd Bergmann --- drivers/staging/rtl8188eu/core/rtw_cmd.c| 6 +++--- drivers/staging/rtl8188eu/include/rtw_cmd.h | 2 +-

Re: [v2, 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY

Hi Guenter, On 2016/6/4 3:25, Guenter Roeck wrote: On Thu, Jun 02, 2016 at 02:48:09PM +0800, Frank Wang wrote: Signed-off-by: Frank Wang --- Changes in v2: - Changed vbus_host optional property from gpio to regulator. - Specified vbus_otg-supply optional

Re: [v2, 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY

Hi Guenter, On 2016/6/4 3:25, Guenter Roeck wrote: On Thu, Jun 02, 2016 at 02:48:09PM +0800, Frank Wang wrote: Signed-off-by: Frank Wang --- Changes in v2: - Changed vbus_host optional property from gpio to regulator. - Specified vbus_otg-supply optional property. - Specified otg_id

Re: [PATCH v4 05/18] dmaengine: st_fdma: Add STMicroelectronics FDMA driver header file

On Wed, May 25, 2016 at 05:06:39PM +0100, Peter Griffin wrote: > +/* > + * request control bits > + */ > +#define REQ_CTRL_NUM_OPS_MASKGENMASK(31, 24) > +#define REQ_CTRL_NUM_OPS(n) (REQ_CTRL_NUM_OPS_MASK & ((n) << 24)) > +#define REQ_CTRL_INITIATOR_MASK

[PATCH] serial: 8250_uniphier: add COMPILE_TEST option

Add COMPILE_TEST for the compilation test coverage. Signed-off-by: Masahiro Yamada --- drivers/tty/serial/8250/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig index

Re: [PATCH v4 05/18] dmaengine: st_fdma: Add STMicroelectronics FDMA driver header file

On Wed, May 25, 2016 at 05:06:39PM +0100, Peter Griffin wrote: > +/* > + * request control bits > + */ > +#define REQ_CTRL_NUM_OPS_MASKGENMASK(31, 24) > +#define REQ_CTRL_NUM_OPS(n) (REQ_CTRL_NUM_OPS_MASK & ((n) << 24)) > +#define REQ_CTRL_INITIATOR_MASK

[PATCH] serial: 8250_uniphier: add COMPILE_TEST option

Add COMPILE_TEST for the compilation test coverage. Signed-off-by: Masahiro Yamada --- drivers/tty/serial/8250/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig index e46761d..b5a0f2e 100644 ---

linux-next: Tree for Jun 6

Hi all, Changes since 20160603: New tree: amlogic Dropped tree: amlogic (build failure) My fixes tree contains: of: silence warnings due to max() usage The amlogic tree gained a build failure so I dropped it for today. The samsung-krzk tree gained a conflict against the arm-soc tree. The

linux-next: Tree for Jun 6

Hi all, Changes since 20160603: New tree: amlogic Dropped tree: amlogic (build failure) My fixes tree contains: of: silence warnings due to max() usage The amlogic tree gained a build failure so I dropped it for today. The samsung-krzk tree gained a conflict against the arm-soc tree. The

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

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, > meaning you couldn't poll for DMA completion with interrupts masked. and why is that? > This

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

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, > meaning you couldn't poll for DMA completion with interrupts masked. and why is that? > This

Re: [PATCH] dma: bcm2835: Fix compiler warning on arm64.

On Fri, Jun 03, 2016 at 07:23:33PM -0700, Eric Anholt wrote: > The min() macro was complaining about mismatched types. The max len > is at most SZ_1G, so we can just put it in an unsigned int. > > Signed-off-by: Eric Anholt > --- > > Vinod, if you ack it, this one would be

Re: [PATCH] dma: bcm2835: Fix compiler warning on arm64.

On Fri, Jun 03, 2016 at 07:23:33PM -0700, Eric Anholt wrote: > The min() macro was complaining about mismatched types. The max len > is at most SZ_1G, so we can just put it in an unsigned int. > > Signed-off-by: Eric Anholt > --- > > Vinod, if you ack it, this one would be nice to be able to

Re: [PATCH] tmpfs: don't undo fallocate past its last page

On Mon, May 16, 2016 at 4:59 AM, Vlastimil Babka wrote: > On 05/08/2016 03:16 PM, Anthony Romano wrote: >> >> When fallocate is interrupted it will undo a range that extends one byte >> past its range of allocated pages. This can corrupt an in-use page by >> zeroing out its first

Re: [PATCH] tmpfs: don't undo fallocate past its last page

On Mon, May 16, 2016 at 4:59 AM, Vlastimil Babka wrote: > On 05/08/2016 03:16 PM, Anthony Romano wrote: >> >> When fallocate is interrupted it will undo a range that extends one byte >> past its range of allocated pages. This can corrupt an in-use page by >> zeroing out its first byte. Instead,

[PATCH v2 07/11] iommu/ipmmu-vmsa: IPMMU device is 64-bit bus master

From: Magnus Damm The r8a7795 IPMMU supports 64-bit bus mastering. Both the coherent DMA mask and the streaming DMA mask are set to unlock the 64-bit address space for coherent allocations and streaming operations. Signed-off-by: Magnus Damm

[PATCH v2 08/11] iommu/ipmmu-vmsa: Write IMCTR twice

From: Magnus Damm Write IMCTR both in the root device and the leaf node. Signed-off-by: Magnus Damm --- Changes since V1: - None drivers/iommu/ipmmu-vmsa.c | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-)

[PATCH v2 07/11] iommu/ipmmu-vmsa: IPMMU device is 64-bit bus master

From: Magnus Damm The r8a7795 IPMMU supports 64-bit bus mastering. Both the coherent DMA mask and the streaming DMA mask are set to unlock the 64-bit address space for coherent allocations and streaming operations. Signed-off-by: Magnus Damm --- Changes since V1: - Updated the commit

[PATCH v2 08/11] iommu/ipmmu-vmsa: Write IMCTR twice

From: Magnus Damm Write IMCTR both in the root device and the leaf node. Signed-off-by: Magnus Damm --- Changes since V1: - None drivers/iommu/ipmmu-vmsa.c | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) --- 0021/drivers/iommu/ipmmu-vmsa.c +++

  1   2   3   4   5   6   7   8   9   10   >