From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bryant Boatright <bryant.boatright@proton.me>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Checkpatch cleanup patches
Date: Mon, 16 Feb 2026 09:40:49 +0100 [thread overview]
Message-ID: <2026021638-upstroke-creole-52aa@gregkh> (raw)
In-Reply-To: <aZLPXTng0Qg20N-W@ubuntu-desk>
On Mon, Feb 16, 2026 at 08:03:47AM +0000, Bryant Boatright wrote:
> On Wed, Dec 17, 2025 at 02:03:25PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Dec 04, 2025 at 11:44:19AM +0000, Bryant Boatright wrote:
> > > Correct camel case names reported by checkpatch.
> > >
> > > These patches are not required to be applied in any order.
> > >
> > > Changes in v3:
> > > 1. Patch 1: Updated parse_res to parse_result for clearer purpose per
> > > feedback from gregkh@linuxfoundation.org.
> > > 2. Patch 1: Change definition of parse_result to multi-line definition per
> > > feed feedback from gregkh@linuxfoundation.org.
> > > 3. Patch 2: Fix typo in commit message introduced in v2 per feedback from
> > > gregkh@linuxfoundation.org.
> > > 4. Remove patch 2 (from v2) as name change was not needed per feedback from
> > > gregkh@linuxfoundation.org.
> > > 5. Add changelog for patchset to cover letter per feedback from
> > > gregkh@linuxfoundation.org.
> > >
> > > Changes in v2:
> > > 1. Patch 1: Make enumeration constant names all upper case per feedback from
> > > straube.linux@gmail.com.
> > >
> > > Bryant Boatright (2):
> > > staging: rtl8723bs: Rename camel case enumeration
> > > staging: rtl8723bs: Rename camel case variable
> > >
> > > .../staging/rtl8723bs/core/rtw_ieee80211.c | 26 +++++++++----------
> > > drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
> > > drivers/staging/rtl8723bs/include/ieee80211.h | 12 ++++++---
> > > 3 files changed, 22 insertions(+), 18 deletions(-)
> > >
> > > --
> > > 2.43.0
> > >
> > >
> > >
> >
> > These did not come through as properly linked together, how did you send
> > them? Can you use something like 'b4' or 'git send-email' to send them
> > as a patch series, and not as unconnected emails?
> >
> > thanks,
> >
> > greg k-h
> >
>
> Sorry for the delayed response. Yes, I can do that - apologies for not catching
> that on this version.
>
> Would you want that sent as a V4 patch, or just resend this series but correctly
> linked?
V4 series please.
thanks,
greg k-h
prev parent reply other threads:[~2026-02-16 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 11:44 [PATCH v3 0/2] Checkpatch cleanup patches Bryant Boatright
2025-12-17 13:03 ` Greg Kroah-Hartman
2026-02-16 8:03 ` Bryant Boatright
2026-02-16 8:40 ` Greg Kroah-Hartman [this message]
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=2026021638-upstroke-creole-52aa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bryant.boatright@proton.me \
--cc=linux-kernel@vger.kernel.org \
--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