From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-staging@lists.linux.dev>
Subject: [PATCH v2 0/4] staging: fix warning of -Wunused-but-set-variable reported by clang
Date: Fri, 13 Sep 2024 08:28:11 +0800 [thread overview]
Message-ID: <20240913002815.5149-1-pkshih@realtek.com> (raw)
The build of wireless-next pull-request using clang report warnings [1].
Fix them accordingly.
[1] https://lore.kernel.org/linux-wireless/172609384625.1065358.6518424528532813444.git-patchwork-notify@kernel.org/T/#m405a10ad637bfc5f337127bab81336d8569e49cd
v2:
- rebase to top of staging tree to resolve conflict of patch 2/4.
- no logic change.
Ping-Ke Shih (4):
staging: rtl8712: remove unused drvinfo_sz from
update_recvframe_attrib
staging: rtl8723bs: remove unused efuseValue from efuse_OneByteWrite()
staging: rtl8723bs: remove unused cnt from recv_func()
staging: rtl8723bs: remove unused 'poll_cnt' from rtw_set_rpwm()
drivers/staging/rtl8712/rtl8712_recv.c | 4 ----
drivers/staging/rtl8723bs/core/rtw_efuse.c | 9 ---------
drivers/staging/rtl8723bs/core/rtw_pwrctrl.c | 2 --
drivers/staging/rtl8723bs/core/rtw_recv.c | 5 +----
4 files changed, 1 insertion(+), 19 deletions(-)
--
2.25.1
next reply other threads:[~2024-09-13 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 0:28 Ping-Ke Shih [this message]
2024-09-13 0:28 ` [PATCH v2 1/4] staging: rtl8712: remove unused drvinfo_sz from update_recvframe_attrib Ping-Ke Shih
2024-09-13 0:28 ` [PATCH v2 2/4] staging: rtl8723bs: remove unused efuseValue from efuse_OneByteWrite() Ping-Ke Shih
2024-09-13 0:28 ` [PATCH v2 3/4] staging: rtl8723bs: remove unused cnt from recv_func() Ping-Ke Shih
2024-09-13 0:28 ` [PATCH v2 4/4] staging: rtl8723bs: remove unused 'poll_cnt' from rtw_set_rpwm() Ping-Ke Shih
2024-09-13 4:48 ` [PATCH v2 0/4] staging: fix warning of -Wunused-but-set-variable reported by clang Philipp Hortmann
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=20240913002815.5149-1-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-staging@lists.linux.dev \
/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