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 0/5] [Series 2] rename variable posHTCap and (4) others
Date: Tue, 12 Dec 2023 11:56:32 -0500 [thread overview]
Message-ID: <20231212165637.17618-1-garyrookard@fastmail.org> (raw)
Hi,
This patch series renames (5) different variables with
the checkpatch coding style issue, Avoid CamelCase.
Patch 1/5) rename variable posHTCap
Patch 2/5) rename variable IsEncrypt
Patch 3/5) rename variable bAssoc
Patch 4/5) rename variable pHT
Patch 5/5) rename variable pCapELE
Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
Gary Rookard (5):
staging: rtl8192e: rename variable posHTCap
staging: rtl8192e: rename variable IsEncrypt
staging: rtl8192e: rename variable bAssoc
staging: rtl8192e: rename variable pHT
staging: rtl8192e: rename variable pCapELE
drivers/staging/rtl8192e/rtl819x_HTProc.c | 90 +++++++++++------------
1 file changed, 45 insertions(+), 45 deletions(-)
--
2.41.0
next reply other threads:[~2023-12-12 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 16:56 Gary Rookard [this message]
2023-12-12 16:56 ` [PATCH 1/5] staging: rtl8192e: rename variable posHTCap Gary Rookard
2023-12-12 16:56 ` [PATCH 2/5] staging: rtl8192e: rename variable IsEncrypt Gary Rookard
2023-12-12 16:56 ` [PATCH 3/5] staging: rtl8192e: rename variable bAssoc Gary Rookard
2023-12-12 16:56 ` [PATCH 4/5] staging: rtl8192e: rename variable pHT Gary Rookard
2023-12-12 18:56 ` Philipp Hortmann
2023-12-12 20:14 ` Gary Rookard
2023-12-13 7:40 ` Dan Carpenter
2023-12-12 16:56 ` [PATCH 5/5] staging: rtl8192e: rename variable pCapELE 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=20231212165637.17618-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 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.