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 03/11] Staging: rtl8192e: Rename variable TimeStampHigh
Date: Sun, 10 Mar 2024 16:55:44 -0700 [thread overview]
Message-ID: <20240310235552.4217-4-tdavies@darkphysics.net> (raw)
In-Reply-To: <20240310235552.4217-1-tdavies@darkphysics.net>
Rename variable TimeStampHigh to time_stamp_high to fix
checkpatch warning Avoid CamelCase.
Signed-off-by: Tree Davies <tdavies@darkphysics.net>
---
drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c | 2 +-
drivers/staging/rtl8192e/rtllib.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c b/drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c
index 480315404969..15b0ac6e6eef 100644
--- a/drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c
+++ b/drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c
@@ -1660,7 +1660,7 @@ bool rtl92e_get_rx_stats(struct net_device *dev, struct rtllib_rx_stats *stats,
(pDrvInfo->FirstAGGR == 1);
stats->time_stamp_low = pDrvInfo->TSFL;
- stats->TimeStampHigh = rtl92e_readl(dev, TSFR + 4);
+ stats->time_stamp_high = rtl92e_readl(dev, TSFR + 4);
_rtl92e_translate_rx_signal_stats(dev, skb, stats, pdesc, pDrvInfo);
skb_trim(skb, skb->len - S_CRC_LEN);
diff --git a/drivers/staging/rtl8192e/rtllib.h b/drivers/staging/rtl8192e/rtllib.h
index 72264e1ef877..e165f1e32e7f 100644
--- a/drivers/staging/rtl8192e/rtllib.h
+++ b/drivers/staging/rtl8192e/rtllib.h
@@ -483,7 +483,7 @@ struct rtllib_rx_stats {
u16 bICV:1;
u16 Decrypted:1;
u32 time_stamp_low;
- u32 TimeStampHigh;
+ u32 time_stamp_high;
u8 RxDrvInfoSize;
u8 RxBufShift;
--
2.30.2
next prev parent 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 [PATCH 00/11] Staging: rtl8192e: Style guide Renames and Macros Tree Davies
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 ` Tree Davies [this message]
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-4-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 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.