From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: gregkh@linuxfoundation.org,
Michael Straube <straube.linux@gmail.com>,
Joe Perches <joe@perches.com>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
martin@kaiser.cx, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] staging: r8188eu: refactor rtw_is_cckrates_included()
Date: Mon, 16 Aug 2021 14:59:37 +0200 [thread overview]
Message-ID: <22319347.s0ZA6q4zN9@localhost.localdomain> (raw)
In-Reply-To: <20210816115430.28264-1-straube.linux@gmail.com>
On Monday, August 16, 2021 1:54:27 PM CEST Michael Straube wrote:
> Refactor function rtw_is_cckrates_included(). Improves readability
> and slightly reduces object file size.
>
> Signed-off-by: Michael Straube <straube.linux@gmail.com>
> ---
> v1 -> v2
> Refactored to more compact code as suggested by Joe Perches.
>
> drivers/staging/r8188eu/core/rtw_ieee80211.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
Thanks for redoing the series as suggested by Joe Perches.
This is a perfect case where conciseness and readability don't clash and
instead the former enhances the latter.
Nice work, although you chose to not take Joe's suggestion about making a
helper inline function. That would have been perfect, but I think it is a
minor issue. So...
Acked-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Regards,
Fabio
P.S.: If I were you, I'd have provided a cover letter that would have helped
the readers to immediately understand the purpose of the entire series. I'm
not sure whether or not the above-mentioned cover is a strict requirement.
> diff --git a/drivers/staging/r8188eu/core/rtw_ieee80211.c
> b/drivers/staging/r8188eu/core/rtw_ieee80211.c index 0c7231cefdda..
964255a8c778 100644
> --- a/drivers/staging/r8188eu/core/rtw_ieee80211.c
> +++ b/drivers/staging/r8188eu/core/rtw_ieee80211.c
> @@ -70,14 +70,13 @@ int rtw_get_bit_value_from_ieee_value(u8 val)
>
> uint rtw_is_cckrates_included(u8 *rate)
> {
> - u32 i = 0;
> + u8 r;
>
> - while (rate[i] != 0) {
> - if ((((rate[i]) & 0x7f) == 2) || (((rate[i]) & 0x7f)
== 4) ||
> - (((rate[i]) & 0x7f) == 11) || (((rate[i]) & 0x7f)
== 22))
> + while ((r = *rate++ & 0x7f)) {
> + if (r == 2 || r == 4 || r == 11 || r == 22)
> return true;
> - i++;
> }
> +
> return false;
> }
next prev parent reply other threads:[~2021-08-16 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 11:54 [PATCH v2 1/4] staging: r8188eu: refactor rtw_is_cckrates_included() Michael Straube
2021-08-16 11:54 ` [PATCH v2 2/4] staging: r8188eu: convert rtw_is_cckrates_included() to bool Michael Straube
2021-08-16 13:01 ` Fabio M. De Francesco
2021-08-16 11:54 ` [PATCH v2 3/4] staging: r8188eu: refactor rtw_is_cckratesonly_included() Michael Straube
2021-08-16 13:03 ` Fabio M. De Francesco
2021-08-16 11:54 ` [PATCH v2 4/4] staging: r8188eu: convert rtw_is_cckratesonly_included() to bool Michael Straube
2021-08-16 13:04 ` Fabio M. De Francesco
2021-08-16 12:59 ` Fabio M. De Francesco [this message]
2021-08-16 16:15 ` [PATCH v2 1/4] staging: r8188eu: refactor rtw_is_cckrates_included() Joe Perches
2021-08-16 16:29 ` Michael Straube
2021-08-16 19:36 ` Michael Straube
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=22319347.s0ZA6q4zN9@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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