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 v2] wifi: rtw88: Parse the RX descriptor with a single function
Date: Mon, 23 Sep 2024 05:49:54 +0000 [thread overview]
Message-ID: <21a239b103d7457eb84d31106f9580cb@realtek.com> (raw)
In-Reply-To: <913f1747-38fc-4409-85a4-57bb9cee506b@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> rtw8703b_query_rx_desc(), rtw8723d_query_rx_desc(),
> rtw8821c_query_rx_desc(), rtw8822b_query_rx_desc(), and
> rtw8822c_query_rx_desc() are almost identical, so replace them all with
> a single function, rtw_rx_query_rx_desc().
>
> Also, access the RX descriptor using a struct with __le32 members and
> le32_get_bits().
>
> Tested with RTL8811CU, RTL8811AU, and RTL8812AU.
I also tested with RTL8723DE and RTL8822CE, so
Tested-by: Ping-Ke Shih <pkshih@realtek.com> # RTL8723DE and RTL8822CE
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2024-09-23 5:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 22:53 [PATCH 1/2] wifi: rtw88: Constify some arrays and structs Bitterblue Smith
2024-09-17 22:56 ` [PATCH 2/2] wifi: rtw88: Parse the RX descriptor with a single function Bitterblue Smith
2024-09-20 2:21 ` Ping-Ke Shih
2024-09-20 12:44 ` Bitterblue Smith
2024-09-20 2:22 ` [PATCH 1/2] wifi: rtw88: Constify some arrays and structs Ping-Ke Shih
2024-09-20 3:06 ` Ping-Ke Shih
2024-09-20 19:27 ` [PATCH v2] wifi: rtw88: Parse the RX descriptor with a single function Bitterblue Smith
2024-09-23 5:49 ` Ping-Ke Shih [this message]
2024-09-26 1:31 ` Ping-Ke Shih
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=21a239b103d7457eb84d31106f9580cb@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).