From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Martin Kaiser <martin@kaiser.cx>,
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>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] staging: r8188eu: clean up usb transfers
Date: Wed, 25 Jan 2023 19:56:13 +0100 [thread overview]
Message-ID: <0b5d743a-c071-e4b5-23e4-ab59d6ef785d@gmail.com> (raw)
In-Reply-To: <20230124210108.62170-1-martin@kaiser.cx>
On 1/24/23 22:01, Martin Kaiser wrote:
> This series cleans up some defines related to usb transfers. It's based on
> the series I sent yesterday.
>
> Martin Kaiser (4):
> staging: r8188eu: usb_read_port_complete needs no regs parameter
> staging: r8188eu: remove defines that strip regs parameter
> staging: r8188eu: remove unused defines
> staging: r8188eu: remove usb_ops_linux.h
>
> drivers/staging/r8188eu/hal/usb_ops_linux.c | 6 ++++-
> drivers/staging/r8188eu/include/usb_ops.h | 2 --
> .../staging/r8188eu/include/usb_ops_linux.h | 27 -------------------
> .../staging/r8188eu/os_dep/usb_ops_linux.c | 1 -
> 4 files changed, 5 insertions(+), 31 deletions(-)
> delete mode 100644 drivers/staging/r8188eu/include/usb_ops_linux.h
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com> # Edimax N150
prev parent reply other threads:[~2023-01-25 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 21:01 Martin Kaiser
2023-01-24 21:01 ` [PATCH 1/4] staging: r8188eu: usb_read_port_complete needs no regs parameter Martin Kaiser
2023-01-24 21:01 ` [PATCH 2/4] staging: r8188eu: remove defines that strip " Martin Kaiser
2023-01-24 21:01 ` [PATCH 3/4] staging: r8188eu: remove unused defines Martin Kaiser
2023-01-24 21:01 ` [PATCH 4/4] staging: r8188eu: remove usb_ops_linux.h Martin Kaiser
2023-01-25 18:56 ` Philipp Hortmann [this message]
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=0b5d743a-c071-e4b5-23e4-ab59d6ef785d@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®