From: Javen <javen_xu@realsil.com.cn>
To: Vlad Banea <montrealtango@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"nic_swsd@realtek.com" <nic_swsd@realtek.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC net-next 0/5] r8169: RSS for the RTL8125B
Date: Fri, 20 Nov 2026 02:31:25 +0000 [thread overview]
Message-ID: <d672fb6d16b04fb4a1c9b3202d276662@realsil.com.cn> (raw)
In-Reply-To: <20261119123305.2459069-1-montrealtango@gmail.com>
>
>Hi Heiner, Javen,
>
>Gentle ping on this RFC. It still applies to net-next.
>
>The question I'm least sure about is patch 1: is the RTL8127A affected by the
>same TX descriptor race? If so, I'll send patch 1 to net as a fix on its own.
>Comments on the overall approach for the RTL8125B would also help before I
>send a non-RFC version.
>
Hi Vlad,
RTL8127 is also affected by this issue.
Thanks,
Javen
>Thanks,
>Vlad
prev parent reply other threads:[~2026-11-20 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 22:01 Vlad Banea
2026-11-11 22:01 ` [RFC net-next 1/5] r8169: recheck the TX descriptor after a vector-map interrupt Vlad Banea
2026-11-11 22:01 ` [RFC net-next 2/5] r8169: describe the vector-map interrupt layout per chip Vlad Banea
2026-11-11 22:01 ` [RFC net-next 3/5] r8169: make the RSS hash types and descriptor type " Vlad Banea
2026-11-11 22:01 ` [RFC net-next 4/5] r8169: add the type 3 RX descriptor Vlad Banea
2026-11-11 22:01 ` [RFC net-next 5/5] r8169: enable RSS on the RTL8125B Vlad Banea
2026-11-19 12:33 ` [RFC net-next 0/5] r8169: RSS for " Vlad Banea
2026-11-20 2:31 ` Javen [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=d672fb6d16b04fb4a1c9b3202d276662@realsil.com.cn \
--to=javen_xu@realsil.com.cn \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=montrealtango@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®