public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Te-Hsiu Huang <tehsiu.huang@gmail.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	Joe Perches <joe@perches.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: refactor BSS Coexistence channel report logic
Date: Thu, 29 Jan 2026 15:14:44 +0100	[thread overview]
Message-ID: <2026012949-scorpion-handgun-433d@gregkh> (raw)
In-Reply-To: <CAMbZB6NhWzPhNB2fiyxyNoqd+=y93JYp0NdQykyEgsL9=qT7-Q@mail.gmail.com>

On Thu, Jan 29, 2026 at 01:54:37AM -0800, Te-Hsiu Huang wrote:
> On Thu, Jan 29, 2026 at 12:54 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> 
> > That's a lot of different things all in one single patch.  SHouldn't
> > this be split up into different ones?
> I kept these changes in one patch because they all work together to
> replace the old ICS logic and remove the magic numbers. Splitting them
> might break the build or make the code inconsistent halfway through.
> I was suggested renaming and using a bool array structure in the
> earlier patch here:
> https://lore.kernel.org/all/e87acd109ea5eb4e3f8fc233788cd0dbd128407d.camel@perches.com/
> I kept the 2D structure to maintain parity with the IEEE 802.11 spec
> as original implementation. It makes the code semantically correct and
> easier to extend for other Operating Classes in the future.
> 
> > And did you use AI to generate this patch?
> I used AI tools to polish the language of my commit message and to
> perform a parity check, ensuring the refactored boolean logic is
> functionally identical to the original code.

Then as per our development rules, you must document this properly.
Please read and follow them for when you resubmit this.

> 
> > Also, how was this tested?  What prompted you to want to make this
> > change in the first place?
> The patch was tested by:
> 1. Cross-compile the module for the rtl8723bs driver (make
> M=drivers/staging/rtl8723bs) to ensure no build regressions.
> 2. Ran it through scripts/checkpatch.pl to confirm it meets kernel
> coding standards.
> 3. Since I do not have the physical hardware, I performed a manual
> check (by AI verification) to ensure the logic remains identical.

AI can not "verify" anything, you must always check that, sorry.

greg k-h

  reply	other threads:[~2026-01-29 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 20:45 [PATCH] staging: rtl8723bs: refactor BSS Coexistence channel report logic Michael Huang
2026-01-29  6:55 ` Dan Carpenter
2026-01-29  8:01   ` [PATCH v2] " Michael Huang
2026-01-29  8:54     ` Greg Kroah-Hartman
2026-01-29  9:54       ` Te-Hsiu Huang
2026-01-29 14:14         ` Greg Kroah-Hartman [this message]
2026-01-29 18:46           ` Te-Hsiu Huang
2026-01-30  8:30     ` Dan Carpenter
2026-01-30  9:46       ` Te-Hsiu Huang
2026-01-29  8:05   ` [PATCH] " Te-Hsiu Huang

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=2026012949-scorpion-handgun-433d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=tehsiu.huang@gmail.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