public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew@lunn.ch, andrew+netdev@lunn.ch, linux@armlinux.org.uk,
	pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
	kuba@kernel.org, vladimir.oltean@nxp.com, michael@fossekall.de,
	daniel@makrotopia.org, nic_swsd@realtek.com, olek2@wp.pl,
	fabio.baltieri@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] r8169: add support for RTL8127ATF (10G Fiber SFP)
Date: Tue, 13 Jan 2026 03:30:20 +0000	[thread overview]
Message-ID: <176827502011.1659151.15829911581216218944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c2ad7819-85f5-4df8-8ecf-571dbee8931b@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 10 Jan 2026 16:12:30 +0100 you wrote:
> RTL8127ATF supports a SFP+ port for fiber modules (10GBASE-SR/LR/ER/ZR and
> DAC). The list of supported modes was provided by Realtek. According to the
> r8127 vendor driver also 1G modules are supported, but this needs some more
> complexity in the driver, and only 10G mode has been tested so far.
> Therefore mainline support will be limited to 10G for now.
> The SFP port signals are hidden in the chip IP and driven by firmware.
> Therefore mainline SFP support can't be used here.
> The PHY driver is used by the RTL8127ATF support in r8169.
> RTL8127ATF reports the same PHY ID as the TP version. Therefore use a dummy
> PHY ID.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] net: phy: realtek: add dummy PHY driver for RTL8127ATF
    https://git.kernel.org/netdev/net-next/c/c4277d21ab69
  - [net-next,v2,2/2] r8169: add support for RTL8127ATF (Fiber SFP)
    https://git.kernel.org/netdev/net-next/c/fef0f545511f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-13  3:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-10 15:12 [PATCH net-next v2 0/2] r8169: add support for RTL8127ATF (10G Fiber SFP) Heiner Kallweit
2026-01-10 15:14 ` [PATCH net-next v2 1/2] net: phy: realtek: add dummy PHY driver for RTL8127ATF Heiner Kallweit
2026-01-10 15:15 ` [PATCH net-next v2 2/2] r8169: add support for RTL8127ATF (Fiber SFP) Heiner Kallweit
2026-01-11 21:05   ` Fabio Baltieri
2026-01-10 18:48 ` [PATCH net-next v2 0/2] r8169: add support for RTL8127ATF (10G Fiber SFP) Jakub Kicinski
2026-01-10 20:03   ` Heiner Kallweit
2026-01-10 20:08     ` Daniel Golle
2026-01-10 22:30       ` Jakub Kicinski
2026-01-13  3:30 ` 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=176827502011.1659151.15829911581216218944.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fabio.baltieri@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@fossekall.de \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=olek2@wp.pl \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.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