From: Ping-Ke Shih <pkshih@realtek.com>
To: "s.l-h@gmx.de" <s.l-h@gmx.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
"chewitt@libreelec.tv" <chewitt@libreelec.tv>
Subject: Re: [PATCH 1/3] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common
Date: Wed, 13 Mar 2024 06:25:14 +0000 [thread overview]
Message-ID: <cdee2e123ce2845f757ba74751f4871999fd5c5a.camel@realtek.com> (raw)
In-Reply-To: <20240313071850.61a42e4f@mir>
On Wed, 2024-03-13 at 07:18 +0100, Stefan Lippers-Hollmann wrote:
>
> The performance is okay - the driver has been working reliably all day
> long (WPA2SAE and WPA2PSK/ CCMP, 2.4 GHz and 5 GHz, against an
> ipq8071a+qcn5024+qcn5054 AP running recent OpenWrt).
>
Thanks. Both PHY rate and throughput look good.
Bitterblue, Can you make a record in commit message of the last commit
that enables 8192DU?
Ping-Ke
next prev parent reply other threads:[~2024-03-13 6:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 22:18 [PATCH 1/3] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common Bitterblue Smith
2024-03-12 22:20 ` [PATCH 2/3] wifi: rtlwifi: Adjust rtl8192d-common for USB Bitterblue Smith
2024-03-13 3:46 ` Ping-Ke Shih
2024-03-13 22:47 ` Bitterblue Smith
2024-03-14 1:20 ` Ping-Ke Shih
2024-03-14 13:49 ` Bitterblue Smith
2024-03-12 22:23 ` [PATCH 3/3] wifi: rtlwifi: Add new rtl8192du driver Bitterblue Smith
2024-03-13 5:49 ` Ping-Ke Shih
2024-03-13 22:45 ` Bitterblue Smith
2024-03-14 0:34 ` Ping-Ke Shih
2024-03-12 23:21 ` [PATCH 1/3] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common Bitterblue Smith
2024-03-13 3:53 ` Ping-Ke Shih
2024-03-13 22:40 ` Bitterblue Smith
2024-03-13 2:16 ` Ping-Ke Shih
2024-03-13 22:39 ` Bitterblue Smith
2024-03-13 5:49 ` Stefan Lippers-Hollmann
2024-03-13 5:55 ` Ping-Ke Shih
2024-03-13 6:18 ` Stefan Lippers-Hollmann
2024-03-13 6:25 ` Ping-Ke Shih [this message]
2024-03-13 22:44 ` Bitterblue Smith
2024-03-13 22:41 ` Bitterblue Smith
2024-03-14 0:28 ` Ping-Ke Shih
2024-09-15 6:04 ` Stefan Lippers-Hollmann
2024-09-16 7:42 ` Ping-Ke Shih
2024-09-16 10:21 ` Stefan Lippers-Hollmann
2024-03-13 8:58 ` Kalle Valo
2024-03-13 22:46 ` Bitterblue Smith
2024-03-14 8:18 ` Kalle Valo
2024-03-14 8:42 ` Kalle Valo
2024-03-14 13:50 ` 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=cdee2e123ce2845f757ba74751f4871999fd5c5a.camel@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chewitt@libreelec.tv \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=s.l-h@gmx.de \
/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).