From: Thomas Monjalon <thomas@monjalon.net>
To: skori@marvell.com, Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: Re: [PATCH v10 1/1] ethdev: add support to provide link type
Date: Wed, 10 Sep 2025 19:21:36 +0200 [thread overview]
Message-ID: <5008943.GXAFRqVoOG@thomas> (raw)
In-Reply-To: <20250909175007.5a54bcf9@hermes.local>
10/09/2025 02:50, Stephen Hemminger:
> On Mon, 8 Sep 2025 14:21:48 +0530
> <skori@marvell.com> wrote:
>
> > From: Sunil Kumar Kori <skori@marvell.com>
> >
> > Adding link type parameter to provide the type
> > of port like twisted pair, fibre etc.
> >
> > Also added an API to convert the RTE_ETH_LINK_CONNECTOR_XXX
> > to a readable string.
> >
> > Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> > Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> > ---
> > v9..v10:
> > - Rebase on top of next-net:main branch.
> > v8..v9:
> > - Adds 25.11 release notes.
> > v7..v8:
> > - Add documentation for invalid link type.
> > - Remove trace point from API.
> > - Rebase on next-net.
> > v6..v7:
> > - Replace link_type to link_connector.
> > - Update comments.
> > v5..v6:
> > - Fix doxygen error.
> > v4..v5:
> > - Convert link type to connector.
> > - Fix build error on Windows.
> > - Handle comsmetic review comments.
> > v3..v4:
> > - Convert #define into enum.
> > - Enhance comments for each port link type.
> > - Fix test failures.
> > v2..v3
> > - Extend link type list as per suggestion.
> >
> > app/test/test_ethdev_link.c | 18 +++++----
> > doc/guides/rel_notes/release_25_11.rst | 9 +++++
> > lib/ethdev/rte_ethdev.c | 45 ++++++++++++++++++++-
> > lib/ethdev/rte_ethdev.h | 54 ++++++++++++++++++++++++++
> > 4 files changed, 117 insertions(+), 9 deletions(-)
>
> Queued to next-net.
> Fixed the fuzz (file offset) differences in release note and test
Please no, I did some comments on this v10.
I wait for a reply, and probably a new version.
prev parent reply other threads:[~2025-09-10 17:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 11:31 [PATCH] " 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
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-10 0:50 ` Stephen Hemminger
2025-09-10 17:21 ` Thomas Monjalon [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=5008943.GXAFRqVoOG@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).