All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Rookard <garyrookard@fastmail.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: philipp.g.hortmann@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] staging: rtl8192e: renamed variable bCurBW40MHz
Date: Sun, 26 Nov 2023 05:46:44 -0500	[thread overview]
Message-ID: <87r0kcx02z.fsf@fastmail.org> (raw)
In-Reply-To: <2023112618-subdued-genetics-8062@gregkh>


Greg KH <gregkh@linuxfoundation.org> writes:

> On Sat, Nov 25, 2023 at 05:34:30PM -0500, Gary Rookard wrote:
>> Renamed from CamelCase to Snake case the variable bCurBW40MHz.
>> bCurBW40MHz -> b_cur_bw_40mhz
>
> Same here, why keep the "b"?  "b" usually means "byte" which of course
> means nothing here, so it can be dropped.
>
> thanks,
>
> greg k-h

Okay, will redo.

Regards,
Gary

  reply	other threads:[~2023-11-26 10:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 22:34 [PATCH 0/5] staging: rtl8192e: patch series renaming (6) different variables Gary Rookard
2023-11-25 22:34 ` [PATCH 1/5] staging: rtl8192e: renamed 2 variables nMcsRate, mcsRate Gary Rookard
2023-11-26 10:30   ` Greg KH
2023-11-26 10:42     ` Gary Rookard
2023-11-25 22:34 ` [PATCH 2/5] staging: rtl8192e: renamed variable isShortGI Gary Rookard
2023-11-25 22:34 ` [PATCH 3/5] staging: rtl8192e: renamed variable bCurBW40MHz Gary Rookard
2023-11-26 10:29   ` Greg KH
2023-11-26 10:46     ` Gary Rookard [this message]
2023-11-25 22:34 ` [PATCH 4/5] staging: rtl8192e: renamed variable nDataRate Gary Rookard
2023-11-26 10:29   ` Greg KH
2023-11-26 10:48     ` Gary Rookard
2023-11-25 22:34 ` [PATCH 5/5] staging: rtl8192e: renamed variable is40MHz Gary Rookard

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=87r0kcx02z.fsf@fastmail.org \
    --to=garyrookard@fastmail.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@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.