From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Luka Gejak <luka.gejak@linux.dev>, linux-wireless@vger.kernel.org
Cc: Ping-Ke Shih <pkshih@realtek.com>
Subject: Re: [PATCH rtw-next 3/5] wifi: rtw88: pci: Introduce struct rtw_pci_gen
Date: Wed, 28 Oct 2026 23:26:40 +0200 [thread overview]
Message-ID: <00aa3f2f-001f-4368-9d00-fccbc53869b1@gmail.com> (raw)
In-Reply-To: <3a8cd96e14c643837676fcee1d85c720b54f5377@linux.dev>
On 24/10/2026 11:41, Luka Gejak wrote:
> October 24, 2026 at 1:01 AM, "Bitterblue Smith" <rtl8821cerfe2@gmail.com> wrote:
>
>>
>> Move a few functions into a new struct rtw_pci_gen in order to add
>> support for RTL8821AE and RTL8812AE. That is an older generation of
>> chips which handle the PCI communications differently.
>>
>> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
>> ---
>> [...]
>
>> rx_ring->r.head = head;
>> + rx_ring->r.dma = dma;
>> + rx_ring->r.len = len;
>> + rx_ring->r.desc_size = desc_size;
>> + rx_ring->r.wp = 0;
>> + rx_ring->r.rp = 0;
>
> In my opinion the commit message should mention why these were moved
> before the loop.
>
Right, that's because rtw_pci_old_reset_rx_desc() needs the ring
length too.
> [...]
>
>> {
>> + struct rtw_pci *rtwpci = (struct rtw_pci *)rtwdev->priv;
>> + const struct rtw_pci_gen *pci_gen = rtwpci->gen;
>> +
>> u8 q;
>
> The blank line before u8 q can go, so the declarations stay together.
>
I didn't notice that.
> [...]
>
>> int rtw_pci_probe(struct pci_dev *pdev,
>> const struct pci_device_id *id)
>> {
>> + struct rtw_pci_info *pci_info = (struct rtw_pci_info *)id->driver_data;
>
> I think this should be a const pointer, since the pci_info tables are
> const.
Sounds good. Although that line gets very long.
>
> Best regards,
> Luka Gejak
next prev parent reply other threads:[~2026-10-28 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 22:57 [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE Bitterblue Smith
2026-10-23 22:59 ` [PATCH rtw-next 1/5] wifi: rtw88: Pass RX buffer to rtw_rx_query_rx_desc() Bitterblue Smith
2026-10-23 23:00 ` [PATCH rtw-next 2/5] wifi: rtw88: Pass TX descriptor to rtw_tx_fill_tx_desc() Bitterblue Smith
2026-10-23 23:01 ` [PATCH rtw-next 3/5] wifi: rtw88: pci: Introduce struct rtw_pci_gen Bitterblue Smith
2026-10-24 8:41 ` Luka Gejak
2026-10-28 21:26 ` Bitterblue Smith [this message]
2026-10-23 23:02 ` [PATCH rtw-next 4/5] wifi: rtw88: pci: Add functions to support older chips Bitterblue Smith
2026-10-24 8:36 ` Luka Gejak
2026-10-28 17:40 ` Bitterblue Smith
2026-10-23 23:05 ` [PATCH rtw-next 5/5] wifi: rtw88: pci: Handle more RX interrupts for RTL8821AE Bitterblue Smith
2026-10-27 1:52 ` [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE Ping-Ke Shih
2026-10-27 7:25 ` Luka Gejak
2026-10-27 8:07 ` Ping-Ke Shih
2026-10-28 17:41 ` Bitterblue Smith
2026-10-29 0:51 ` Ping-Ke Shih
2026-10-29 1:29 ` Ping-Ke Shih
2026-10-29 21:00 ` Bitterblue Smith
2026-10-30 0:43 ` 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=00aa3f2f-001f-4368-9d00-fccbc53869b1@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=pkshih@realtek.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