From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next 6/6] wifi: rtw89: Enable the new rtw89_8852bu module
Date: Fri, 4 Jul 2025 05:34:49 +0000 [thread overview]
Message-ID: <4277c890c9be47ab8b2ec60bea1df73d@realtek.com> (raw)
In-Reply-To: <9da12cb0-d364-41bd-a62d-4c1f87e14a16@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> Enable compilation of the new rtw89_8852bu module.
>
> Tested mostly in station mode, and a little bit in AP mode.
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
Please send v2 with my acked-by. Since I have merged patchset of USB support,
nipa can help to build this patchset then.
Thanks for your great USB work.
next prev parent reply other threads:[~2025-07-04 5:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 16:00 [PATCH rtw-next 0/6] wifi: rtw89: Add support for RTL8852BU Bitterblue Smith
2025-07-01 16:02 ` [PATCH rtw-next 1/6] wifi: rtw89: 8852bx: Accept USB devices and load their MAC address Bitterblue Smith
2025-07-04 5:28 ` Ping-Ke Shih
2025-07-01 16:02 ` [PATCH rtw-next 2/6] wifi: rtw89: 8852b: Fix rtw8852b_pwr_{on,off}_func() for USB Bitterblue Smith
2025-07-04 5:30 ` Ping-Ke Shih
2025-07-01 16:03 ` [PATCH rtw-next 3/6] wifi: rtw89: 8852b: Add rtw8852b_dle_mem_usb3 Bitterblue Smith
2025-07-04 5:31 ` Ping-Ke Shih
2025-07-01 16:03 ` [PATCH rtw-next 4/6] wifi: rtw89: 8852b: Add rtw8852b_hfc_param_ini_usb Bitterblue Smith
2025-07-04 5:31 ` Ping-Ke Shih
2025-07-01 16:04 ` [PATCH rtw-next 5/6] wifi: rtw89: Add rtw8852bu.c Bitterblue Smith
2025-07-04 5:32 ` Ping-Ke Shih
2025-07-01 16:05 ` [PATCH rtw-next 6/6] wifi: rtw89: Enable the new rtw89_8852bu module Bitterblue Smith
2025-07-04 5:34 ` Ping-Ke Shih [this message]
2025-07-01 17:44 ` [PATCH rtw-next 0/6] wifi: rtw89: Add support for RTL8852BU Shengyu Qu
2025-07-02 21:13 ` 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=4277c890c9be47ab8b2ec60bea1df73d@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@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;
as well as URLs for NNTP newsgroup(s).