public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
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: misc cleanups
Date: Sun,  5 Dec 2021 18:13:32 +0100	[thread overview]
Message-ID: <20211205171342.20551-1-straube.linux@gmail.com> (raw)

This series consists of various cleanups.

Tested on x86_64 with InterTech DMG-02.

v2:
Removed patch 11 and 12.

As mentionied by Pavel the hal data allocation is never checked
for success. I'll work on that and send a separate series that
also removes the GET_HAL_DATA macro.

Michael Straube (10):
  staging: r8188eu: remove RF_PATH_{C,D}
  staging: r8188eu: struct odm_mac_status_info is not used
  staging: r8188eu: remove macro PHY_SetRFReg
  staging: r8188eu: remove macro PHY_QueryRFReg
  staging: r8188eu: remove macro PHY_SetBBReg
  staging: r8188eu: remove macro PHY_QueryBBReg
  staging: r8188eu: remove duplicate defines
  staging: r8188eu: bWIFI_Direct is set but never used
  staging: r8188eu: bWIFI_Display is set but never used
  staging: r8188eu: remove unused macro IS_FW_81xxC

 drivers/staging/r8188eu/core/rtw_p2p.c        |  3 -
 drivers/staging/r8188eu/hal/HalPhyRf_8188e.c  |  6 +-
 drivers/staging/r8188eu/hal/odm.c             |  8 +--
 drivers/staging/r8188eu/hal/odm_interface.c   | 12 ++--
 .../staging/r8188eu/hal/rtl8188e_hal_init.c   |  8 ---
 drivers/staging/r8188eu/hal/rtl8188e_phycfg.c | 60 ++++++-------------
 drivers/staging/r8188eu/hal/rtl8188e_rf6052.c | 26 ++++----
 drivers/staging/r8188eu/hal/usb_halinit.c     | 12 ++--
 .../staging/r8188eu/include/Hal8188EPhyCfg.h  | 16 -----
 drivers/staging/r8188eu/include/hal_intf.h    |  2 -
 drivers/staging/r8188eu/include/odm.h         |  8 ---
 drivers/staging/r8188eu/include/rtl8188e_dm.h |  7 +--
 .../staging/r8188eu/include/rtl8188e_hal.h    |  2 +-
 13 files changed, 49 insertions(+), 121 deletions(-)

-- 
2.34.1


             reply	other threads:[~2021-12-05 17:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05 17:13 Michael Straube [this message]
2021-12-05 17:13 ` [PATCH v2 01/10] staging: r8188eu: remove RF_PATH_{C,D} Michael Straube
2021-12-05 17:13 ` [PATCH v2 02/10] staging: r8188eu: struct odm_mac_status_info is not used Michael Straube
2021-12-05 17:13 ` [PATCH v2 03/10] staging: r8188eu: remove macro PHY_SetRFReg Michael Straube
2021-12-05 17:13 ` [PATCH v2 04/10] staging: r8188eu: remove macro PHY_QueryRFReg Michael Straube
2021-12-05 17:13 ` [PATCH v2 05/10] staging: r8188eu: remove macro PHY_SetBBReg Michael Straube
2021-12-05 17:13 ` [PATCH v2 06/10] staging: r8188eu: remove macro PHY_QueryBBReg Michael Straube
2021-12-05 17:13 ` [PATCH v2 07/10] staging: r8188eu: remove duplicate defines Michael Straube
2021-12-05 17:13 ` [PATCH v2 08/10] staging: r8188eu: bWIFI_Direct is set but never used Michael Straube
2021-12-05 17:13 ` [PATCH v2 09/10] staging: r8188eu: bWIFI_Display " Michael Straube
2021-12-05 17:13 ` [PATCH v2 10/10] staging: r8188eu: remove unused macro IS_FW_81xxC 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=20211205171342.20551-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