From: Teddy Engel <engel.teddy@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Teddy Engel <engel.teddy@gmail.com>
Subject: [PATCH v2 0/5] staging: rtl8192e: Cleanup multiple issues
Date: Thu, 13 Jun 2024 21:15:06 +0100 [thread overview]
Message-ID: <cover.1718309120.git.engel.teddy@gmail.com> (raw)
Remove some unused constants, macros, and structs.
Capitalize a constant.
The patch order matters - please apply in order.
Teddy Engel (5):
staging: rtl8192e: Remove unused constants
staging: rtl8192e: Remove unused struct phy_ofdm_rx_status_rxsc
staging: rtl8192e: Capitalize constant RegC38_TH
staging: rtl8192e: Remove unused macro dm_tx_bb_gain_idx_to_amplify
staging: rtl8192e: Remove unnecessary pre-declaration of struct
net_device
drivers/staging/rtl8192e/rtl8192e/r8190P_def.h | 9 ---------
drivers/staging/rtl8192e/rtl8192e/rtl_cam.h | 1 -
drivers/staging/rtl8192e/rtl8192e/rtl_dm.c | 4 ++--
drivers/staging/rtl8192e/rtl8192e/rtl_dm.h | 6 +-----
drivers/staging/rtl8192e/rtl8192e/rtl_pci.h | 1 -
5 files changed, 3 insertions(+), 18 deletions(-)
--
2.39.2
next reply other threads:[~2024-06-13 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 20:15 Teddy Engel [this message]
2024-06-13 20:15 ` [PATCH v2 1/5] staging: rtl8192e: Remove unused constants Teddy Engel
2024-06-13 20:15 ` [PATCH v2 2/5] staging: rtl8192e: Remove unused struct phy_ofdm_rx_status_rxsc Teddy Engel
2024-06-13 20:15 ` [PATCH v2 3/5] staging: rtl8192e: Capitalize constant RegC38_TH Teddy Engel
2024-06-13 20:15 ` [PATCH v2 4/5] staging: rtl8192e: Remove unused macro dm_tx_bb_gain_idx_to_amplify Teddy Engel
2024-06-13 20:15 ` [PATCH v2 5/5] staging: rtl8192e: Remove unnecessary pre-declaration of struct net_device Teddy Engel
2024-06-14 20:00 ` [PATCH v2 0/5] staging: rtl8192e: Cleanup multiple issues 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.1718309120.git.engel.teddy@gmail.com \
--to=engel.teddy@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