linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev, Martin Kaiser <martin@kaiser.cx>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Phillip Potter <phil@philpotter.co.uk>,
	Pavel Skripkin <paskripkin@gmail.com>
Subject: Re: [PATCH] staging: r8188eu: delete driver
Date: Wed, 8 Mar 2023 14:44:29 +0100	[thread overview]
Message-ID: <ZAiRPbXff1f27HUz@kroah.com> (raw)
In-Reply-To: <92a9442a-cece-4179-fbdc-3c9188da073e@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

On Wed, Mar 08, 2023 at 02:26:39PM +0100, Hans de Goede wrote:
> Hi All,
> 
> > Now that the same hardware that the r8188eu driver supported is
> > supported by the real wireless driver rtl8xxxu, the r8188eu driver can
> > be deleted.
> >
> > Also the rtl8xxxu driver supports way more devices, and is a fraction of
> > the overall size, making this a much better overall solution.
> >
> > Thanks to the r8188eu developers and maintainers and reviewers over the
> > years, your work allowed Linux users to use their hardware before the
> > real driver was implemented properly.
> >
> > Reported-by: Hans de Goede <hdegoede@redhat.com>
> > Cc: Martin Kaiser <martin@kaiser.cx>
> > Cc: Larry Finger <Larry.Finger@lwfinger.net>
> > Cc: Phillip Potter <phil@philpotter.co.uk>
> > Cc: Pavel Skripkin <paskripkin@gmail.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Thank you for doing this, I agree that this is the best solution
> moving forward:
> 
> Acked-by: Hans de Goede <hdegoede@redhat.com>

Great!

Also, to verify the "these devices are supported", I compared the list
of module aliases exported by both drivers.  The r8188eu is a tiny
subset of the rtl8xxxu driver, with no devices listed in the r8188eu
that are not in the rtl8xxxu driver.

Attached are the lists of the vendor/product USB ids for each driver as
proof.

thanks,

greg k-h

[-- Attachment #2: r8188eu.devices --]
[-- Type: text/plain, Size: 165 bytes --]

v056Ep4008
v07B8p8179
v0B05p18F0
v0BDAp0179
v0BDAp8179
v0BDApFFEF
v0DF6p0076
v2001p330F
v2001p3310
v2001p3311
v2001p331B
v2357p010C
v2357p0111
v2C4Ep0102
v7392pB811

[-- Attachment #3: rtl8xxxu.devices --]
[-- Type: text/plain, Size: 1078 bytes --]

v04BBp094C
v04BBp0950
v04F2pAFF7
v04F2pAFF8
v04F2pAFF9
v04F2pAFFA
v04F2pAFFB
v04F2pAFFC
v050Dp1004
v050Dp1102
v050Dp2102
v050Dp2103
v056Ep4008
v0586p341F
v06F8pE033
v06F8pE035
v0789p016D
v07AAp0056
v07B8p8178
v07B8p8179
v07B8p8189
v0846p9021
v0846p9041
v0846pF001
v0B05p17AB
v0B05p17BA
v0B05p18F0
v0BDAp0179
v0BDAp018A
v0BDAp0724
v0BDAp1724
v0BDAp1E1E
v0BDAp2E2E
v0BDAp317F
v0BDAp5088
v0BDAp8170
v0BDAp8176
v0BDAp8177
v0BDAp8178
v0BDAp8179
v0BDAp817A
v0BDAp817B
v0BDAp817D
v0BDAp817E
v0BDAp817F
v0BDAp818A
v0BDAp818B
v0BDAp818C
v0BDAp8191
v0BDAp8724
v0BDApB720
v0BDApF179
v0BDApFFEF
v0DF6p0052
v0DF6p005C
v0DF6p0061
v0DF6p0070
v0DF6p0076
v0E66p0019
v0E66p0020
v0EB0p9071
v103Cp1629
v1058p0631
v13D3p3357
v2001p3307
v2001p3308
v2001p3309
v2001p330A
v2001p330B
v2001p330F
v2001p3310
v2001p3311
v2001p3319
v2001p331B
v2019p1201
v2019p4902
v2019pAB2A
v2019pAB2B
v2019pAB2E
v2019pAB33
v2019pED17
v20F4p624D
v20F4p648B
v2357p0100
v2357p0107
v2357p0108
v2357p0109
v2357p010C
v2357p0111
v2C4Ep0102
v4855p0090
v4855p0091
v4856p0091
v7392p7811
v7392p7822
v7392pA611
v7392pB811
vCDABp8010

  reply	other threads:[~2023-03-08 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 13:19 [PATCH] staging: r8188eu: delete driver Greg Kroah-Hartman
2023-03-08 13:26 ` Hans de Goede
2023-03-08 13:44   ` Greg Kroah-Hartman [this message]
2023-03-08 14:17 ` Martin Kaiser
2023-03-08 18:22 ` Larry Finger
2023-03-08 20:33 ` Philipp Hortmann
2023-03-08 22:36 ` Michael Straube
2023-03-10 19:08 ` Pavel Skripkin
2023-03-11 10:33   ` Phillip Potter
2023-03-11 12:19     ` Greg Kroah-Hartman
2023-03-14  8:06       ` Richard Weinberger
2023-03-20 19:31         ` Bitterblue Smith

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=ZAiRPbXff1f27HUz@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin@kaiser.cx \
    --cc=paskripkin@gmail.com \
    --cc=patches@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).