From: Andrew Lunn <andrew@lunn.ch>
To: "D H, Siddaraju" <siddaraju.dh@intel.com>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Michal Kubecek <mkubecek@suse.cz>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Das, Shubham" <shubham.das@intel.com>,
"Chintalapalle, Balaji" <balaji.chintalapalle@intel.com>,
"Srinivasan, Vijay" <vijay.srinivasan@intel.com>,
"Lindberg, Magnus" <magnus.k.lindberg@ericsson.com>,
Niklas Damberg <niklas.damberg@ericsson.com>,
"Wirandi, Jonas" <jonas.wirandi@ericsson.com>,
Siddaraju DH <siddarajudh@gmail.com>
Subject: Re: the confusing 10000base_CR. Shouldn't it be 10000_SFI_DA?
Date: Mon, 29 Jun 2026 15:11:00 +0200 [thread overview]
Message-ID: <deee3864-69dd-4eb5-bcfc-4ab771f4530c@lunn.ch> (raw)
In-Reply-To: <SN7PR11MB6900D73E1714AA8AE05BA7BF9AE82@SN7PR11MB6900.namprd11.prod.outlook.com>
> Will wait for @Michal Kubecek's response about the manual page update
> and as second possibility: options to update ethtool help string.
>
> IMHO, yes the comment in ethtool.h enum definition is good
> as it helps developers who use ethtool.h directly but from
> ethtool app USER point-of-view, the manual page is the
> first impression and ethtool --help is second. The effort here is
> to help the user with a clarification, to avoid the clear confusion
> with the wrong naming of 10000baseCR
Is there confusion? git blame suggests it has been there 10 years, and
this is the first time somebody has questioned it.
I would limit changes to Documentation, man pages, help etc.
Andrew
next prev parent reply other threads:[~2026-06-29 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 14:15 the confusing 10000base_CR. Shouldn't it be 10000_SFI_DA? D H, Siddaraju
2026-06-26 14:32 ` Andrew Lunn
2026-06-26 18:12 ` D H, Siddaraju
2026-06-26 18:18 ` Andrew Lunn
2026-06-26 19:19 ` D H, Siddaraju
2026-06-29 9:30 ` Maxime Chevallier
2026-06-29 11:25 ` D H, Siddaraju
2026-06-29 13:11 ` Andrew Lunn [this message]
2026-06-29 17:29 ` D H, Siddaraju
2026-06-29 18:14 ` Michal Kubecek
2026-06-26 14:33 ` Maxime Chevallier
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=deee3864-69dd-4eb5-bcfc-4ab771f4530c@lunn.ch \
--to=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=shubham.das@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox