From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Jardin <vjardin@free.fr>
Cc: ioana.ciornei@nxp.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: pcs: lynx: add support for 25GBASE-R
Date: Thu, 03 Sep 2026 02:20:28 +0000 [thread overview]
Message-ID: <178840202893.3047971.11842592730625729019.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922-for-upstream-lynx-25gbaser-v1-v2-1-1e6cf79c7b52@free.fr>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Sep 2026 21:40:33 +0200 you wrote:
> From: Vincent Jardin <vjardin@free.fr>
>
> The Lynx PCS never supported 25GBASE-R. Add it, so that a 25G DPMAC on
> LX2160A can be driven by phylink.
>
> The SerDes side had the mode since the commit
> 1cab8fba5073 ("phy: lynx-28g: add support for 25GBASER")
> and dpaa2-mac maps DPMAC_ETH_IF_CAUI to PHY_INTERFACE_MODE_25GBASER,
> but the PCS never handled it, so phylink_validate() failed with the
> interface.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: pcs: lynx: add support for 25GBASE-R
https://git.kernel.org/netdev/net-next/c/e8965b0523f2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-03 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:40 [PATCH net-next v2] net: pcs: lynx: add support for 25GBASE-R Vincent Jardin via B4 Relay
2026-09-22 19:40 ` Vincent Jardin
2026-09-01 22:01 ` Maxime Chevallier
2026-09-03 2:20 ` patchwork-bot+netdevbpf [this message]
2026-09-03 21:52 ` Bradley Morgan
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=178840202893.3047971.11842592730625729019.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vjardin@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.