DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sunil Kumar Kori <skori@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
Subject: RE: [EXTERNAL] Re: [PATCH v5 1/1] ethdev: add support to provide link type
Date: Wed, 20 Aug 2025 09:55:56 +0000	[thread overview]
Message-ID: <CO6PR18MB38601A277170C0571CF9107AB433A@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250819092927.739f64ec@hermes.local>

> On Tue, 19 Aug 2025 11:21:06 +0530
> <skori@marvell.com> wrote:
> 
> > +/**@{@name PORT type
> > + * Ethernet port link connector type
> > + */
> > +enum rte_eth_link_connector {
> > +	RTE_ETH_LINK_CONNECTOR_NONE = 0,     /**< Not defined */
> > +	RTE_ETH_LINK_CONNECTOR_TP,           /**< Twisted Pair */
> > +	RTE_ETH_LINK_CONNECTOR_AUI,          /**< Attachment Unit Interface */
> > +	RTE_ETH_LINK_CONNECTOR_MII,          /**< Media Independent Interface
> */
> > +	RTE_ETH_LINK_CONNECTOR_FIBER,        /**< Optical Fiber Link */
> > +	RTE_ETH_LINK_CONNECTOR_BNC,          /**< BNC Link type for RF
> connection */
> > +	RTE_ETH_LINK_CONNECTOR_DAC,          /**< Direct Attach copper */
> > +	RTE_ETH_LINK_CONNECTOR_SGMII,        /**< Serial Gigabit Media
> Independent Interface */
> > +	RTE_ETH_LINK_CONNECTOR_QSGMII,       /**< Link to multiplex 4 SGMII
> over one serial link */
> > +	RTE_ETH_LINK_CONNECTOR_XFI,          /**< 10 Gigabit Attachment Unit
> Interface */
> > +	RTE_ETH_LINK_CONNECTOR_SFI,          /**< 10 Gigabit Serial Interface for
> optical network */
> > +	RTE_ETH_LINK_CONNECTOR_XLAUI,        /**< 40 Gigabit Attachment Unit
> Interface */
> > +	RTE_ETH_LINK_CONNECTOR_GAUI,         /**< Gigabit Interface for
> 50/100/200 Gbps */
> > +	RTE_ETH_LINK_CONNECTOR_XAUI,         /**< 10 Gigabit Attachment Unit
> Interface */
> > +	RTE_ETH_LINK_CONNECTOR_CAUI,         /**< 100 Gigabit Attachment Unit
> Interface */
> > +	RTE_ETH_LINK_CONNECTOR_LAUI,         /**< 50 Gigabit Attachment Unit
> Interface */
> > +	RTE_ETH_LINK_CONNECTOR_SFP,          /**< Pluggable module for 1
> Gigabit */
> > +	RTE_ETH_LINK_CONNECTOR_SFP_PLUS,     /**< Pluggable module for 10
> Gigabit */
> > +	RTE_ETH_LINK_CONNECTOR_SFP28,        /**< Pluggable module for 25
> Gigabit */
> > +	RTE_ETH_LINK_CONNECTOR_SFP_DD,       /**< Pluggable module for 100
> Gigabit */
> > +	RTE_ETH_LINK_CONNECTOR_QSFP,         /**< Module to mutiplex 4 SFP i.e.
> 4*1=4 Gbps */
> > +	RTE_ETH_LINK_CONNECTOR_QSFP_PLUS,    /**< Module to mutiplex 4
> SFP_PLUS i.e. 4*10=40 Gbps */
> > +	RTE_ETH_LINK_CONNECTOR_QSFP28,       /**< Module to mutiplex 4 SFP28
> i.e. 4*25=100 Gbps */
> > +	RTE_ETH_LINK_CONNECTOR_QSFP56,       /**< Module to mutiplex 4 SFP56
> i.e. 4*50=200 Gbps */
> > +	RTE_ETH_LINK_CONNECTOR_QSFP_DD,      /**< Module to mutiplex 4
> SFP_DD i.e. 4*100=400 Gbps */
> > +	RTE_ETH_LINK_CONNECTOR_OTHER = 31,   /**< non-physical interfaces
> like virtio, ring etc */
> > +};
> > +/**@}*/
> > +
> 
> doc build fails when you add this.
> 
> Please test.
> 
> [30/1996] Generating doxygen-html with a custom command
> FAILED: [code=1] doc/api/html
> /usr/bin/python3 ../doc/api/generate_doxygen.py doc/api/html
> /usr/bin/doxygen doc/api/doxy-api-html.conf
> /home/runner/work/dpdk/dpdk/lib/ethdev/rte_ethdev.h:335: error: Member
> rte_eth_link_connector (enumeration) of file rte_ethdev.h is not documented.
> (warning treated as error, aborting now) Traceback (most recent call last):
>   File "/home/runner/work/dpdk/dpdk/build/../doc/api/generate_doxygen.py",
> line 13, in <module>
>     subprocess.run(doxygen_command, check=True, stdout=out)
>   File "/usr/lib/python3.10/subprocess.py", line 526, in run
>     raise CalledProcessError(retcode, process.args,
> subprocess.CalledProcessError: Command '['/usr/bin/doxyg

My bad, I didn’t notice this. Thanks for pointing it. 

  reply	other threads:[~2025-08-20  9:56 UTC|newest]

Thread overview: 33+ 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           ` Sunil Kumar Kori [this message]
2025-08-20 11:13         ` [PATCH v6 " skori
2025-08-20 12:51           ` Morten Brørup

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=CO6PR18MB38601A277170C0571CF9107AB433A@CO6PR18MB3860.namprd18.prod.outlook.com \
    --to=skori@marvell.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ndabilpuram@marvell.com \
    --cc=stephen@networkplumber.org \
    --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 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).