From: Josua Mayer <josua@solid-run.com>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Cc: Mikhail Anikin <mikhail.anikin@solid-run.com>,
Rabeeh Khoury <rabeeh@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Josua Mayer <josua@solid-run.com>
Subject: [PATCH 0/2] net: sfp: support 25G long-range modules (extended compliance code 0x3)
Date: Sun, 18 Jan 2026 16:07:36 +0200 [thread overview]
Message-ID: <20260118-sfp-25g-lr-v1-0-2daf48ffae7f@solid-run.com> (raw)
Add ethtool link-mode bit for 25Gbps long-range fiber, and enable it
when parsing sfp module eeprom for extended compliance code 0x3.
Signed-off-by: Josua Mayer <josua@solid-run.com>
---
Josua Mayer (2):
net: ethtool: Add link mode for 25Gbps long-range fiber
net: sfp: support 25G long-range modules (extended compliance code 0x3)
drivers/net/phy/phy-core.c | 2 +-
drivers/net/phy/sfp-bus.c | 4 +++-
include/uapi/linux/ethtool.h | 1 +
net/ethtool/common.c | 2 ++
4 files changed, 7 insertions(+), 2 deletions(-)
---
base-commit: b4e486e2c46f754a515571a8ca1238fa567396dd
change-id: 20260118-sfp-25g-lr-b0b8cccbb19a
Best regards,
--
Josua Mayer <josua@solid-run.com>
next reply other threads:[~2026-01-18 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 14:07 Josua Mayer [this message]
2026-01-18 14:07 ` [PATCH 1/2] net: ethtool: Add link mode for 25Gbps long-range fiber Josua Mayer
2026-01-18 14:07 ` [PATCH 2/2] net: sfp: support 25G long-range modules (extended compliance code 0x3) Josua Mayer
2026-01-18 16:01 ` Andrew Lunn
2026-01-19 7:30 ` Josua Mayer
2026-01-19 10:48 ` Russell King (Oracle)
2026-01-19 19:30 ` Jakub Kicinski
2026-01-21 9:44 ` Josua Mayer
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=20260118-sfp-25g-lr-v1-0-2daf48ffae7f@solid-run.com \
--to=josua@solid-run.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mikhail.anikin@solid-run.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rabeeh@solid-run.com \
--cc=yazan.shhady@solid-run.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