[PATCH] staging: lustre: lmv: mark symbols static where possible

2016-09-17 Thread Baoyou Xie
We get a few warnings when building kernel with W=1: drivers/staging/lustre/lustre/lmv/lmv_obd.c:1640:1: warning: no previous prototype for 'lmv_locate_target_for_name' [-Wmissing-prototypes] drivers/staging/lustre/lustre/lmv/lmv_obd.c:2421:5: warning: no previous prototype for 'lmv_read_page' [-

[PATCH] staging/lustre: clean function declaration in cl_io.c up

2016-09-17 Thread Baoyou Xie
We get 1 warning when building kernel with W=1: drivers/staging/lustre/lustre/obdclass/cl_page.c:488:6: warning: no previous prototype for 'cl_page_disown0' [-Wmissing-prototypes] In fact, this function is declared in drivers/staging/lustre/lustre/obdclass/cl_io.c, but should be removed in a head

[PATCH] staging: lustre: obdclass: clean function declarations in obd_config.c and class_obd.c up

2016-09-17 Thread Baoyou Xie
We get 3 warnings when building kernel with W=1: drivers/staging/lustre/lustre/obdclass/obd_mount.c:705:5: warning: no previous prototype for 'lustre_check_exclusion' [-Wmissing-prototypes] drivers/staging/lustre/lustre/obdclass/obd_mount.c:1226:5: warning: no previous prototype for 'lustre_regi

[PATCH] staging/lustre: clean function declaration in super25.c up

2016-09-17 Thread Baoyou Xie
We get 1 warning when building kernel with W=1: drivers/staging/lustre/lustre/obdclass/obd_config.c:719:6: warning: no previous prototype for 'lustre_register_client_process_config' [-Wmissing-prototypes] In fact, this function is declared in drivers/staging/lustre/lustre/llite/super25.c, but sho

[PATCH] staging: lustre: clean function declaration in super25.c up

2016-09-17 Thread Baoyou Xie
We get 1 warning when building kernel with W=1: drivers/staging/lustre/lnet/selftest/conctl.c:804:1: warning: no previous prototype for 'lstcon_ioctl_entry' [-Wmissing-prototypes] In fact, this function is declared in drivers/staging/lustre/lustre/llite/super25.c, but should be moved into a heade

[PATCH] rtl8xxxu: Stop log spam from each successful interrupt

2016-09-17 Thread Larry Finger
As soon as debugging is turned on, the logs are filled with messages reporting the interrupt status. As this quantity is usually zero, this output is not needed. In fact, there will be a report if the status is not zero, thus the debug line in question could probably be deleted. Rather than taking

Re: [PATCH] rtl8xxxu: Stop log spam from each successful interrupt

2016-09-17 Thread Joe Perches
On Sat, 2016-09-17 at 12:09 -0500, Larry Finger wrote: > As soon as debugging is turned on, the logs are filled with messages > reporting the interrupt status. As this quantity is usually zero, this > output is not needed. In fact, there will be a report if the status is > not zero, thus the debug

Re: [PATCHv2] staging: wlan-ng: if statement style cleanup

2016-09-17 Thread Greg Kroah-Hartman
On Fri, Sep 16, 2016 at 10:42:21AM -0400, Jon Eyolfson wrote: > Changed if statement bodies from 2 levels deeper than if statement to 1. > > Signed-off-by: Jon Eyolfson > --- > drivers/staging/wlan-ng/cfg80211.c | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/dr

[PATCH] Staging: dgnc: dgnc_tty: fixed a line too long style issue

2016-09-17 Thread Cathal Mullaney
Fixed a coding style issue. Signed-off-by: Cathal Mullaney --- drivers/staging/dgnc/dgnc_tty.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c index 31b18e6..fd46ef0 100644 --- a/drivers/staging/dgnc/dgnc_tty

Re: [PATCH] rtl8xxxu: Stop log spam from each successful interrupt

2016-09-17 Thread Jes Sorensen
Joe Perches writes: > On Sat, 2016-09-17 at 12:09 -0500, Larry Finger wrote: >> As soon as debugging is turned on, the logs are filled with messages >> reporting the interrupt status. As this quantity is usually zero, this >> output is not needed. In fact, there will be a report if the status is >

Re: [PATCH] rtl8xxxu: Stop log spam from each successful interrupt

2016-09-17 Thread Jes Sorensen
Larry Finger writes: > As soon as debugging is turned on, the logs are filled with messages > reporting the interrupt status. As this quantity is usually zero, this > output is not needed. In fact, there will be a report if the status is > not zero, thus the debug line in question could probably b

[PATCH] Staging: octeon: ethernet-rx: fixed three redundant blank line style issues

2016-09-17 Thread Cathal Mullaney
Fixed three minor coding style issues. Signed-off-by: Cathal Mullaney --- drivers/staging/octeon/ethernet-rx.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/staging/octeon/ethernet-rx.c b/drivers/staging/octeon/ethernet-rx.c index ce1e2a3..f0900d1 100644 --- a/drivers/staging/oc

Re: [PATCH] rtl8xxxu: Stop log spam from each successful interrupt

2016-09-17 Thread Larry Finger
On 09/17/2016 03:59 PM, Jes Sorensen wrote: Larry Finger writes: As soon as debugging is turned on, the logs are filled with messages reporting the interrupt status. As this quantity is usually zero, this output is not needed. In fact, there will be a report if the status is not zero, thus the

[PATCHv3] staging: wlan-ng: if statement style cleanup

2016-09-17 Thread Jon Eyolfson
Changed if statement bodies from 2 levels deeper than if statement to 1. Signed-off-by: Jon Eyolfson --- drivers/staging/wlan-ng/cfg80211.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/wlan-ng/cfg80211.c b/drivers/staging/wlan-ng/cfg80211.c index a