From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bruce Ou <oubruce1234@gmail.com>
Cc: Dan Carpenter <error27@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] staging: rtl8723bs: fix CamelCase warning for bResult
Date: Tue, 7 Jul 2026 12:27:03 +0200 [thread overview]
Message-ID: <2026070739-poem-scale-6118@gregkh> (raw)
In-Reply-To: <20260623120815.14737-2-oubruce1234@gmail.com>
On Tue, Jun 23, 2026 at 08:08:13PM +0800, Bruce Ou wrote:
> Fix the coding style warning reported by checkpatch.pl regarding
> the CamelCase local variable bResult by renaming it to result.
>
> No functional changes are introduced.
>
> Signed-off-by: Bruce Ou <oubruce1234@gmail.com>
> ---
> Changes in v2:
> - Split from a single comprehensive patch into a standalone patch.
>
> drivers/staging/rtl8723bs/core/rtw_efuse.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_efuse.c b/drivers/staging/rtl8723bs/core/rtw_efuse.c
> index a40d6eab7249..4bf205e078e7 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_efuse.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_efuse.c
> @@ -89,7 +89,7 @@ u16 addr,
> u8 *data)
> {
> u32 tmpidx = 0;
> - u8 bResult;
> + u8 result;
Why isn't this a boolean variable now?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-07 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 12:08 [PATCH v2 0/3] staging: rtl8723bs: clean up CamelCase style warnings Bruce Ou
2026-06-23 12:08 ` [PATCH v2 1/3] staging: rtl8723bs: fix CamelCase warning for bResult Bruce Ou
2026-07-07 10:27 ` Greg Kroah-Hartman [this message]
2026-06-23 12:08 ` [PATCH v2 2/3] staging: rtl8723bs: fix CamelCase warning for Address Bruce Ou
2026-06-23 12:08 ` [PATCH v2 3/3] staging: rtl8723bs: fix remaining CamelCase local variables Bruce Ou
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=2026070739-poem-scale-6118@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=oubruce1234@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