Scheduled Maintenance & Upgrade

2019-04-15 Thread Help Desk
Help Desk Scheduled Maintenance & Upgrade Your account is in the process of being upgraded to the newest Windows-based servers and an enhanced online email interface inline with internet infrastructure Maintenance. The new servers will provide better anti-spam and anti-virus functions,

Re: [PATCH v4 12/12] staging: most: Documentation: update driver documentation

2019-04-15 Thread Eugeniu Rosca
Hello Christian, hello Andrey, cc: Vladimir Barinov cc: linux-renesas-soc Our team currently has the requirement of adding MOST support to the v4.14-based R-Car3 kernel [1], matching the level of features and interfaces of mld-1.8.0 [2] release. Based on a quick check [3], the mld-1.8.0 release

[PATCH 0/3] Cleanups in rtl8723bs

2019-04-15 Thread Madhumitha Prabakaran
Patch 1 and 2 remove typedef in structures. Patch 3 remove unused structure. Madhumitha Prabakaran (3): Staging: rtl8723bs: Remove typedef in struct ieee_param_ex Staging: rtl8723bs: Remove typedef in struct ieee_param Staging: rtl8723bs: Remove an unused struct tx_pending_t

[PATCH 1/3] Staging: rtl8723bs: Remove typedef in struct ieee_param_ex

2019-04-15 Thread Madhumitha Prabakaran
Remove typedef in struct ieee_param_ex, as the struct that has elements that can reasonably be directly accessed should never be a typedef. Signed-off-by: Madhumitha Prabakaran --- drivers/staging/rtl8723bs/include/ieee80211.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 3/3] Staging: rtl8723bs: Remove an unused struct tx_pending_t

2019-04-15 Thread Madhumitha Prabakaran
Remove an unused struct tx_pending_t, as it is never used in kernel tree. Signed-off-by: Madhumitha Prabakaran --- drivers/staging/rtl8723bs/include/ieee80211.h | 7 --- 1 file changed, 7 deletions(-) diff --git a/drivers/staging/rtl8723bs/include/ieee80211.h

[PATCH 2/3] Staging: rtl8723bs: Remove typedef in struct ieee_param

2019-04-15 Thread Madhumitha Prabakaran
Remove typedef in struct ieee_param, as the struct that has elements that can reasonably be directly accessed should never be a typedef. Signed-off-by: Madhumitha Prabakaran --- drivers/staging/rtl8723bs/include/ieee80211.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] staging: comedi: adv_pci1710: fix spelling mistake: "droput" -> "dropout"

2019-04-15 Thread Colin King
From: Colin Ian King There is a spelling mistake in a dev_error message. Fix it. Signed-off-by: Colin Ian King --- drivers/staging/comedi/drivers/adv_pci1710.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/comedi/drivers/adv_pci1710.c

[PATCH] staging: wilc1000: fix spelling mistake "dissconect" -> "disconnect"

2019-04-15 Thread Colin King
From: Colin Ian King There is a spelling mistake in a netdev_err error message, fix it. Signed-off-by: Colin Ian King --- drivers/staging/wilc1000/host_interface.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wilc1000/host_interface.c

Re: [PATCH] Staging: greybus: Cleanup in header file control.h

2019-04-15 Thread Dan Carpenter
On Mon, Apr 15, 2019 at 05:03:33PM +0200, Johan Hovold wrote: > But then all eight or so instances should be replaced in one go, to > maintain consistency. Yeah, that's fair enough, I suppose. regards, dan carepenter ___ devel mailing list

Re: [PATCH] Staging: greybus: Cleanup in header file control.h

2019-04-15 Thread Johan Hovold
On Mon, Apr 15, 2019 at 05:40:16PM +0300, Dan Carpenter wrote: > What I'm saying is that if we just apply it then we avoid the long > discussion forever. The macro is OK, sure, but it's not like anyone is > going to come back later and argue that macros are better or preferred. That may be a

Re: [PATCH] Staging: greybus: Cleanup in header file control.h

