From: Dan Carpenter <dan.carpenter@oracle.com>
To: MAACHE Mehdi <mehdi.maache@gmail.com>
Cc: greg@kroah.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, Tracey Dent <tdent48227@gmail.com>
Subject: Re: [PATCH] Staging: rtl8187se: fixed some checkpatch warnings and errors in r8180_wx.c
Date: Tue, 20 Nov 2012 17:25:04 +0300 [thread overview]
Message-ID: <20121120142504.GC11248@mwanda> (raw)
In-Reply-To: <1353418002-8254-1-git-send-email-mehdi.maache@gmail.com>
On Tue, Nov 20, 2012 at 02:26:42PM +0100, MAACHE Mehdi wrote:
> This is a patch to the r8180_wx.c file that fixes up some warnings and errors found by the checkpatch.pl tool
> - WARNING: line over 80 characters
> - ERROR: "(foo*)" should be "(foo *)"
> - ERROR: "foo* bar" should be "foo *bar"
> - ERROR: trailing whitespace
> - ERROR: that open brace { should be on the previous line
>
This needs to be broken into 4-5 separate patches and sent as
series. One patch per warning type.
> - if (erq->flags & IW_ENCODE_DISABLED)
> -
> - if (erq->length > 0) {
> - u32* tkey = (u32*) key;
> + if ((erq->flags & IW_ENCODE_DISABLED) && erq->length > 0) {
> + u32 *tkey = (u32 *) key;
Interesting... You have preserved the meaning of the original code,
but actually the original code is buggy. Just delete the
"if (erq->flags & IW_ENCODE_DISABLED)" check. This bug was
introduced in de171bd6ff "Staging: rtl8187se: r8180_wx: fixed a lot
of checkptahc.pl issues".
Send that as a separate patch and mark it as a bugfix.
regards,
dan carpenter
next prev parent reply other threads:[~2012-11-20 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 13:26 [PATCH] Staging: rtl8187se: fixed some checkpatch warnings and errors in r8180_wx.c MAACHE Mehdi
2012-11-20 14:25 ` Dan Carpenter [this message]
2012-11-21 10:13 ` MAACHE Mehdi
-- strict thread matches above, loose matches on Subject: below --
2012-11-09 15:15 Mehdi Maache
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=20121120142504.GC11248@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mehdi.maache@gmail.com \
--cc=tdent48227@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.