[PATCH] staging: lustre: really make lustre dependent on LNet

2016-03-14 Thread Arnd Bergmann
A patch intended to add a dependency on LNET for lustre didn't actually do that and instead allowed configurations that contain lustre with lnet but without IPv4 support that subsequently fail to link: warning: (LUSTRE_FS) selects LNET which has unmet direct dependencies (STAGING && INET && m &&

[PATCH] staging/comedi/dt282x: avoid integer overflow warning

2016-03-14 Thread Arnd Bergmann
gcc-6 warns about passing negative signed integer into swab16() in the dt282x driver: drivers/staging/comedi/drivers/dt282x.c: In function 'dt282x_load_changain': include/uapi/linux/swab.h:14:33: warning: integer overflow in expression [-Woverflow] (((__u16)(x) & (__u16)0xff00U) >> 8)))

[PATCH v8 1/2] staging/android: remove redundant comments on sync_merge_data

2016-03-14 Thread Gustavo Padovan
From: Gustavo Padovan struct sync_merge_data already have documentation on top of the struct definition. No need to duplicate it. Signed-off-by: Gustavo Padovan Reviewed-by: Maarten Lankhorst

[PATCH v8 2/2] staging/android: refactor SYNC IOCTLs

2016-03-14 Thread Gustavo Padovan
From: Gustavo Padovan Change SYNC_IOC_FILE_INFO (former SYNC_IOC_FENCE_INFO) behaviour to avoid future API breaks and optimize buffer allocation. Now num_fences can be filled by the caller to inform how many fences it wants to retrieve from the kernel. If the

[PATCH] Staging: wlan-ng: defined oui_rfc1042[] and oui_8021h[] arrays as const arrays

2016-03-14 Thread Claudiu Beznea
This patch defines oui_rfc1042[] and oui_8021h[] arrays from p80211conv.c as const arrays since these are not changed anywhere in code. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211conv.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH] Staging: vt6655: defined byVT3253InitTab_RFMD[] and byVT3253B0_RFMD[] as const arrays.

2016-03-14 Thread Claudiu Beznea
This patch changes byVT3253InitTab_RFMD[] and byVT3253B0_RFMD[] arrays in const arrays since these are not changed anywhere in the code. Signed-off-by: Claudiu Beznea --- drivers/staging/vt6655/baseband.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 4.4 35/50] x86/mm: Fix slow_virt_to_phys() for X86_PAE again

2016-03-14 Thread Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit bf70e5513dfea29c3682e7eb3dbb45f0723bac09 upstream. "d1cd12108346: x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE" was unintentionally

[PATCH] Staging: rtl8192u: remove extra blank lines.

2016-03-14 Thread Ben Marsh
This patch removes blank lines in r8192U_wx.c that were flagged by checkpatch.pl Signed-off-by: Ben Marsh --- drivers/staging/rtl8192u/r8192U_wx.c | 22 -- 1 file changed, 22 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_wx.c

[PATCH 2/2] staging: fsl-mc: fix incorrect type passed to dev_err macros

2016-03-14 Thread Cihangir Akturk
dev_err macros expect const struct device ** as its second argument, but here the argument we are passing is of typ struct device **. This patch fixes this error. Signed-off-by: Cihangir Akturk --- drivers/staging/fsl-mc/bus/mc-bus.c | 4 ++-- 1 file changed, 2 insertions(+),

[PATCH 1/2] staging: fsl-mc: fix incorrect type passed to dev_dbg macros

2016-03-14 Thread Cihangir Akturk
dev_dbg macros expect const struct device ** as its second argument but here the argument we are passing is of type struct device ** this patch fixes this error. Signed-off-by: Cihangir Akturk --- drivers/staging/fsl-mc/bus/mc-sys.c | 6 +++--- 1 file changed, 3

[PATCH 0/2] fix incorrect type passed to dev_* macros

2016-03-14 Thread Cihangir Akturk
Following patches fixes the incorrect pointer type passed to dev_* macros. Cihangir Akturk (2): staging: fsl-mc: fix incorrect type passed to dev_dbg macros staging: fsl-mc: fix incorrect type passed to dev_err macros drivers/staging/fsl-mc/bus/mc-bus.c | 4 ++--

Re: [PATCH 1/5] Staging: comedi: Fix type issues in s626.c

2016-03-14 Thread Ian Abbott
On 14/03/16 11:06, Ravishankar Karkala Mallikarjunayya wrote: This is a patch to the s626.c file that fixes up a type issues found by the checkpatch.pl tool. i.e Prefer kernel type 'u8' over 'uint8_t' Prefer kernel type 'u16' over 'uint16_t' Prefer kernel type 'u32' over 'uint32_t'

[PATCH] staging: refresh TODO for rtl8712

2016-03-14 Thread Xose Vazquez Perez
People should not waste time and energy working on this staging driver. At least four drivers were written for this hardware: https://marc.info/?l=linux-wireless=138358275410975 And there is a replacement using the kernel wireless stack at: https://github.com/chunkeey/rtl8192su Also a

Re: [PATCH 5/5] Staging: comedi: Fix type issue in ni_tio.c

2016-03-14 Thread Joe Perches
On Mon, 2016-03-14 at 16:36 +0530, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the ni_tio.c file that fixes up a type issues > found by the checkpatch.pl tool. > i.e. Prefer kernel type 'u64' over 'uint64_t' [] > diff --git a/drivers/staging/comedi/drivers/ni_tio.c >

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

2016-03-14 Thread Sakari Ailus
Hi Mauro, On Mon, Mar 14, 2016 at 08:46:33AM -0300, Mauro Carvalho Chehab wrote: > Em Mon, 14 Mar 2016 12:52:54 +0200 > Sakari Ailus escreveu: > > > Hi Mauro, > > > > On Mon, Mar 14, 2016 at 07:13:58AM -0300, Mauro Carvalho Chehab wrote: > > > Em Mon, 14 Mar 2016 09:22:37

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

