From: patchwork-bot+netdevbpf@kernel.org
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: hkallweit1@gmail.com, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
javen_xu@realsil.com.cn, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] r8169: give RTL_GIGA_MAC_VER_EXTENDED a distinct value
Date: Thu, 13 Aug 2026 01:00:10 +0000 [thread overview]
Message-ID: <178658281064.2171351.14292582236575256726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260808101941.57666-1-kmehltretter@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 8 Aug 2026 12:19:41 +0200 you wrote:
> RTL_GIGA_MAC_VER_EXTENDED implicitly follows
> RTL_GIGA_MAC_VER_LAST = RTL_GIGA_MAC_NONE - 1, so it has the same value
> as RTL_GIGA_MAC_NONE.
>
> rtl_init_one() therefore sends unknown chips through extended detection.
> If TX_CONFIG_V2 reads as zero, they are misidentified as RTL9151AS
> instead of being rejected.
>
> [...]
Here is the summary with links:
- [net] r8169: give RTL_GIGA_MAC_VER_EXTENDED a distinct value
https://git.kernel.org/netdev/net-next/c/d77f3f016826
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-08-13 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 10:19 [PATCH net] r8169: give RTL_GIGA_MAC_VER_EXTENDED a distinct value Karl Mehltretter
2026-08-13 1:00 ` 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=178658281064.2171351.14292582236575256726.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=kmehltretter@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.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