From: Michael Straube <straube.linux@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Michael Straube <straube.linux@gmail.com>
Subject: [PATCH v2 00/10] staging: r8188eu: remove rf_type and rtw_rf_config
Date: Sun, 28 Nov 2021 18:09:14 +0100 [thread overview]
Message-ID: <20211128170924.5874-1-straube.linux@gmail.com> (raw)
This series removes rf_type from struct hal_data_8188e and the
module paramater rtw_rc_config.
Tested on x86_64 with InterTech DMG-02.
v2:
included the previously sent series
"staging: r8188eu: remove more usages of rf_type"
Michael Straube (10):
staging: r8188eu: remove rf_type from rtw_update_ht_cap()
staging: r8188eu: remove rf_type from issue_assocreq()
staging: r8188eu: remove rf_type from storePwrIndexDiffRateOffset()
staging: r8188eu: remove rf_type from getTxPowerIndex88E()
staging: r8188eu: remove TxCount from getTxPowerIndex88E()
staging: r8188eu: remove rf_type from writeOFDMPowerReg88E()
staging: r8188eu: remove rf_type from bb_reg_dump()
staging: r8188eu: remove unused HW_VAR_RF_TYPE
staging: r8188eu: remove rf_type from struct hal_data_8188e
staging: r8188eu: remove module parameter rtw_rf_config
drivers/staging/r8188eu/core/rtw_mlme.c | 12 +--
drivers/staging/r8188eu/core/rtw_mlme_ext.c | 25 ++----
.../staging/r8188eu/hal/rtl8188e_hal_init.c | 4 -
drivers/staging/r8188eu/hal/rtl8188e_phycfg.c | 85 +++----------------
drivers/staging/r8188eu/hal/rtl8188e_rf6052.c | 6 +-
drivers/staging/r8188eu/hal/usb_halinit.c | 3 -
drivers/staging/r8188eu/include/drv_types.h | 1 -
drivers/staging/r8188eu/include/hal_intf.h | 1 -
.../staging/r8188eu/include/rtl8188e_hal.h | 3 -
drivers/staging/r8188eu/include/rtw_rf.h | 10 ---
drivers/staging/r8188eu/os_dep/ioctl_linux.c | 27 ++----
drivers/staging/r8188eu/os_dep/os_intfs.c | 3 -
12 files changed, 30 insertions(+), 150 deletions(-)
--
2.34.0
next reply other threads:[~2021-11-28 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 17:09 Michael Straube [this message]
2021-11-28 17:09 ` [PATCH v2 01/10] staging: r8188eu: remove rf_type from rtw_update_ht_cap() Michael Straube
2021-11-28 17:09 ` [PATCH v2 02/10] staging: r8188eu: remove rf_type from issue_assocreq() Michael Straube
2021-11-28 17:09 ` [PATCH v2 03/10] staging: r8188eu: remove rf_type from storePwrIndexDiffRateOffset() Michael Straube
2021-11-28 17:09 ` [PATCH v2 04/10] staging: r8188eu: remove rf_type from getTxPowerIndex88E() Michael Straube
2021-11-28 17:09 ` [PATCH v2 05/10] staging: r8188eu: remove TxCount " Michael Straube
2021-11-28 17:09 ` [PATCH v2 06/10] staging: r8188eu: remove rf_type from writeOFDMPowerReg88E() Michael Straube
2021-11-28 17:09 ` [PATCH v2 07/10] staging: r8188eu: remove rf_type from bb_reg_dump() Michael Straube
2021-11-28 17:09 ` [PATCH v2 08/10] staging: r8188eu: remove unused HW_VAR_RF_TYPE Michael Straube
2021-11-28 17:09 ` [PATCH v2 09/10] staging: r8188eu: remove rf_type from struct hal_data_8188e Michael Straube
2021-11-28 17:09 ` [PATCH v2 10/10] staging: r8188eu: remove module parameter rtw_rf_config Michael Straube
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=20211128170924.5874-1-straube.linux@gmail.com \
--to=straube.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).