From: Tree Davies <tdavies@darkphysics.net>
To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com, anjan@momi.ca
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Tree Davies <tdavies@darkphysics.net>
Subject: [PATCH 00/11] Staging: rtl8192e: Style guide Renames and Macros
Date: Sun, 10 Mar 2024 16:55:41 -0700 [thread overview]
Message-ID: <20240310235552.4217-1-tdavies@darkphysics.net> (raw)
10/11 patches in this series rename variables to fix camelCase style
guide violations. The 11th patch implements the use of the BIT macro
instead of regular bit shift operations.
MOTE: Because patch #11 changes DEFINEs the compiler issues
redefinition warnings. I don't know how to address these as part
of this submission.
All changes Tested on Hardware
Thank you in advance to reviewers.
Tree
Tree Davies (11):
Staging: rtl8192e: Rename variable ReturnPoint
Staging: rtl8192e: Rename variable TimeStampLow
Staging: rtl8192e: Rename variable TimeStampHigh
Staging: rtl8192e: Rename variable Frame_Order
Staging: rtl8192e: Rename variable aSifsTime
Staging: rtl8192e: Rename variable posHTCap
Staging: rtl8192e: Rename variable bRTSUseShortPreamble
Staging: rtl8192e: Rename variable pBssHT
Staging: rtl8192e: Rename variable bAllowAllDA
Staging: rtl8192e: Rename variable WriteIntoReg
Staging: rtl8192e: Implement BIT macro for bit shift ops
.../staging/rtl8192e/rtl8192e/r8192E_dev.c | 16 ++--
.../staging/rtl8192e/rtl8192e/r8192E_dev.h | 4 +-
drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 2 +-
drivers/staging/rtl8192e/rtl819x_HTProc.c | 24 +++---
drivers/staging/rtl8192e/rtllib.h | 80 +++++++++----------
5 files changed, 63 insertions(+), 63 deletions(-)
--
2.30.2
next reply other threads:[~2024-03-10 23:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 23:55 Tree Davies [this message]
2024-03-10 23:55 ` [PATCH 01/11] Staging: rtl8192e: Rename variable ReturnPoint Tree Davies
2024-03-10 23:55 ` [PATCH 02/11] Staging: rtl8192e: Rename variable TimeStampLow Tree Davies
2024-03-10 23:55 ` [PATCH 03/11] Staging: rtl8192e: Rename variable TimeStampHigh Tree Davies
2024-03-10 23:55 ` [PATCH 04/11] Staging: rtl8192e: Rename variable Frame_Order Tree Davies
2024-03-10 23:55 ` [PATCH 05/11] Staging: rtl8192e: Rename variable aSifsTime Tree Davies
2024-03-10 23:55 ` [PATCH 06/11] Staging: rtl8192e: Rename variable posHTCap Tree Davies
2024-03-10 23:55 ` [PATCH 07/11] Staging: rtl8192e: Rename variable bRTSUseShortPreamble Tree Davies
2024-03-10 23:55 ` [PATCH 08/11] Staging: rtl8192e: Rename variable pBssHT Tree Davies
2024-03-10 23:55 ` [PATCH 09/11] Staging: rtl8192e: Rename variable bAllowAllDA Tree Davies
2024-03-10 23:55 ` [PATCH 10/11] Staging: rtl8192e: Rename variable WriteIntoReg Tree Davies
2024-03-10 23:55 ` [PATCH 11/11] Staging: rtl8192e: Implement BIT macro for bit shift ops Tree Davies
2024-03-11 6:39 ` kernel test robot
2024-03-11 9:24 ` kernel test robot
2024-03-11 5:45 ` [PATCH 00/11] Staging: rtl8192e: Style guide Renames and Macros Dan Carpenter
2024-03-25 18:01 ` Greg KH
2024-03-25 18:02 ` 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=20240310235552.4217-1-tdavies@darkphysics.net \
--to=tdavies@darkphysics.net \
--cc=anjan@momi.ca \
--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