From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: <david@cardinalsystem.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: "Michael Straube" <straube.linux@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Ethan Tidmore" <ethantidmore06@gmail.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
<linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: rename variables to snake_case
Date: Sun, 29 Mar 2026 18:51:18 -0500 [thread overview]
Message-ID: <DHFO471EX30W.1B58WCIKFNFS6@gmail.com> (raw)
In-Reply-To: <20260327203636.24891-1-david@cardinalsystem.net>
On Fri Mar 27, 2026 at 3:36 PM CDT, david wrote:
> From: David Holland <david@cardinalsystem.net>
>
> The Linux kernel coding style guidelines prohibit the use of CamelCase
> variable names. All variables should be snakecase.
>
> Rename the 'ChipVersion' parameter to 'chip_version' and the
> 'AutoLoadFail' parameter to 'auto_load_fail' in hal_com.c to adhere to
> the standard snakecase naming convention.
>
> Signed-off-by: David Holland <david@cardinalsystem.net>
> ---
...
>
> @@ -86,7 +86,7 @@ void dump_chip_info(struct hal_version ChipVersion)
> * BIT[6:0] Channel Plan
> *sw_channel_plan channel plan from SW (registry/module param)
> *def_channel_plan channel plan used when HW/SW both invalid
> - *AutoLoadFail efuse autoload fail or not
> + *auto_load_fail efuse autoload fail or not
I think the whitespace here was intentional (although I can't tell why
they did it like this), originally the comments starting with channel and
efuse lined up and this changes it.
Thanks,
ET
prev parent reply other threads:[~2026-03-29 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 20:36 [PATCH] staging: rtl8723bs: rename variables to snake_case david
2026-03-29 6:43 ` Bera Yüzlü
2026-03-29 7:32 ` Greg KH
2026-03-29 23:51 ` Ethan Tidmore [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=DHFO471EX30W.1B58WCIKFNFS6@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.carpenter@linaro.org \
--cc=david@cardinalsystem.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=straube.linux@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