From: Ping-Ke Shih <pkshih@realtek.com>
To: Fiona Klute <fiona.klute@gmx.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"pavel@ucw.cz" <pavel@ucw.cz>, "megi@xff.cz" <megi@xff.cz>
Subject: RE: [PATCH v2 0/9] rtw88: Add support for RTL8723CS/RTL8703B
Date: Fri, 1 Mar 2024 00:57:29 +0000 [thread overview]
Message-ID: <0ee4679bd3e2442f9e57e6d63ccf2927@realtek.com> (raw)
In-Reply-To: <31dd8a43-0df0-4f1b-905d-67b1a63fab0e@gmx.de>
> -----Original Message-----
> From: Fiona Klute <fiona.klute@gmx.de>
> Sent: Friday, March 1, 2024 8:45 AM
> To: Ping-Ke Shih <pkshih@realtek.com>; linux-wireless@vger.kernel.org
> Cc: kvalo@kernel.org; ulf.hansson@linaro.org; linux-mmc@vger.kernel.org; pavel@ucw.cz; megi@xff.cz
> Subject: Re: [PATCH v2 0/9] rtw88: Add support for RTL8723CS/RTL8703B
>
> The bigger changes are all in rtw8703b.h (patch 4; the PHY status struct
> instead of macros) and rtw8703b.c (patch 5; PHY status parsing, MAC
> address retrieval, and IKQ done wait). The PHY status struct is
> basically the same as in the vendor driver, I just resolved some macro
> detours for big/little endian detection and spelled out "reserved" in
> field names.
>
> Changes in the other patches are minimal: additional MODULE_AUTHOR in
> rtw8723x.c, missing "static"s in rtw8723x.c and rtw8723x.h, formatting,
> and using rtw_read8_mask in the firmware reset (patch 6).
Thanks for the info.
Ping-Ke
prev parent reply other threads:[~2024-03-01 0:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 23:54 [PATCH v2 0/9] rtw88: Add support for RTL8723CS/RTL8703B Fiona Klute
2024-02-27 23:54 ` [PATCH v2 1/9] wifi: rtw88: Shared module for rtw8723x devices Fiona Klute
2024-02-27 23:54 ` [PATCH v2 2/9] wifi: rtw88: Debug output for rtw8723x EFUSE Fiona Klute
2024-02-27 23:54 ` [PATCH v2 3/9] wifi: rtw88: Add definitions for 8703b chip Fiona Klute
2024-02-27 23:54 ` [PATCH v2 4/9] wifi: rtw88: Add rtw8703b.h Fiona Klute
2024-03-01 2:09 ` Ping-Ke Shih
2024-03-01 16:35 ` Fiona Klute
2024-03-01 17:15 ` Fiona Klute
2024-03-02 0:35 ` Ping-Ke Shih
2024-03-02 0:33 ` Ping-Ke Shih
2024-03-02 0:57 ` Fiona Klute
2024-02-27 23:54 ` [PATCH v2 5/9] wifi: rtw88: Add rtw8703b.c Fiona Klute
2024-03-01 2:33 ` Ping-Ke Shih
2024-03-01 4:36 ` Ping-Ke Shih
2024-03-01 16:54 ` Fiona Klute
2024-02-27 23:55 ` [PATCH v2 6/9] wifi: rtw88: Add rtw8703b_tables.h Fiona Klute
2024-02-27 23:55 ` [PATCH v2 7/9] wifi: rtw88: Add rtw8703b_tables.c Fiona Klute
2024-03-01 2:36 ` Ping-Ke Shih
2024-03-01 16:46 ` Fiona Klute
2024-03-02 0:28 ` Ping-Ke Shih
2024-02-27 23:55 ` [PATCH v2 8/9] wifi: rtw88: Reset 8703b firmware before download Fiona Klute
2024-02-27 23:55 ` [PATCH v2 9/9] wifi: rtw88: SDIO device driver for RTL8723CS Fiona Klute
2024-03-01 2:39 ` Ping-Ke Shih
2024-02-29 6:40 ` [PATCH v2 0/9] rtw88: Add support for RTL8723CS/RTL8703B Ping-Ke Shih
2024-03-01 0:45 ` Fiona Klute
2024-03-01 0:57 ` Ping-Ke Shih [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=0ee4679bd3e2442f9e57e6d63ccf2927@realtek.com \
--to=pkshih@realtek.com \
--cc=fiona.klute@gmx.de \
--cc=kvalo@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=megi@xff.cz \
--cc=pavel@ucw.cz \
--cc=ulf.hansson@linaro.org \
/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