From: Kang Minchul <tegongkang@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Pavel Skripkin <paskripkin@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Kang Minchul <tegongkang@gmail.com>
Subject: [PATCH v2 0/4] staging: r8188eu: cleaning up unused variables
Date: Mon, 24 Oct 2022 17:49:21 +0900 [thread overview]
Message-ID: <20221024084925.262289-1-tegongkang@gmail.com> (raw)
This patch series cleans up unused variables in r8188eu
causing coccicheck warnings.
Difference between v1 and this patch is that this patch series
include making function amsdu_to_msdu in /r8188eu/core/rtw_recv.c
into void function.
Kang Minchul (4):
staging: r8188eu: remove unnecessary variable in ioctl_linux
staging: r8188eu: make amsdu_to_msdu void function
staging: r8188eu: remove unnecessary variable in rtl8188eu_xmit
staging: r8188eu: remove unnecessary variable in rtw_ap
drivers/staging/r8188eu/core/rtw_ap.c | 5 ++---
drivers/staging/r8188eu/core/rtw_recv.c | 5 +----
drivers/staging/r8188eu/hal/rtl8188eu_xmit.c | 3 +--
drivers/staging/r8188eu/os_dep/ioctl_linux.c | 4 +---
4 files changed, 5 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2022-10-24 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 8:49 Kang Minchul [this message]
2022-10-24 8:49 ` [PATCH v2 1/4] staging: r8188eu: remove unnecessary variable in ioctl_linux Kang Minchul
2022-10-24 8:49 ` [PATCH v2 2/4] staging: r8188eu: make amsdu_to_msdu void function Kang Minchul
2022-10-24 12:49 ` kernel test robot
2022-10-24 8:49 ` [PATCH v2 3/4] staging: r8188eu: remove unnecessary variable in rtl8188eu_xmit Kang Minchul
2022-10-24 8:49 ` [PATCH v2 4/4] staging: r8188eu: remove unnecessary variable in rtw_ap Kang Minchul
2022-10-24 11:23 ` [PATCH v2 0/4] staging: r8188eu: cleaning up unused variables Kang Minchul
2022-10-25 17:22 ` Greg Kroah-Hartman
2022-10-25 17:33 ` Kang Minchul
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=20221024084925.262289-1-tegongkang@gmail.com \
--to=tegongkang@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@gmail.com \
--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