Re: [PATCH 1/4] staging: rtl8723bs: update TODO list for completed cleanups
From: Greg KH <gregkh@linuxfoundation.org>
Date: 2026-09-09 07:42:15
Also in:
lkml
On Tue, Sep 08, 2026 at 09:34:27PM +0300, AJ39210 wrote:
quoted hunk ↗ jump to hunk
Signed-off-by: AJ39210 <redacted> --- drivers/staging/rtl8723bs/TODO | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-)diff --git a/drivers/staging/rtl8723bs/TODO b/drivers/staging/rtl8723bs/TODO index 34c216e6d..8de062b47 100644 --- a/drivers/staging/rtl8723bs/TODO +++ b/drivers/staging/rtl8723bs/TODO@@ -1,7 +1,10 @@ TODO: -- find and remove any code for other chips that is left over -- convert any remaining unusual variable types -- checkpatch.pl fixes - most of the remaining ones are lines too long. Many - of them will require refactoring -- merge Realtek's bugfixes and new features into the driver -- switch to use MAC80211 +- Partial: remove remaining code for other chips that is left over. Unused + non-8723B AMPDU burst enum values and unused 8188E ODM fields have been + removed, but more legacy code remains. +- Partial: convert unusual variable types. The channel control APIs and rate + helpers now use kernel fixed-width types, but more legacy types remain. +- Partial checkpatch.pl fixes: several overlong callback and scan-list lines + have been wrapped, but many warnings remain and will require refactoring. +- Merge Realtek's bugfixes and new features into the driver. +- Switch to use MAC80211.-- 2.55.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: - You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what is needed in order to properly describe the change. - You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what a proper Subject: line should look like. - It looks like you did not use your "real" name for the patch on either the Signed-off-by: line, or the From: line (both of which have to match). Please read the kernel file, Documentation/process/submitting-patches.rst for how to do this correctly. 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