From: Ping-Ke Shih <pkshih@realtek.com>
To: Su Hui <suhui@nfschina.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"trix@redhat.com" <trix@redhat.com>
Cc: "lizetao1@huawei.com" <lizetao1@huawei.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: RE: [PATCH wireless-next 1/2] rtlwifi: rtl8821ae: phy: remove some useless code
Date: Thu, 23 Nov 2023 00:52:17 +0000 [thread overview]
Message-ID: <ea7fc9364f0c4ec8ac9953c6de77bf79@realtek.com> (raw)
In-Reply-To: <20231122090210.951185-1-suhui@nfschina.com>
> -----Original Message-----
> From: Su Hui <suhui@nfschina.com>
> Sent: Wednesday, November 22, 2023 5:02 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; kvalo@kernel.org; nathan@kernel.org; ndesaulniers@google.com;
> trix@redhat.com
> Cc: Su Hui <suhui@nfschina.com>; lizetao1@huawei.com; linux-wireless@vger.kernel.org;
> linux-kernel@vger.kernel.org; llvm@lists.linux.dev; kernel-janitors@vger.kernel.org
> Subject: [PATCH wireless-next 1/2] rtlwifi: rtl8821ae: phy: remove some useless code
subject prefix should be "wifi: rtlwifi: ..."
>
> Clang static checker warning:
> Value stored to 'v1' is never read [deadcode.DeadStores]
> Value stored to 'channel' is never read [deadcode.DeadStores]
>
> Remove them to save some place.
>
> Signed-off-by: Su Hui <suhui@nfschina.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
prev parent reply other threads:[~2023-11-23 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 9:02 [PATCH wireless-next 1/2] rtlwifi: rtl8821ae: phy: remove some useless code Su Hui
2023-11-22 9:02 ` [PATCH wireless-next 2/2] rtlwifi: rtl8821ae: phy: fix an undefined bitwise shift behavior Su Hui
2023-11-22 13:02 ` Dan Carpenter
2023-11-23 0:41 ` Ping-Ke Shih
2023-11-23 1:34 ` Su Hui
2023-11-23 1:33 ` Su Hui
2023-11-23 5:48 ` Dan Carpenter
2023-11-23 0:52 ` Ping-Ke Shih [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=ea7fc9364f0c4ec8ac9953c6de77bf79@realtek.com \
--to=pkshih@realtek.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lizetao1@huawei.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=suhui@nfschina.com \
--cc=trix@redhat.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