public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] staging: rtl8192e: Rename CamelCase variables and remove one from rtl_core.h
Date: Sat, 21 Jan 2023 22:44:46 +0100	[thread overview]
Message-ID: <cover.1674336211.git.philipp.g.hortmann@gmail.com> (raw)

Rename variables to avoid CamelCase which is not accepted by checkpatch.
Remove unused variable.

Tested with rtl8192e
Transferred this patch over wlan connection of rtl8192e

Can only be applied after the patch series from 20.01.2023.

Philipp Hortmann (3):
  staging: rtl8192e: Remove unused variable bfirst_init
  staging: rtl8192e: Rename eeprom_CustomerID, SwChnlStage and
    SwChnlStep
  staging: rtl8192e: Rename btxpower_trackin.., Slide_Beaco.. and
    Slide_B..

 drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c | 16 ++++++++--------
 drivers/staging/rtl8192e/rtl8192e/r8192E_phy.c |  8 ++++----
 drivers/staging/rtl8192e/rtl8192e/rtl_core.c   |  6 ------
 drivers/staging/rtl8192e/rtl8192e/rtl_core.h   | 13 ++++++-------
 drivers/staging/rtl8192e/rtl8192e/rtl_dm.c     | 10 +++++-----
 5 files changed, 23 insertions(+), 30 deletions(-)

-- 
2.39.0


             reply	other threads:[~2023-01-21 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 21:44 Philipp Hortmann [this message]
2023-01-21 21:44 ` [PATCH 1/3] staging: rtl8192e: Remove unused variable bfirst_init Philipp Hortmann
2023-01-21 21:44 ` [PATCH 2/3] staging: rtl8192e: Rename eeprom_CustomerID, SwChnlStage and SwChnlStep Philipp Hortmann
2023-01-21 21:45 ` [PATCH 3/3] staging: rtl8192e: Rename btxpower_trackin.., Slide_Beaco.. and Slide_B Philipp Hortmann

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=cover.1674336211.git.philipp.g.hortmann@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --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