linux-staging.lists.linux.dev archive mirror
 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 00/11] staging: r8188eu: the next set of cleanups
Date: Sun,  2 Jan 2022 14:11:30 +0100	[thread overview]
Message-ID: <20220102131141.12310-1-straube.linux@gmail.com> (raw)

This set
 - removes some unused structs, enums and defines
 - removes set but not used fields from some structures

Tested on x86_64 with Inter-Tech DMG-02.

Michael Straube (11):
  staging: r8188eu: remove MAX_CHANNEL_NUM_2G
  staging: r8188eu: remove struct rt_channel_plan_2g
  staging: r8188eu: remove unused enum and defines
  staging: r8188eu: struct rx_hpc is not used
  staging: r8188eu: clean up struct rtw_dig
  staging: r8188eu: clean up struct sw_ant_switch
  staging: r8188eu: struct odm_sta_info is not used
  staging: r8188eu: enum hw90_block is not used
  staging: r8188eu: remove unneeded comments from Hal8188EPhyCfg.h
  staging: r8188eu: remove unused defines from Hal8188EPhyCfg.h
  staging: r8188eu: remove unused defines from rtw_eeprom.h

 drivers/staging/r8188eu/core/rtw_mlme_ext.c   |  2 +-
 drivers/staging/r8188eu/hal/odm.c             | 11 ---
 .../staging/r8188eu/include/Hal8188EPhyCfg.h  | 34 +------
 drivers/staging/r8188eu/include/odm.h         | 90 +------------------
 drivers/staging/r8188eu/include/rtw_eeprom.h  | 31 -------
 .../staging/r8188eu/include/rtw_mlme_ext.h    |  5 --
 drivers/staging/r8188eu/include/rtw_rf.h      | 24 -----
 7 files changed, 3 insertions(+), 194 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-01-02 13:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 13:11 Michael Straube [this message]
2022-01-02 13:11 ` [PATCH 01/11] staging: r8188eu: remove MAX_CHANNEL_NUM_2G Michael Straube
2022-01-02 13:11 ` [PATCH 02/11] staging: r8188eu: remove struct rt_channel_plan_2g Michael Straube
2022-01-02 13:11 ` [PATCH 03/11] staging: r8188eu: remove unused enum and defines Michael Straube
2022-01-02 13:11 ` [PATCH 04/11] staging: r8188eu: struct rx_hpc is not used Michael Straube
2022-01-02 13:11 ` [PATCH 05/11] staging: r8188eu: clean up struct rtw_dig Michael Straube
2022-01-02 13:11 ` [PATCH 06/11] staging: r8188eu: clean up struct sw_ant_switch Michael Straube
2022-01-02 13:11 ` [PATCH 07/11] staging: r8188eu: struct odm_sta_info is not used Michael Straube
2022-01-02 13:11 ` [PATCH 08/11] staging: r8188eu: enum hw90_block " Michael Straube
2022-01-02 13:11 ` [PATCH 09/11] staging: r8188eu: remove unneeded comments from Hal8188EPhyCfg.h Michael Straube
2022-01-02 13:11 ` [PATCH 10/11] staging: r8188eu: remove unused defines " Michael Straube
2022-01-02 13:11 ` [PATCH 11/11] staging: r8188eu: remove unused defines from rtw_eeprom.h Michael Straube
2022-01-02 18:06 ` [PATCH 00/11] staging: r8188eu: the next set of cleanups Martin Kaiser

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=20220102131141.12310-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).