linux-kernel - Re: [PATCH] staging: wlan-ng: Made into two lines

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] [day] [month] [year] [list]

Message-ID: <20150813183551.GA24496@kroah.com>
Date:	Thu, 13 Aug 2015 11:35:51 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Aparna Karuthodi <kdasaparna@...il.com>
Cc:	johannes.berg@...el.com, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: wlan-ng: Made into two lines

On Thu, Aug 13, 2015 at 11:44:23PM +0530, Aparna Karuthodi wrote:
> Broke the line into two lines to remove a coding style warning detected
> by checkpatch.
> 
> The warning is given below:
> drivers/staging/wlan-ng/cfg80211.c:755: WARNING: line over 80
> characters
> 
> Signed-off-by: Aparna Karuthodi <kdasaparna@...il.com>
> ---
>  drivers/staging/wlan-ng/cfg80211.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/wlan-ng/cfg80211.c b/drivers/staging/wlan-ng/cfg80211.c
> index 7c87aec..53e0681 100644
> --- a/drivers/staging/wlan-ng/cfg80211.c
> +++ b/drivers/staging/wlan-ng/cfg80211.c
> @@ -752,7 +752,8 @@ static const struct cfg80211_ops prism2_usb_cfg_ops = {
>  
>  
>  /* Functions to create/free wiphy interface */
> -static struct wiphy *wlan_create_wiphy(struct device *dev, wlandevice_t *wlandev)
> +static struct wiphy *wlan_create_wiphy(struct device *dev,
> +wlandevice_t *wlandev)

Does that look correct?

--
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/