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 0/5] staging: r8188eu: clean up struct pwrctrl_priv
Date: Mon, 4 Apr 2022 10:21:37 +0200 [thread overview]
Message-ID: <20220404082142.4639-1-straube.linux@gmail.com> (raw)
Tis series removes unused and set but never changed fields from the
pwrctrl_priv structure.
Tested on x86_64 with Inter-Tech DMG-02.
Michael Straube (5):
staging: r8188eu: remove unused fields from struct pwrctrl_priv
staging: r8188eu: reg_rfoff is never set
staging: r8188eu: pnp_bstop_trx is never set
staging: r8188eu: pwr_state_check_cnts is always zero
staging: r8188eu: ps_flag is never set
drivers/staging/r8188eu/core/rtw_pwrctrl.c | 4 +---
drivers/staging/r8188eu/hal/usb_halinit.c | 4 ----
drivers/staging/r8188eu/hal/usb_ops_linux.c | 7 +++----
drivers/staging/r8188eu/include/rtw_pwrctrl.h | 14 --------------
drivers/staging/r8188eu/os_dep/os_intfs.c | 10 ----------
drivers/staging/r8188eu/os_dep/usb_ops_linux.c | 3 +--
6 files changed, 5 insertions(+), 37 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-04 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 8:21 Michael Straube [this message]
2022-04-04 8:21 ` [PATCH 1/5] staging: r8188eu: remove unused fields from struct pwrctrl_priv Michael Straube
2022-04-04 8:21 ` [PATCH 2/5] staging: r8188eu: reg_rfoff is never set Michael Straube
2022-04-04 8:21 ` [PATCH 3/5] staging: r8188eu: pnp_bstop_trx " Michael Straube
2022-04-04 8:21 ` [PATCH 4/5] staging: r8188eu: pwr_state_check_cnts is always zero Michael Straube
2022-04-04 8:21 ` [PATCH 5/5] staging: r8188eu: ps_flag is never set 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=20220404082142.4639-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).