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: odm cleanups
Date: Thu, 2 Dec 2021 20:23:04 +0100 [thread overview]
Message-ID: <20211202192309.9362-1-straube.linux@gmail.com> (raw)
This series removes unused and some set but never used variables
from the odm_dm_struct structure.
Tested on x86_64 with InterTech DMG-02.
Michael Straube (5):
staging: r8188eu: remove unused variables from odm_dm_struct
staging: r8188eu: pbNet_closed is set but never used
staging: r8188eu: pSecurity is set but never used
staging: r8188eu: pNumTxBytesUnicast is set but never used
staging: r8188eu: pNumRxBytesUnicast is set but never used
drivers/staging/r8188eu/hal/odm.c | 12 ----
drivers/staging/r8188eu/hal/rtl8188e_dm.c | 4 --
drivers/staging/r8188eu/include/odm.h | 73 +----------------------
3 files changed, 1 insertion(+), 88 deletions(-)
--
2.34.0
next reply other threads:[~2021-12-02 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 19:23 Michael Straube [this message]
2021-12-02 19:23 ` [PATCH 1/5] staging: r8188eu: remove unused variables from odm_dm_struct Michael Straube
2021-12-02 19:23 ` [PATCH 2/5] staging: r8188eu: pbNet_closed is set but never used Michael Straube
2021-12-02 19:23 ` [PATCH 3/5] staging: r8188eu: pSecurity " Michael Straube
2021-12-02 19:23 ` [PATCH 4/5] staging: r8188eu: pNumTxBytesUnicast " Michael Straube
2021-12-02 19:23 ` [PATCH 5/5] staging: r8188eu: pNumRxBytesUnicast " Michael Straube
2021-12-02 21:22 ` [PATCH 0/5] staging: r8188eu: odm cleanups Martin Kaiser
-- strict thread matches above, loose matches on Subject: below --
2022-02-20 10:02 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=20211202192309.9362-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).