From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: Rakhi Sharma <rakhish1994@gmail.com>,
Larry.Finger@lwfinger.net, gregkh@linuxfoundation.org,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 3/3] Staging: rtl8723au: core: rtw_ieee80211: Fixed space and brace coding style issue.
Date: Mon, 01 Feb 2016 07:29:17 -0500 [thread overview]
Message-ID: <wrfjio287gwy.fsf@redhat.com> (raw)
In-Reply-To: <1454261145.7329.58.camel@perches.com> (Joe Perches's message of "Sun, 31 Jan 2016 09:25:45 -0800")
Joe Perches <joe@perches.com> writes:
> On Sun, 2016-01-31 at 09:36 -0500, Jes Sorensen wrote:
>> Rakhi Sharma <rakhish1994@gmail.com> writes:
>> > Fixed the space and brace coding style error.
>> > ERROR: space required before that '='
>> > ERROR: that open brace { should be on the previous line.
>> >
>> > Signed-off-by: Rakhi Sharma <rakhish1994@gmail.com>
>> > ---
>> > drivers/staging/rtl8723au/core/rtw_ieee80211.c | 4 ++--
>> > 1 file changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
>> > b/drivers/staging/rtl8723au/core/rtw_ieee80211.c
>> > index 3b0d782..0c933e4 100644
>> > --- a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
>> > +++ b/drivers/staging/rtl8723au/core/rtw_ieee80211.c
>> > @@ -65,8 +65,8 @@ static u8 WIFI_OFDMRATES[] = {
>> >
>> > int rtw_get_bit_value_from_ieee_value23a(u8 val)
>> > {
>> > - unsigned char dot11_rate_table[] =
>> > - {2, 4, 11, 22, 12, 18, 24, 36, 48, 72, 96, 108, 0};
>> > + unsigned char dot11_rate_table[] = {
>> > + 2, 4, 11, 22, 12, 18, 24, 36, 48, 72, 96, 108, 0};
>> >
>> > int i = 0;
>>
>> This is a great example of checkpatch doing the wrong thing. What you
>> did here was to make the code uglier rather than better.
>>
>> NACK
>
> Here's the original code:
>
> int rtw_get_bit_value_from_ieee_value23a(u8 val)
> {
> unsigned char dot11_rate_table[]=
> {2, 4, 11, 22, 12, 18, 24, 36, 48, 72, 96, 108, 0};
>
> int i = 0;
>
> while (dot11_rate_table[i] != 0) {
> if (dot11_rate_table[i] == val)
> return BIT(i);
> i++;
> }
> return 0;
> }
>
> It has several nominal style defects:
>
> o compares different types (unsigned char to u8)
> o uses a while loop and test of a known sized array
> o array isn't declared static const
> o array initialization is different style from others
> in the same file. "type foo[] = { bar, baz };"
> o the function argument is tested on the right side
> tested on left side is more common.
>
> So this could be transformed into something like:
>
> int rtw_get_bit_value_from_ieee_value23a(u8 val)
> {
> int i;
> static const u8 dot11_rate_table[] = {
> 2, 4, 11, 22, 12, 18, 24, 36, 48, 72, 96, 108
> };
and per my previous email, the above is worse than than the original.
The cleaner way to list it would be:
static const char dot11_rate_table[] =
{ 2, 4, 11, 22, 12, 18, 24, 36, 48, 72, 96, 108 };
Jes
next prev parent reply other threads:[~2016-02-01 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 13:24 [PATCH 3/3] Staging: rtl8723au: core: rtw_ieee80211: Fixed space and brace coding style issue Rakhi Sharma
2016-01-31 14:36 ` Jes Sorensen
2016-01-31 17:25 ` Joe Perches
2016-02-01 12:29 ` Jes Sorensen [this message]
2016-02-01 14:28 ` Joe Perches
2016-02-01 15:02 ` Jes Sorensen
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=wrfjio287gwy.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rakhish1994@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;
as well as URLs for NNTP newsgroup(s).