From: Gary Rookard <garyrookard@fastmail.org>
To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Gary Rookard <garyrookard@fastmail.org>
Subject: [PATCH v2 0/4] [Series 4] staging: rtl8192e: rename variable pHT and (3) other
Date: Fri, 15 Dec 2023 20:01:01 -0500 [thread overview]
Message-ID: <20231216010105.9810-1-garyrookard@fastmail.org> (raw)
Hi,
This patch series renames (4) different variables with
the checkpatch coding style issue, Avoid CamelCase.
(resubmittals)
Patch 1/4) rename variable pHT
Patch 2/4) rename variable pCapELE
Patch 3/4) rename variable HTGetHighestMCSRate
Patch 4/4) rename variable HTFilterMCSRate
Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
Gary Rookard (4):
staging: rtl8192e: rename variable pHT
staging: rtl8192e: rename variable pCapELE
staging: rtl8192e: rename variable HTGetHighestMCSRate
staging: rtl8192e: rename variable HTFilterMCSRate
drivers/staging/rtl8192e/rtl819x_HTProc.c | 86 +++++++++++------------
drivers/staging/rtl8192e/rtllib.h | 2 +-
drivers/staging/rtl8192e/rtllib_wx.c | 2 +-
3 files changed, 45 insertions(+), 45 deletions(-)
--
2.41.0
next reply other threads:[~2023-12-16 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 1:01 Gary Rookard [this message]
2023-12-16 1:01 ` [PATCH v2 1/4] staging: rtl8192e: rename variable pHT Gary Rookard
2023-12-16 1:01 ` [PATCH v2 2/4] staging: rtl8192e: rename variable pCapELE Gary Rookard
2023-12-16 1:01 ` [PATCH v2 3/4] staging: rtl8192e: rename variable HTGetHighestMCSRate Gary Rookard
2023-12-16 1:01 ` [PATCH v2 4/4] staging: rtl8192e: renamed variable HTFilterMCSRate Gary Rookard
2023-12-16 7:27 ` [PATCH v2 0/4] [Series 4] staging: rtl8192e: rename variable pHT and (3) other Greg KH
2023-12-16 13:09 ` Gary Rookard
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 23:12 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=20231216010105.9810-1-garyrookard@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox