linux-kernel - Re: [PATCH 1/2] staging: wlan-ng/hfa384x_usb.c: remove return statements for void function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Jun 2014 08:28:40 -0700
From:	Joe Perches <joe@...ches.com>
To:	Cheng-Wei Lee <lee.rhapsody@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sherif Shehab Aldin <shehabaldin.sherif@...il.com>,
	Avinash Kumar <avi.kp.137@...il.com>,
	Peter Senna Tschudin <peter.senna@...il.com>,
	devel <devel@...verdev.osuosl.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] staging: wlan-ng/hfa384x_usb.c: remove return
 statements for void function

On Wed, 2014-06-25 at 23:24 +0800, Cheng-Wei Lee wrote:
> This patch fixes the following checkpatch.pl issues in hfa384x_usb.c:
> WARNING: void function return statements are not generally useful

subject/code mismatch.

> Signed-off-by: Quentin Lee <lee.rhapsody@...il.com>
> ---
>  drivers/staging/wlan-ng/hfa384x_usb.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c
> b/drivers/staging/wlan-ng/hfa384x_usb.c
> index 98343ff7..07cee56 100644
> --- a/drivers/staging/wlan-ng/hfa384x_usb.c
> +++ b/drivers/staging/wlan-ng/hfa384x_usb.c
> @@ -3705,6 +3705,7 @@ static void hfa384x_usbout_callback(struct urb *urb)
>  		case -EPIPE:
>  			{
>  				hfa384x_t *hw = wlandev->priv;
> +
>  				netdev_warn(hw->wlandev->netdev,
>  					    "%s tx pipe stalled: requesting reset\n",
>  					    wlandev->netdev->name);



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/