From: Larry Finger <Larry.Finger@lwfinger.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-staging@lists.linux.dev
Subject: Re: kernel BUG in new r8188eu
Date: Mon, 2 Aug 2021 09:49:37 -0500 [thread overview]
Message-ID: <4f3e91f4-3d7b-a580-3134-757614d92491@lwfinger.net> (raw)
In-Reply-To: <YQfKohnSRWHjlht6@kroah.com>
On 8/2/21 5:36 AM, Greg Kroah-Hartman wrote:
> Ah, doh, that was my fault, sorry, that patch was incorrect (odd git id,
> don't know where that came from, it's a different id in my tree.) Let
> me revert this commit and then will redo it correctly.
>
> thanks for finding this.
>
>> There are lots of these on Ebay from $2.47 up with free shipping!
> Any hints on the name for how to figure out which devices are supported
> by this driver?
I do not why my git id did not match yours.
It was no problem. After I determined that the original code was correct, it was
an easy bisection - 6 cycles with only r8188eu needing rebuilding.
The driver supports RTL8188EU and RTL8188EUS. The name comes from the 8188E, and
the U means a USB interface. The S indicates a new design that appears the same
to the driver.
Larry
prev parent reply other threads:[~2021-08-02 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 19:59 kernel BUG in new r8188eu Larry Finger
2021-07-31 5:37 ` Greg Kroah-Hartman
2021-07-31 16:18 ` Larry Finger
2021-07-31 18:53 ` Fabio Aiuto
2021-07-31 21:54 ` Larry Finger
2021-08-01 6:31 ` Greg Kroah-Hartman
2021-08-01 20:15 ` Larry Finger
2021-08-02 10:36 ` Greg Kroah-Hartman
2021-08-02 11:45 ` Fabio M. De Francesco
2021-08-02 14:38 ` Greg Kroah-Hartman
2021-08-02 14:40 ` Larry Finger
2021-08-02 15:46 ` Greg Kroah-Hartman
2021-08-02 14:49 ` Larry Finger [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=4f3e91f4-3d7b-a580-3134-757614d92491@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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).