From: patchwork-bot+netdevbpf@kernel.org
To: Francesco Dolcini <francesco@dolcini.it>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, francesco.dolcini@toradex.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1] net: pcs: xpcs: add 10000baseCR_Full to 10GBASE-R link modes
Date: Fri, 20 Nov 2026 02:30:16 +0000 [thread overview]
Message-ID: <179514181602.3985754.15557680920042942739.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116101644.83097-1-francesco@dolcini.it>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Nov 2026 11:16:44 +0100 you wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> An SFP+ direct attach cable is reported by the SFP layer as
> 10000baseCR_Full, and this link mode is missing from the 10GBASE-R
> supported list, therefore xpcs_validate() masks it away and the
> 10GBASE-R interface cannot be used with such a cable.
>
> [...]
Here is the summary with links:
- [net-next,v1] net: pcs: xpcs: add 10000baseCR_Full to 10GBASE-R link modes
https://git.kernel.org/netdev/net-next/c/0742ef27cd72
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-11-20 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 10:16 [PATCH net-next v1] net: pcs: xpcs: add 10000baseCR_Full to 10GBASE-R link modes Francesco Dolcini
2026-11-16 13:30 ` Andrew Lunn
2026-11-17 22:17 ` netdev-bot+sashiko
2026-11-20 2: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=179514181602.3985754.15557680920042942739.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=hkallweit1@gmail.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 \
/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.