From: Greg KH <gregkh@linuxfoundation.org>
To: Rivka Bukchin <rivkab300@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: rtl8723bs: fix CamelCase variable names
Date: Mon, 9 Mar 2026 17:06:14 +0100 [thread overview]
Message-ID: <2026030905-surprise-contents-af4f@gregkh> (raw)
In-Reply-To: <20260302160849.2693-1-rivkab300@gmail.com>
On Mon, Mar 02, 2026 at 06:08:49PM +0200, Rivka Bukchin wrote:
> Rename pHT_info_ie and pHT_caps_ie to ht_info_ie and ht_caps_ie
> to address checkpatch CamelCase warnings and follow snake_case
> naming convention used in the kernel.
>
> Signed-off-by: Rivka Bukchin <rivkab300@gmail.com>
Does not apply to my current tree :(
prev parent reply other threads:[~2026-03-09 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:08 [PATCH v3] staging: rtl8723bs: fix CamelCase variable names Rivka Bukchin
2026-03-02 17:30 ` Ethan Tidmore
2026-03-09 16:06 ` Greg KH [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=2026030905-surprise-contents-af4f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rivkab300@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