From: Joe Perches <joe@perches.com>
To: Pedro Marzo Perez <marzo.pedro@gmail.com>
Cc: gregkh@linuxfoundation.org, navyasri.tech@gmail.com,
dilekuzulmez@gmail.com, haticeerturk27@gmail.com,
senija.stanojevic@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixed coding style issues at ieee80211_crypt_wep.c
Date: Fri, 15 May 2015 23:56:41 -0700 [thread overview]
Message-ID: <1431759401.15709.65.camel@perches.com> (raw)
In-Reply-To: <1431765608-3658-1-git-send-email-marzo.pedro@gmail.com>
On Sat, 2015-05-16 at 10:40 +0200, Pedro Marzo Perez wrote:
> This patch just fixes some warnings and style errors reported by checkpatch.pl script
> - Braces should not start in a new line
> - C99 comments are not allowed (never use //)
> - Literal strings should never be parted in several lines
> - There was a useless return on a void function
Some will say this is doing too many things in a single patch.
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
[]
> + pr_debug("ieee80211_crypt_wep: could not allocate crypto API arc4\n");
[]
> + pr_debug("ieee80211_crypt_wep: could not allocate crypto API arc4\n");
These could use a pr_fmt prefix and the "ieee80211_crypt_wep: "
could be removed.
In fact, these could be consolidated into a single line if
moved into the fail block if the first allocation does
a direct return NULL instead of goto fail.
> @@ -293,6 +288,5 @@ void __exit ieee80211_crypto_wep_exit(void)
>
> void ieee80211_wep_null(void)
> {
> -// printk("============>%s()\n", __func__);
> - return;
> + /*printk("============>%s()\n", __func__);*/
Just delete this instead.
> }
next prev parent reply other threads:[~2015-05-16 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 8:40 [PATCH] Fixed coding style issues at ieee80211_crypt_wep.c Pedro Marzo Perez
2015-05-16 6:56 ` Joe Perches [this message]
2015-05-18 8:33 ` Dan Carpenter
2015-05-18 17:32 ` pmarzo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431759401.15709.65.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=dilekuzulmez@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=haticeerturk27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marzo.pedro@gmail.com \
--cc=navyasri.tech@gmail.com \
--cc=senija.stanojevic@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox