From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Malov <ivan.malov@arknetworks.am>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Sunil Kumar Kori <skori@marvell.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
David Marchand <david.marchand@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v3 1/1] ethdev: add support to provide link type
Date: Wed, 13 Aug 2025 07:17:18 -0700 [thread overview]
Message-ID: <20250813071718.48c85ea6@hermes.local> (raw)
In-Reply-To: <165f84cf-1fd7-527b-bda6-8b2823ac85e9@arknetworks.am>
On Wed, 13 Aug 2025 16:16:29 +0400 (+04)
Ivan Malov <ivan.malov@arknetworks.am> wrote:
> >> +#define RTE_ETH_LINK_TYPE_FIBRE 4 /**< Fibre */
> >
> > In general we use the US word "fiber",
> > but we are not very consistent, so it is not a strong opinion.
>
> To me, "fibre" reads more natural. Not a strong opinion either.
What word does IEEE standard use? That is what matters.
next prev parent reply other threads:[~2025-08-13 14:17 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 11:31 [PATCH] ethdev: add support to provide link type skori
2025-06-05 15:26 ` Stephen Hemminger
2025-06-06 9:28 ` [PATCH v2 1/1] " skori
2025-06-06 9:54 ` Morten Brørup
2025-06-06 15:23 ` Stephen Hemminger
2025-06-10 5:02 ` [EXTERNAL] " Sunil Kumar Kori
2025-06-10 6:45 ` Morten Brørup
2025-08-13 7:42 ` Sunil Kumar Kori
2025-08-13 8:42 ` [PATCH] " skori
2025-08-13 8:43 ` [PATCH v3 1/1] " skori
2025-08-13 10:25 ` Thomas Monjalon
2025-08-13 12:16 ` Ivan Malov
2025-08-13 14:17 ` Stephen Hemminger [this message]
2025-08-14 5:09 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-13 15:04 ` Stephen Hemminger
2025-08-14 8:10 ` [PATCH v4 " skori
2025-08-14 9:04 ` Morten Brørup
2025-08-14 16:15 ` Stephen Hemminger
2025-08-18 6:21 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-18 7:24 ` Morten Brørup
2025-08-18 8:13 ` Ivan Malov
2025-08-18 8:39 ` Morten Brørup
2025-08-18 8:50 ` Ivan Malov
2025-08-18 22:41 ` Jochen Behrens
2025-08-19 9:57 ` Morten Brørup
2025-08-18 6:20 ` Sunil Kumar Kori
2025-08-14 16:07 ` Stephen Hemminger
2025-08-18 6:13 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-19 5:51 ` [PATCH v5 " skori
2025-08-19 16:29 ` Stephen Hemminger
2025-08-20 9:55 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-20 11:13 ` [PATCH v6 " skori
2025-08-20 12:51 ` Morten Brørup
2025-08-20 17:52 ` [PATCH v7 " skori
2025-08-20 18:58 ` Stephen Hemminger
2025-08-21 4:51 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-21 15:20 ` Stephen Hemminger
2025-08-22 4:34 ` Sunil Kumar Kori
2025-08-21 5:32 ` [PATCH v8 " skori
2025-08-29 20:33 ` Stephen Hemminger
2025-09-01 5:05 ` [EXTERNAL] " Sunil Kumar Kori
2025-09-01 5:44 ` [PATCH v9 " skori
2025-09-06 17:51 ` Stephen Hemminger
2025-09-08 6:21 ` [EXTERNAL] " Sunil Kumar Kori
2025-09-08 8:54 ` Sunil Kumar Kori
2025-09-08 8:51 ` [PATCH v10 " skori
2025-09-08 9:23 ` Thomas Monjalon
2025-09-11 8:12 ` [EXTERNAL] " Sunil Kumar Kori
2025-09-10 0:50 ` Stephen Hemminger
2025-09-10 17:21 ` Thomas Monjalon
2025-09-11 8:48 ` [PATCH v11 1/1] ethdev: add link connector type skori
2025-09-11 9:41 ` Morten Brørup
2025-09-11 10:37 ` Sunil Kumar Kori
2025-09-11 10:34 ` [PATCH v12 " skori
2025-09-11 10:39 ` Morten Brørup
2025-09-15 16:32 ` Stephen Hemminger
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=20250813071718.48c85ea6@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=thomas@monjalon.net \
/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.