From: Dorine Tipo <dorine.a.tipo@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
outreachy@lists.linux.dev
Cc: Dorine Tipo <dorine.a.tipo@gmail.com>
Subject: [PATCH v2] staging: vt6655: Remove unused function RFbAL7230SelectChannelPostProcess
Date: Mon, 11 Mar 2024 03:56:49 +0000 [thread overview]
Message-ID: <20240311035649.25043-1-dorine.a.tipo@gmail.com> (raw)
In-Reply-To: <20240311015601.17428-1-dorine.a.tipo@gmail.com>
Remove RFbAL7230SelectChannelPostProcess as it is dead code.
This commit removes the dead code to improve code cleanliness and reduce
unnecessary complexity in the driver.
Signed-off-by: Dorine Tipo <dorine.a.tipo@gmail.com>
---
Changes since V1:
- Removed unintended blank line introduced after removing dead code
drivers/staging/vt6655/rf.h | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/vt6655/rf.h b/drivers/staging/vt6655/rf.h
index 057860a5e100..3427341e581f 100644
--- a/drivers/staging/vt6655/rf.h
+++ b/drivers/staging/vt6655/rf.h
@@ -68,9 +68,5 @@ bool RFbRawSetPower(struct vnt_private *priv, unsigned char byPwr,
void RFvRSSITodBm(struct vnt_private *priv, unsigned char byCurrRSSI,
long *pldBm);
-/* {{ RobertYu: 20050104 */
-bool RFbAL7230SelectChannelPostProcess(struct vnt_private *priv, u16 byOldChannel,
- u16 byNewChannel);
-/* }} RobertYu */
#endif /* __RF_H__ */
--
2.25.1
next prev parent reply other threads:[~2024-03-11 4:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 1:56 [PATCH] staging: vt6655: Remove unused function from rf.h RFbAL7230SelectChannelPostProcess Dorine Tipo
2024-03-11 3:56 ` Dorine Tipo [this message]
2024-03-11 5:46 ` [PATCH v2] staging: vt6655: Remove unused function RFbAL7230SelectChannelPostProcess Dan Carpenter
2024-03-11 6:07 ` [PATCH v3] " Dorine Tipo
2024-03-11 7:31 ` Dan Carpenter
2024-03-14 5:33 ` Philipp Hortmann
2024-03-14 6:36 ` Dan Carpenter
2024-03-14 18:45 ` Philipp Hortmann
2024-03-15 5:00 ` Bagas Sanjaya
2024-03-16 13:33 ` Philipp Hortmann
2024-03-16 16:10 ` Dan Carpenter
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=20240311035649.25043-1-dorine.a.tipo@gmail.com \
--to=dorine.a.tipo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).