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 1/5] staging: r8188eu: usb_vendor_req_mutex is not used
Date: Sun, 6 Feb 2022 18:59:21 +0100 [thread overview]
Message-ID: <20220206175925.461426-2-martin@kaiser.cx> (raw)
In-Reply-To: <20220206175925.461426-1-martin@kaiser.cx>
usb_vendor_req_mutex in struct dvobj_priv is not used.
Remove it.
Signed-off-by: Martin Kaiser <martin@kaiser.cx>
---
drivers/staging/r8188eu/include/drv_types.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/r8188eu/include/drv_types.h b/drivers/staging/r8188eu/include/drv_types.h
index 987dae613d8b..7e6385109cbc 100644
--- a/drivers/staging/r8188eu/include/drv_types.h
+++ b/drivers/staging/r8188eu/include/drv_types.h
@@ -141,7 +141,6 @@ struct dvobj_priv {
u8 RtNumOutPipes;
int RegUsbSS;
struct semaphore usb_suspend_sema;
- struct mutex usb_vendor_req_mutex;
struct usb_interface *pusbintf;
struct usb_device *pusbdev;
--
2.30.2
next prev parent reply other threads:[~2022-02-06 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 17:59 [PATCH 0/5] staging: r8188eu: clean up struct dvobj_priv Martin Kaiser
2022-02-06 17:59 ` Martin Kaiser [this message]
2022-02-06 17:59 ` [PATCH 2/5] staging: r8188eu: dvobj_priv's signal_strength is not used Martin Kaiser
2022-02-06 17:59 ` [PATCH 3/5] staging: r8188eu: RegUsbSS " Martin Kaiser
2022-02-06 17:59 ` [PATCH 4/5] staging: r8188eu: usb_suspend_sema is initialised but " Martin Kaiser
2022-02-06 17:59 ` [PATCH 5/5] staging: r8188eu: remove ishighspeed from dvobj_priv Martin Kaiser
2022-02-08 9:30 ` Greg Kroah-Hartman
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=20220206175925.461426-2-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®