2016-03-14 Thread Mauro Carvalho Chehab
Em Mon, 14 Mar 2016 12:52:54 +0200 Sakari Ailus escreveu: > Hi Mauro, > > On Mon, Mar 14, 2016 at 07:13:58AM -0300, Mauro Carvalho Chehab wrote: > > Em Mon, 14 Mar 2016 09:22:37 +0200 > > Sakari Ailus escreveu: > > > > > Hi Shuah, > > > > > > On

[PATCH 1/5] Staging: comedi: Fix type issues in s626.c

2016-03-14 Thread Ravishankar Karkala Mallikarjunayya
This is a patch to the s626.c file that fixes up a type issues found by the checkpatch.pl tool. i.e Prefer kernel type 'u8' over 'uint8_t' Prefer kernel type 'u16' over 'uint16_t' Prefer kernel type 'u32' over 'uint32_t' Prefer kernel type 's16' over 'int16_t' Prefer kernel type

[PATCH 5/5] Staging: comedi: Fix type issue in ni_tio.c

2016-03-14 Thread Ravishankar Karkala Mallikarjunayya
This is a patch to the ni_tio.c file that fixes up a type issues found by the checkpatch.pl tool. i.e. Prefer kernel type 'u64' over 'uint64_t' Signed-off-by: Ravishankar Karkala Mallikarjunayya --- drivers/staging/comedi/drivers/ni_tio.c | 8 1 file changed,

[PATCH 4/5] Staging: comedi: fix CHECK issue in ni_tio.c

2016-03-14 Thread Ravishankar Karkala Mallikarjunayya
This is a patch to the ni_tio.c file that fixes up a CHECK issues found by the checkpatch.pl tool. i.e. Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON(). Signed-off-by: Ravishankar Karkala Mallikarjunayya ---

[PATCH 2/5] Staging: comedi: Fix Block comment issues in s626.c

2016-03-14 Thread Ravishankar Karkala Mallikarjunayya
This is a patch to the s626.c file that fixes up a Block comments issues found by the checkpatch.pl tool. i.e. Block comments use a trailing */ on a separate line Signed-off-by: Ravishankar Karkala Mallikarjunayya --- drivers/staging/comedi/drivers/s626.c | 42

[PATCH 3/5] Staging: comedi: Fix WARNING issue in s626.c

2016-03-14 Thread Ravishankar Karkala Mallikarjunayya
This is a patch to the s626.c file that fixes up a line over 80 characters issues found by the checkpatch.pl tool. Signed-off-by: Ravishankar Karkala Mallikarjunayya --- drivers/staging/comedi/drivers/s626.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

2016-03-14 Thread Sakari Ailus
Hi Mauro, On Mon, Mar 14, 2016 at 07:13:58AM -0300, Mauro Carvalho Chehab wrote: > Em Mon, 14 Mar 2016 09:22:37 +0200 > Sakari Ailus escreveu: > > > Hi Shuah, > > > > On Sat, Mar 12, 2016 at 06:48:09PM -0700, Shuah Khan wrote: > > > Add GFP flags to

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

2016-03-14 Thread Takashi Iwai
On Mon, 14 Mar 2016 11:13:58 +0100, Mauro Carvalho Chehab wrote: > > Em Mon, 14 Mar 2016 09:22:37 +0200 > Sakari Ailus escreveu: > > > Hi Shuah, > > > > On Sat, Mar 12, 2016 at 06:48:09PM -0700, Shuah Khan wrote: > > > Add GFP flags to media_create_pad_link(),

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

2016-03-14 Thread Mauro Carvalho Chehab
Em Mon, 14 Mar 2016 09:22:37 +0200 Sakari Ailus escreveu: > Hi Shuah, > > On Sat, Mar 12, 2016 at 06:48:09PM -0700, Shuah Khan wrote: > > Add GFP flags to media_create_pad_link(), media_create_intf_link(), > > media_devnode_create(), and media_add_link() that could get

Re: [PATCH] Add tw5864 driver

2016-03-14 Thread Hans Verkuil
Hi Andrey, See below for a quick review of the code. I agree with Greg's comment why this is added to staging instead of drivers/media/pci? When you post the v2 patch, can you add the output of 'v4l2-compliance -s' to the cover letter? Please use the latest v4l2-compliance version from the

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

2016-03-14 Thread Sakari Ailus
Hi Shuah, On Sat, Mar 12, 2016 at 06:48:09PM -0700, Shuah Khan wrote: > Add GFP flags to media_create_pad_link(), media_create_intf_link(), > media_devnode_create(), and media_add_link() that could get called > in atomic context to allow callers to pass in the right flags for > memory allocation.

[PATCH] staging: dgnc: Add whitespace around OR'd flags ("|")

2016-03-14 Thread Sam Horlbeck Olsen
This patch fixes the checkpatch.pl message: CHECK: spaces preferred around that '|' (ctx:VxV) + writeb((UART_FCR_ENABLE_FIFO|UART_FCR_CLEAR_RCVR|UART_FCR_CLEAR_XMIT), ^ ^ As per the guidelines for coding style in the kernel, I have

Re: [PATCH] Add tw5864 driver

2016-03-14 Thread Joe Perches
On Mon, 2016-03-14 at 03:59 +0200, Andrey Utkin wrote: > Support for boards based on Techwell TW5864 chip which provides > multichannel video & audio grabbing and encoding (H.264, MJPEG, > ADPCM G.726). trivia: Perhaps all the __used arrays could be const