2019-04-15 Thread Dan Carpenter
What I'm saying is that if we just apply it then we avoid the long discussion forever. The macro is OK, sure, but it's not like anyone is going to come back later and argue that macros are better or preferred. regards, dan carpenter ___ devel mailing

Re: [PATCH] Staging: greybus: Cleanup in header file control.h

2019-04-15 Thread Johan Hovold
On Mon, Apr 15, 2019 at 04:33:57PM +0300, Dan Carpenter wrote: > On Mon, Apr 15, 2019 at 03:10:02PM +0200, Johan Hovold wrote: > > On Fri, Apr 05, 2019 at 03:14:37PM -0500, Madhumitha Prabakaran wrote: > > > Fix a blank line after function/struct/union/enum > > > declarations. Also, convert

Re: [PATCH] Staging: greybus: Cleanup in header file control.h

2019-04-15 Thread Dan Carpenter
On Mon, Apr 15, 2019 at 03:10:02PM +0200, Johan Hovold wrote: > On Fri, Apr 05, 2019 at 03:14:37PM -0500, Madhumitha Prabakaran wrote: > > Fix a blank line after function/struct/union/enum > > declarations. Also, convert to_gb_control() macro into an inline > > function in order to maintain Linux

Re: [PATCH] Staging: greybus: Cleanup in header file control.h

2019-04-15 Thread Johan Hovold
On Fri, Apr 05, 2019 at 03:14:37PM -0500, Madhumitha Prabakaran wrote: > Fix a blank line after function/struct/union/enum > declarations. Also, convert to_gb_control() macro into an inline > function in order to maintain Linux kernel coding style based > on which the inline function is

Re: [greybus-dev] [PATCH] Staging: greybus: Fix spinlock_t definition without comment

2019-04-15 Thread Johan Hovold
On Fri, Apr 05, 2019 at 05:50:10PM -0500, Alex Elder wrote: > On 4/5/19 3:53 PM, Dan Carpenter wrote: > > On Fri, Apr 05, 2019 at 03:00:46PM -0500, Madhumitha Prabakaran > > wrote: > >> Fix spinlock_t definition without comment. > >> > >> Signed-off-by: Madhumitha Prabakaran > > Madhumitha, the

Re: [PATCH] Staging: greybus: usb: Fixed a coding style error

2019-04-15 Thread Johan Hovold
On Sun, Mar 31, 2019 at 01:30:40AM -0400, Will Cunningham wrote: > Line was >80 characters. > > Signed-off-by: Will Cunningham > --- > drivers/staging/greybus/usb.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/staging/greybus/usb.c

[PATCH v2 2/2] staging: comedi: vmk80xx: Fix possible double-free of ->usb_rx_buf

2019-04-15 Thread Ian Abbott
`vmk80xx_alloc_usb_buffers()` is called from `vmk80xx_auto_attach()` to allocate RX and TX buffers for USB transfers. It allocates `devpriv->usb_rx_buf` followed by `devpriv->usb_tx_buf`. If the allocation of `devpriv->usb_tx_buf` fails, it frees `devpriv->usb_rx_buf`, leaving the pointer set

[PATCH 2/2] staging: comedi: ni_usb6501: Fix possible double-free of ->usb_rx_buf

2019-04-15 Thread Ian Abbott
`ni6501_alloc_usb_buffers()` is called from `ni6501_auto_attach()` to allocate RX and TX buffers for USB transfers. It allocates `devpriv->usb_rx_buf` followed by `devpriv->usb_tx_buf`. If the allocation of `devpriv->usb_tx_buf` fails, it frees `devpriv->usb_rx_buf`, leaving the pointer set

[PATCH 0/2] staging: comedi: ni_usb6501: Fix a couple of bugs

2019-04-15 Thread Ian Abbott
Fix a bug detected by syzbot and another that I found while investigating it. 1) staging: comedi: ni_usb6501: Fix use of uninitialized mutex 2) staging: comedi: ni_usb6501: Fix possible double-free of ->usb_rx_buf drivers/staging/comedi/drivers/ni_usb6501.c | 10 -- 1 file changed, 4

