From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Rivka Bukchin" <rivkab300@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] staging: rtl8723bs: fix CamelCase variable names
Date: Mon, 02 Mar 2026 11:30:45 -0600 [thread overview]
Message-ID: <DGSH44H1ORRZ.305LBTYIL3ZJ7@gmail.com> (raw)
In-Reply-To: <20260302160849.2693-1-rivkab300@gmail.com>
On Mon Mar 2, 2026 at 10:08 AM CST, 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>
>
> ---
> v3:
> - Rename pHT_caps_ie to ht_caps_ie for consistency
> - Fix commit message format
>
> v2:
> - Use full real name in Signed-off-by and From fields
Patch failed to apply against staging-next. :(
Thanks,
ET
next prev parent reply other threads:[~2026-03-02 17:31 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 [this message]
2026-03-09 16:06 ` Greg KH
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=DGSH44H1ORRZ.305LBTYIL3ZJ7@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.