From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/20] staging: r8188eu: pass struct adapter to usb_write
Date: Tue, 17 Jan 2023 19:38:28 +0100 [thread overview]
Message-ID: <Y8brJFAjan6DuhwF@kroah.com> (raw)
In-Reply-To: <20230111195640.306748-19-martin@kaiser.cx>
On Wed, Jan 11, 2023 at 08:56:38PM +0100, Martin Kaiser wrote:
> The usb_write function takes a struct intf_hdl only to extract the struct
> adapter from it. We can pass struct adapter directly.
>
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> ---
> drivers/staging/r8188eu/hal/usb_ops_linux.c | 15 +++++----------
> 1 file changed, 5 insertions(+), 10 deletions(-)
This commit did not apply to my tree so I stopped here in the series.
Please rebase and resubmit the remaining ones.
thanks,
greg k-h
next prev parent reply other threads:[~2023-01-17 18:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 19:56 [PATCH 00/20] staging: r8188eu: io cleanup Martin Kaiser
2023-01-11 19:56 ` [PATCH 01/20] staging: r8188eu: remove struct io_priv Martin Kaiser
2023-01-11 19:56 ` [PATCH 02/20] staging: r8188eu: remove io function prototypes Martin Kaiser
2023-01-11 19:56 ` [PATCH 03/20] staging: r8188eu: remove ioreq " Martin Kaiser
2023-01-11 19:56 ` [PATCH 04/20] staging: r8188eu: remove async read " Martin Kaiser
2023-01-11 19:56 ` [PATCH 05/20] staging: r8188eu: remove async write " Martin Kaiser
2023-01-11 19:56 ` [PATCH 06/20] staging: r8188eu: remove struct io_queue Martin Kaiser
2023-01-11 19:56 ` [PATCH 07/20] staging: r8188eu: remove attrib function prototypes Martin Kaiser
2023-01-11 19:56 ` [PATCH 08/20] staging: r8188eu: remove rtw_write_scsi function prototype Martin Kaiser
2023-01-11 19:56 ` [PATCH 09/20] staging: r8188eu: remove dev_power_down " Martin Kaiser
2023-01-11 19:56 ` [PATCH 10/20] staging: r8188eu: remove struct reg_protocol_rd Martin Kaiser
2023-01-11 19:56 ` [PATCH 11/20] staging: r8188eu: remove struct reg_protocol_wt Martin Kaiser
2023-01-11 19:56 ` [PATCH 12/20] staging: r8188eu: remove interface handler prototypes Martin Kaiser
2023-01-11 19:56 ` [PATCH 13/20] staging: r8188eu: remove readmem and writemem prototypes Martin Kaiser
2023-01-11 19:56 ` [PATCH 14/20] staging: r8188eu: remove IO defines Martin Kaiser
2023-01-11 19:56 ` [PATCH 15/20] staging: r8188eu: remove struct io_req Martin Kaiser
2023-01-11 19:56 ` [PATCH 16/20] staging: r8188eu: remove usb buffer macros Martin Kaiser
2023-01-11 19:56 ` [PATCH 17/20] staging: r8188eu: pass struct adapter to usb_read Martin Kaiser
2023-01-11 19:56 ` [PATCH 18/20] staging: r8188eu: pass struct adapter to usb_write Martin Kaiser
2023-01-17 18:38 ` Greg Kroah-Hartman [this message]
2023-01-11 19:56 ` [PATCH 19/20] staging: r8188eu: remove struct intf_hdl Martin Kaiser
2023-01-11 19:56 ` [PATCH 20/20] staging: r8188eu: remove struct intf_priv Martin Kaiser
2023-01-11 22:10 ` [PATCH 00/20] staging: r8188eu: io cleanup Philipp Hortmann
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=Y8brJFAjan6DuhwF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).