From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yuho Choi <dbgh9129@gmail.com>
Cc: linux-staging@lists.linux.dev, Hans de Goede <hansg@kernel.org>,
Michael Straube <straube.linux@gmail.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Minu Jin <s9430939@naver.com>, Ingo Molnar <mingo@kernel.org>,
Ethan Tidmore <ethantidmore06@gmail.com>,
William Hansen-Baird <william.hansen.baird@gmail.com>,
linux-kernel@vger.kernel.org, Myeonghun Pak <mhun512@gmail.com>,
Ijae Kim <ae878000@gmail.com>, Taegyu Kim <tmk5904@psu.edu>
Subject: Re: [PATCH v1] staging: rtl8723bs: remove shadowed bDumpRxPkt declaration
Date: Mon, 20 Apr 2026 12:03:14 +0200 [thread overview]
Message-ID: <2026042020-yodel-educator-1c7b@gregkh> (raw)
In-Reply-To: <20260420030543.72423-1-dbgh9129@gmail.com>
On Sun, Apr 19, 2026 at 11:05:43PM -0400, Yuho Choi wrote:
> DBG_RX_DUMP_EAP redeclares bDumpRxPkt inside validate_recv_frame(),
> shadowing the existing function-local variable. Drop the inner declaration
> and reuse the existing variable to avoid unnecessary shadowing.
>
> Co-developed-by: Myeonghun Pak <mhun512@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Co-developed-by: Taegyu Kim <tmk5904@psu.edu>
> Signed-off-by: Taegyu Kim <tmk5904@psu.edu>
> Signed-off-by: Yuho Choi <dbgh9129@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_recv.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
> index 337671b1211f0..cf5698dda91fc 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_recv.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_recv.c
> @@ -1534,7 +1534,6 @@ static signed int validate_recv_frame(struct adapter *adapter, union recv_frame
> precvpriv->rx_drop++;
> } else if (retval == _SUCCESS) {
> #ifdef DBG_RX_DUMP_EAP
> - u8 bDumpRxPkt;
If you trace this back, why is this variable being used at all? Look at
how it is being used, and please explain the logic here.
Personally, I think this can be deleted entirely, but please verify
this.
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-20 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 3:05 [PATCH v1] staging: rtl8723bs: remove shadowed bDumpRxPkt declaration Yuho Choi
2026-04-20 8:25 ` Andy Shevchenko
2026-04-20 10:03 ` Greg Kroah-Hartman [this message]
2026-04-20 22:08 ` Ethan Tidmore
2026-04-20 23:00 ` 최유호
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=2026042020-yodel-educator-1c7b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ae878000@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=dbgh9129@gmail.com \
--cc=ethantidmore06@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mhun512@gmail.com \
--cc=mingo@kernel.org \
--cc=s9430939@naver.com \
--cc=straube.linux@gmail.com \
--cc=tmk5904@psu.edu \
--cc=william.hansen.baird@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