public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Gary Rookard <garyrookard@fastmail.org>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: rtl8192e: this patch series renames (5) different variables
Date: Thu, 7 Dec 2023 18:37:25 +0100	[thread overview]
Message-ID: <0541b225-cc2a-491f-9631-212455c0098f@gmail.com> (raw)
In-Reply-To: <20231206230404.1721-1-garyrookard@fastmail.org>

On 12/7/23 00:03, Gary Rookard wrote:
> Hi,
> 
> This patch series renames 5 different variables with the checkpatch coding
> style issue, Avoid CamelCase.
> 
> Patch 1/5) renamed variable bAMSDU_Support
> Patch 2/5) renamed variable bAMPD?U_Enable
> Patch 3/5) renamed variable AMPDU_factor
> Patch 4/5) renamed variable MPDU_Density
> Patch 5/5) renamed variable bTxEnableFwCalcDur
> 
> Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
> 
> Gary Rookard (5):
>    staging: rtl8192e: renamed variable bAMSDU_Support
>    staging: rtl8192e: renamed variable bAMPDUEnable
>    staging: rtl8192e: renamed variable AMPDU_Factor
>    staging: rtl8192e: renamed variable MPDU_Density
>    staging: rtl8192e: renamed variable bTxEnableFwCalcDur
> 
>   .../staging/rtl8192e/rtl8192e/r8192E_dev.c    |  4 ++--
>   drivers/staging/rtl8192e/rtl8192e/rtl_core.c  |  2 +-
>   drivers/staging/rtl8192e/rtl819x_HT.h         |  8 +++----
>   drivers/staging/rtl8192e/rtl819x_HTProc.c     | 24 +++++++++----------
>   drivers/staging/rtl8192e/rtllib.h             |  6 ++---
>   drivers/staging/rtl8192e/rtllib_tx.c          | 10 ++++----
>   6 files changed, 27 insertions(+), 27 deletions(-)
> 

Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>

      parent reply	other threads:[~2023-12-07 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 23:03 [PATCH 0/5] staging: rtl8192e: this patch series renames (5) different variables Gary Rookard
2023-12-06 23:04 ` [PATCH 1/5] staging: rtl8192e: renamed variable bAMSDU_Support Gary Rookard
2023-12-06 23:04 ` [PATCH 2/5] staging: rtl8192e: renamed variable bAMPDUEnable Gary Rookard
2023-12-06 23:04 ` [PATCH 3/5] staging: rtl8192e: renamed variable AMPDU_Factor Gary Rookard
2023-12-06 23:04 ` [PATCH 4/5] staging: rtl8192e: renamed variable MPDU_Density Gary Rookard
2023-12-06 23:04 ` [PATCH 5/5] staging: rtl8192e: renamed variable bTxEnableFwCalcDur Gary Rookard
2023-12-07 17:37 ` Philipp Hortmann [this message]

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=0541b225-cc2a-491f-9631-212455c0098f@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=garyrookard@fastmail.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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