From: Larry Finger <Larry.Finger@lwfinger.net>
To: Phillip Potter <phil@philpotter.co.uk>, gregkh@linuxfoundation.org
Cc: dan.carpenter@oracle.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, fabioaiuto83@gmail.com
Subject: Re: [PATCH 0/7] staging: rtl8188eu: replace driver with better version
Date: Fri, 23 Jul 2021 16:08:38 -0500 [thread overview]
Message-ID: <42086ca2-69b2-b2d4-893f-82418df2ec7a@lwfinger.net> (raw)
In-Reply-To: <20210723004214.912295-1-phil@philpotter.co.uk>
On 7/22/21 7:42 PM, Phillip Potter wrote:
> I had to break this patchset up a bit to get around the file size limits
> on the mailing list, and also I removed the hostapd stuff which is
> userspace related and therefore not required.
Phillip,
I'm sorry that I have mislead you, but the v5.2.2.4 branch appears to be broken.
I have not been able to get that one to work.
The master branch, which is v4.1.4_6773.20130222, is working quite well. It
suffers from the problem that when it is scanning, the USB receive buffer is
ignored, but that is a problem with most of the Realtek USB drivers. As a
result, the ping time to my router will sometimes get to 2 sec, rather than the
usual 1-2 ms.That is something that I will try to fix. My suspicion is that
scanning should be left to the network manager.
This version also behaves nicely with NetworkManager.
None of the source files in this branch have trailing white space.
Sorry for the confusion.
Larry
next prev parent reply other threads:[~2021-07-23 21:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 0:42 [PATCH 0/7] staging: rtl8188eu: replace driver with better version Phillip Potter
2021-07-23 0:42 ` [PATCH 1/7] staging: rtl8188eu: remove existing staging driver Phillip Potter
2021-07-23 0:42 ` [PATCH 2/7] staging: rtl8188eu: introduce new core dir for RTL8188eu driver Phillip Potter
2021-07-23 0:42 ` [PATCH 3/7] staging: rtl8188eu: introduce new hal " Phillip Potter
2021-07-23 0:42 ` [PATCH 4/7] staging: rtl8188eu: introduce new os_dep " Phillip Potter
2021-07-23 17:33 ` kernel test robot
2021-07-23 17:33 ` [RFC PATCH] staging: rtl8188eu: fix duplicated inclusion kernel test robot
2021-07-23 0:42 ` [PATCH 5/7] staging: rtl8188eu: introduce new include dir for RTL8188eu driver Phillip Potter
2021-07-23 0:42 ` [PATCH 6/7] staging: rtl8188eu: introduce new supporting files " Phillip Potter
2021-07-23 7:29 ` Fabio Aiuto
2021-07-23 11:09 ` Greg KH
2021-07-23 11:19 ` Phillip Potter
2021-07-23 0:42 ` [PATCH 7/7] staging: rtl8188eu: attach newly imported driver to build system Phillip Potter
2021-07-23 7:19 ` kernel test robot
2021-07-23 14:33 ` kernel test robot
2021-07-23 1:56 ` [PATCH 0/7] staging: rtl8188eu: replace driver with better version Larry Finger
2021-07-23 7:29 ` Phillip Potter
2021-07-23 11:01 ` Greg KH
2021-07-23 11:05 ` Phillip Potter
2021-07-23 21:08 ` Larry Finger [this message]
2021-07-23 21:27 ` Phillip Potter
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=42086ca2-69b2-b2d4-893f-82418df2ec7a@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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).