From: patchwork-bot+netdevbpf@kernel.org
To: D@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
H@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Siddaraju <siddaraju.dh@intel.com>
Cc: mkubecek@suse.cz, andrew@lunn.ch, maxime.chevallier@bootlin.com,
netdev@vger.kernel.org, Shubham.Das@intel.com,
balaji.chintalapalle@intel.com, vijay.srinivasan@intel.com,
magnus.k.lindberg@ericsson.com, niklas.damberg@ericsson.com,
jonas.wirandi@ericsson.com, siddarajudh@gmail.com
Subject: Re: [PATCH v2 ethtool] man: ethtool: link 10000baseCR to SFF-8431, Appendix-E SFP+ DA
Date: Mon, 06 Jul 2026 22:00:06 +0000 [thread overview]
Message-ID: <178337520638.1223576.17680136243635201029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260703102004.1111597-1-siddaraju.dh@intel.com>
Hello:
This patch was applied to ethtool/ethtool.git (master)
by Michal Kubecek <mkubecek@suse.cz>:
On Fri, 3 Jul 2026 15:50:04 +0530 you wrote:
> Annotate the 10000baseCR entry in the advertise mask table so users
> understand what physical media this mode it actually represents.
>
> 10000baseCR does not correspond to any IEEE 802.3 *base-CR PMD.
> It has no autonegotiation, no link training, and no mandatory FEC.
> The industry standard for this media type is SFF-8431 Appendix-E
> Direct Attach cable, also known as 10G_SFI_DA.
>
> [...]
Here is the summary with links:
- [v2,ethtool] man: ethtool: link 10000baseCR to SFF-8431, Appendix-E SFP+ DA
https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=b0d4a0d60471
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-07-06 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 10:20 [PATCH v2 ethtool] man: ethtool: link 10000baseCR to SFF-8431, Appendix-E SFP+ DA Siddaraju DH
2026-07-03 13:41 ` Maxime Chevallier
2026-07-06 22: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=178337520638.1223576.17680136243635201029.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=D@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=H@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Shubham.Das@intel.com \
--cc=andrew@lunn.ch \
--cc=balaji.chintalapalle@intel.com \
--cc=jonas.wirandi@ericsson.com \
--cc=magnus.k.lindberg@ericsson.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=niklas.damberg@ericsson.com \
--cc=siddaraju.dh@intel.com \
--cc=siddarajudh@gmail.com \
--cc=vijay.srinivasan@intel.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.