From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: javen_xu@realsil.com.cn, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] r8169: add support for extended chip version id and RTL9151AS
Date: Tue, 27 Jan 2026 03:40:17 +0000 [thread overview]
Message-ID: <176948521785.672496.16492728326006112952.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <a3525b74-a1aa-43f6-8413-56615f6fa795@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 24 Jan 2026 22:27:24 +0100 you wrote:
> From: Javen Xu <javen_xu@realsil.com.cn>
>
> The bits in register TxConfig used for chip identification aren't
> sufficient for the number of upcoming chip versions. Therefore a register
> is added with extended chip version information, for compatibility
> purposes it's called TX_CONFIG_V2. First chip to use the extended chip
> identification is RTL9151AS.
>
> [...]
Here is the summary with links:
- [net-next] r8169: add support for extended chip version id and RTL9151AS
https://git.kernel.org/netdev/net-next/c/5e3c5a2b85da
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-27 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 21:27 [PATCH net-next] r8169: add support for extended chip version id and RTL9151AS Heiner Kallweit
2026-01-26 17:04 ` Simon Horman
2026-01-27 3:40 ` patchwork-bot+netdevbpf [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=176948521785.672496.16492728326006112952.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--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