From: Greg KH <gregkh@linuxfoundation.org>
To: Mashiro Chen <mashiro.chen@mailbox.org>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v2] staging: rtl8723bs: remove unused RTL8188E antenna selection macros
Date: Tue, 31 Mar 2026 07:02:24 +0200 [thread overview]
Message-ID: <2026033111-jittery-written-63e0@gregkh> (raw)
In-Reply-To: <20260331045738.84449-1-mashiro.chen@mailbox.org>
On Tue, Mar 31, 2026 at 12:57:38PM +0800, Mashiro Chen wrote:
> Remove the SET_TX_DESC_ANTSEL_{A,B,C}_88E macros from odm_types.h.
> These are leftover dead code for the RTL8188E chip and have no callers
> in the rtl8723bs driver. The RTL8188E is a different chip family and
> has its own driver at drivers/net/wireless/realtek/rtl8xxxu
>
> This addresses the TODO item "find and remove any code for other chips
> that is left over".
>
> Signed-off-by: Mashiro Chen <mashiro.chen@mailbox.org>
> ---
> drivers/staging/rtl8723bs/hal/odm_types.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/odm_types.h b/drivers/staging/rtl8723bs/hal/odm_types.h
> index 8168dc14e8796..0da662e1493a6 100644
> --- a/drivers/staging/rtl8723bs/hal/odm_types.h
> +++ b/drivers/staging/rtl8723bs/hal/odm_types.h
> @@ -36,10 +36,6 @@ enum hal_status {
> #define STA_INFO_T struct sta_info
> #define PSTA_INFO_T struct sta_info *
>
> - #define SET_TX_DESC_ANTSEL_A_88E(__pTxDesc, __Value) SET_BITS_TO_LE_4BYTE(__pTxDesc+8, 24, 1, __Value)
> - #define SET_TX_DESC_ANTSEL_B_88E(__pTxDesc, __Value) SET_BITS_TO_LE_4BYTE(__pTxDesc+8, 25, 1, __Value)
> - #define SET_TX_DESC_ANTSEL_C_88E(__pTxDesc, __Value) SET_BITS_TO_LE_4BYTE(__pTxDesc+28, 29, 1, __Value)
> -
> /* define useless flag to avoid compile warning */
> #define USE_WORKITEM 0
> #define FPGA_TWO_MAC_VERIFICATION 0
> --
> 2.53.0
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2026-03-31 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 4:00 [PATCH] staging: rtl8723bs: remove unused RTL8188E antenna selection macros Mashiro Chen
2026-03-31 4:57 ` [PATCH v2] " Mashiro Chen
2026-03-31 5:02 ` Greg KH [this message]
2026-03-31 5:04 ` [PATCH v3] " Mashiro Chen
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=2026033111-jittery-written-63e0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mashiro.chen@mailbox.org \
/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