Re: [PATCH v3 0/2] Checkpatch cleanup patches

From: Bryant Boatright

Date: Mon Feb 16 2026 - 03:04:14 EST


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@xxxxxxxxxxxxxxxxxxx.
> > 2. Patch 1: Change definition of parse_result to multi-line definition per
> > feed feedback from gregkh@xxxxxxxxxxxxxxxxxxx.
> > 3. Patch 2: Fix typo in commit message introduced in v2 per feedback from
> > gregkh@xxxxxxxxxxxxxxxxxxx.
> > 4. Remove patch 2 (from v2) as name change was not needed per feedback from
> > gregkh@xxxxxxxxxxxxxxxxxxx.
> > 5. Add changelog for patchset to cover letter per feedback from
> > gregkh@xxxxxxxxxxxxxxxxxxx.
> >
> > Changes in v2:
> > 1. Patch 1: Make enumeration constant names all upper case per feedback from
> > straube.linux@xxxxxxxxx.
> >
> > 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?