From: Martin Kaiser <martin@kaiser.cx>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH 0/6] staging: r8188eu: clean up efuse / eeprom code
Date: Thu, 25 Nov 2021 16:14:30 +0100 [thread overview]
Message-ID: <20211125151436.5895-1-martin@kaiser.cx> (raw)
Remove unused defines and functions related to efuses and eeprom.
Martin Kaiser (6):
staging: r8188eu: Efuse_CalculateWordCnts is not used
staging: r8188eu: efuse_WordEnableDataRead is not used
staging: r8188eu: remove unused efuse defines
staging: r8188eu: do not extract eeprom version from the fuses
staging: r8188eu: remove unused eeprom defines
staging: r8188eu: hal data's board type is unused
drivers/staging/r8188eu/core/rtw_efuse.c | 56 -------------------
.../staging/r8188eu/hal/rtl8188e_hal_init.c | 24 --------
drivers/staging/r8188eu/hal/usb_halinit.c | 2 -
.../staging/r8188eu/include/rtl8188e_hal.h | 7 ---
.../staging/r8188eu/include/rtl8188e_spec.h | 49 ----------------
drivers/staging/r8188eu/include/rtw_efuse.h | 25 ---------
6 files changed, 163 deletions(-)
--
2.20.1
next reply other threads:[~2021-11-25 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 15:14 Martin Kaiser [this message]
2021-11-25 15:14 ` [PATCH 1/6] staging: r8188eu: Efuse_CalculateWordCnts is not used Martin Kaiser
2021-11-25 15:14 ` [PATCH 2/6] staging: r8188eu: efuse_WordEnableDataRead " Martin Kaiser
2021-11-25 15:14 ` [PATCH 3/6] staging: r8188eu: remove unused efuse defines Martin Kaiser
2021-11-25 15:14 ` [PATCH 4/6] staging: r8188eu: do not extract eeprom version from the fuses Martin Kaiser
2021-11-25 15:14 ` [PATCH 5/6] staging: r8188eu: remove unused eeprom defines Martin Kaiser
2021-11-25 15:14 ` [PATCH 6/6] staging: r8188eu: hal data's board type is unused 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=20211125151436.5895-1-martin@kaiser.cx \
--to=martin@kaiser.cx \
--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 \
--cc=straube.linux@gmail.com \
/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
all inboxes | Powered by JetHome®