From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Saurav Girepunje <saurav.girepunje@gmail.com>,
linux-staging@lists.linux.dev
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Remove redundant initialization of variable efuseValue
Date: Tue, 4 Oct 2022 23:12:15 +0200 [thread overview]
Message-ID: <b82e784d-f4c5-10df-2bcb-ee69b0f4a317@gmail.com> (raw)
In-Reply-To: <20221004153539.150867-1-colin.i.king@gmail.com>
On 10/4/22 17:35, Colin Ian King wrote:
> The variable efuseValue is being initialized with a value that is never
> read. The variable is being re-assigned later on. The initialization is
> redundant and can be removed.
>
> Cleans up warning:
> drivers/staging/rtl8723bs/core/rtw_efuse.c:285:6: warning: variable
> 'efuseValue' set but not used [-Wunused-but-set-variable]
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_efuse.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_efuse.c b/drivers/staging/rtl8723bs/core/rtw_efuse.c
> index 06e727ce9cc2..eb848f9bbf2c 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_efuse.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_efuse.c
> @@ -282,7 +282,7 @@ u8 efuse_OneByteWrite(struct adapter *padapter, u16 addr, u8 data, bool bPseudoT
> {
> u8 tmpidx = 0;
> u8 bResult = false;
> - u32 efuseValue = 0;
> + u32 efuseValue;
>
> if (bPseudoTest)
> return Efuse_Write1ByteToFakeContent(addr, data);
I propose to remove all lines with efuseValue as it is dead code.
Make a v2 of this patch with version history below the ---
Thanks for your support.
Bye Philipp
prev parent reply other threads:[~2022-10-04 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 15:35 Colin Ian King
2022-10-04 21:12 ` Philipp Hortmann [this message]
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=b82e784d-f4c5-10df-2bcb-ee69b0f4a317@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=saurav.girepunje@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
all inboxes | Powered by JetHome®