[PATCH 1/2] staging: comedi: ni_usb6501: Fix use of uninitialized mutex

2019-04-15 Thread Ian Abbott
If `ni6501_auto_attach()` returns an error, the core comedi module code will call `ni6501_detach()` to clean up. If `ni6501_auto_attach()` successfully allocated the comedi device private data, `ni6501_detach()` assumes that a `struct mutex mut` contained in the private data has been initialized

RE: [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags

2019-04-15 Thread Alastair D'Silva
> -Original Message- > From: David Laight > Sent: Monday, 15 April 2019 9:04 PM > To: 'Alastair D'Silva' ; 'Petr Mladek' > > Cc: 'Alastair D'Silva' ; 'Jani Nikula' > ; 'Joonas Lahtinen' > ; 'Rodrigo Vivi' ; > 'David Airlie' ; 'Daniel Vetter' ; 'Karsten > Keil' ; 'Jassi Brar' ; 'Tom >

[PATCH 1/2] staging: comedi: vmk80xx: Fix use of uninitialized semaphore

2019-04-15 Thread Ian Abbott
If `vmk80xx_auto_attach()` returns an error, the core comedi module code will call `vmk80xx_detach()` to clean up. If `vmk80xx_auto_attach()` successfully allocated the comedi device private data, `vmk80xx_detach()` assumes that a `struct semaphore limit_sem` contained in the private data has

[PATCH 0/2] staging: comedi: vmk80xx: Fix a couple of bugs

2019-04-15 Thread Ian Abbott
Fix a bug detected by syzbot and another bug that I noticed while investigating the syzbot reported bug. 1) staging: comedi: vmk80xx: Fix use of uninitialized semaphore 2) staging: comedi: vmk80xx: Fix possible double-free of ->usb_rx_buf drivers/staging/comedi/drivers/vmk80xx.c | 8 +++- 1

[PATCH 2/2] staging: comedi: vmk80xx: Fix possible double-free of ->usb_rx_buf

2019-04-15 Thread Ian Abbott
`vmk80xx_alloc_usb_buffers()` is called from `vmk80xx_auto_attach()` to allocate RX and TX buffers for USB transfers. It allocates `devpriv->usb_rx_buf` followed by `devpriv->usb_tx_buf`. If the allocation of `devpriv->usb_tx_buf` fails, it frees `devpriv->usb_rx_buf`, leaving the pointer set

RE: [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags

2019-04-15 Thread David Laight
From: Alastair D'Silva > Sent: 15 April 2019 11:45 ... > > Although I think you'd want a 'no hex' flag to suppress the hex. > > > > Probably more useful flags are ones to suppress the address column. > > This is already supported by the prefix_type parameter - are you proposing > that we

RE: [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line

2019-04-15 Thread David Laight
From: Alastair D'Silva > Sent: 15 April 2019 11:29 ... > I do, and I believe the choice of the output length should be in the hands > of the caller. > > On further thought, it would make more sense to remove the hardcoded list of > sizes and just enforce a power of 2. The function shouldn't

RE: [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line

2019-04-15 Thread Alastair D'Silva
> From: Alastair D'Silva > > Sent: 15 April 2019 11:29 > ... > > I do, and I believe the choice of the output length should be in the > > hands of the caller. > > > > On further thought, it would make more sense to remove the hardcoded > > list of sizes and just enforce a power of 2. The function

RE: [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags

2019-04-15 Thread Alastair D'Silva
> -Original Message- > From: David Laight > Sent: Monday, 15 April 2019 8:21 PM > To: 'Alastair D'Silva' ; 'Petr Mladek' > > Cc: 'Alastair D'Silva' ; 'Jani Nikula' > ; 'Joonas Lahtinen' > ; 'Rodrigo Vivi' ; > 'David Airlie' ; 'Daniel Vetter' ; 'Karsten > Keil' ; 'Jassi Brar' ; 'Tom >

RE: [PATCH 2/4] lib/hexdump.c: Optionally suppress lines of filler bytes

2019-04-15 Thread Alastair D'Silva
> > > On Wed 2019-04-10 13:17:18, Alastair D'Silva wrote: > > > > From: Alastair D'Silva > > > > > > > > Some buffers may only be partially filled with useful data, while > > > > the rest is padded (typically with 0x00 or 0xff). > > > > > > > > This patch introduces flags which allow lines of

RE: [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line

2019-04-15 Thread Alastair D'Silva
> > > On Wed 2019-04-10 13:17:17, Alastair D'Silva wrote: > > > > From: Alastair D'Silva > > > > > > > > With modern high resolution screens, we can display more data, > > > > which makes life a bit easier when debugging. > > > > > > I have quite some doubts about this feature. > > > > > > We

RE: [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags

2019-04-15 Thread David Laight
From: Alastair D'Silva > Sent: 15 April 2019 11:07 ... > In the above example the author only wants the hex output, while in other > situations, both hex & ASCII output is desirable. If you just want ASCII > output, the caller should just use a printk or one of it's wrappers. Hexdump will

RE: [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags

2019-04-15 Thread Alastair D'Silva
> -Original Message- > From: Petr Mladek > Sent: Monday, 15 April 2019 7:24 PM > To: Alastair D'Silva > Cc: 'Alastair D'Silva' ; 'Jani Nikula' > ; 'Joonas Lahtinen' > ; 'Rodrigo Vivi' ; > 'David Airlie' ; 'Daniel Vetter' ; 'Karsten > Keil' ; 'Jassi Brar' ; 'Tom > Lendacky' ; 'David S.

Re: [PATCH 3/4] lib/hexdump.c: Replace ascii bool in hex_dump_to_buffer with flags

2019-04-15 Thread Petr Mladek
On Sat 2019-04-13 09:31:27, Alastair D'Silva wrote: > > -Original Message- > > From: Petr Mladek > > Sent: Saturday, 13 April 2019 12:12 AM > > To: Alastair D'Silva > > Cc: alast...@d-silva.org; Jani Nikula ; > Joonas > > Lahtinen ; Rodrigo Vivi > > ; David Airlie ; Daniel Vetter > > ;

Re: [PATCH 2/4] lib/hexdump.c: Optionally suppress lines of filler bytes

2019-04-15 Thread Petr Mladek
On Sat 2019-04-13 09:28:03, Alastair D'Silva wrote: > > -Original Message- > > From: Petr Mladek > > Sent: Saturday, 13 April 2019 12:04 AM > > To: Alastair D'Silva > > Cc: alast...@d-silva.org; Jani Nikula ; > Joonas > > Lahtinen ; Rodrigo Vivi > > ; David Airlie ; Daniel Vetter > > ;

Re: [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line

2019-04-15 Thread Petr Mladek
On Sat 2019-04-13 09:22:05, Alastair D'Silva wrote: > > -Original Message- > > From: Petr Mladek > > Sent: Friday, 12 April 2019 11:48 PM > > To: Alastair D'Silva > > Cc: alast...@d-silva.org; Jani Nikula ; > Joonas > > Lahtinen ; Rodrigo Vivi > > ; David Airlie ; Daniel Vetter > > ;

Re: [PATCH] staging: android: vsoc: fix copy_from_user overrun

2019-04-15 Thread Dan Carpenter
On Mon, Apr 15, 2019 at 09:32:44AM +0300, Dan Carpenter wrote: > On Sun, Apr 14, 2019 at 05:37:26PM +0200, Vincent Stehlé wrote: > > The `np->permission' structure is smaller than the `np' structure but > > sizeof(*np) worth of data is copied in there. Fix the size passed to > > copy_from_user()

Re: [PATCH] staging: android: vsoc: fix copy_from_user overrun

2019-04-15 Thread Dan Carpenter
On Sun, Apr 14, 2019 at 05:37:26PM +0200, Vincent Stehlé wrote: > The `np->permission' structure is smaller than the `np' structure but > sizeof(*np) worth of data is copied in there. Fix the size passed to > copy_from_user() to avoid overrun. > > Fixes: 3d2ec9dcd5539d42 ("staging: Android: Add