public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
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 v3 0/3] staging: rtl8192e: patch series renames (3) different variables
Date: Tue, 28 Nov 2023 13:17:24 -0500	[thread overview]
Message-ID: <20231128181727.19504-1-garyrookard@fastmail.org> (raw)

Hi,

This [v3]  patch series renames 3 different variables
and improves the commit message style.
[v2] Style issues, redo.
[v1] Style issues, redo.

Patch 1/3) Coding style issue, checkpatch Avoid CamelCase,
rename it nMcsRate -> mcs_rate.

Patch 2/3) Coding style issue, checkpatch Avoid CamelCase,
rename it bCurBW40MHz -> cur_bw_40mhz.

Patch 3/3) Coding style issue, checkpatch Avoid CamelCase,
rename it nDateRate -> data_rate.

Signed-off-by: Gary Rookard <garyrookard@fastmail.org>

Gary Rookard (3):
  staging: rtl8192e: renamed variable nMcsRate
  staging: rtl8192e: renamed variable bCurBW40MHz
  staging: rtl8192e: renamed variable nDataRate

 drivers/staging/rtl8192e/rtl819x_HT.h        |  2 +-
 drivers/staging/rtl8192e/rtl819x_HTProc.c    | 36 ++++++++++----------
 drivers/staging/rtl8192e/rtllib_softmac_wx.c |  4 +--
 drivers/staging/rtl8192e/rtllib_tx.c         | 10 +++---
 4 files changed, 26 insertions(+), 26 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-11-28 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 18:17 Gary Rookard [this message]
2023-11-28 18:17 ` [PATCH v3 1/3] staging: rtl8192e: renamed variable nMcsRate Gary Rookard
2023-11-28 18:17 ` [PATCH v3 2/3] staging: rtl8192e: renamed variable bCurBW40MHz Gary Rookard
2023-11-28 18:17 ` [PATCH v3 3/3] staging: rtl8192e: renamed variable nDataRate 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=20231128181727.19504-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