From: Stephen Hemminger <stephen@networkplumber.org>
To: Zhanibek Bakin <zhanibek.bakin@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [ethdev]: question about the experimental functions
Date: Tue, 10 Feb 2026 06:24:29 -0800 [thread overview]
Message-ID: <20260210062429.6c1b4230@phoenix.local> (raw)
In-Reply-To: <CACRNuqcKD6QucokYg=O+WoGXGnMwTEkYWyjyeoxKDoT6_BB1RA@mail.gmail.com>
On Tue, 10 Feb 2026 10:56:09 +0500
Zhanibek Bakin <zhanibek.bakin@gmail.com> wrote:
> Hi there,
>
> I have a question about the experimental
> functions: rte_eth_dev_get_module_eeprom() &
> rte_eth_dev_get_module_info().
>
> From what I can see, they have been marked experimental for quite some
> time(7+ years).
> On top of that, I don't see they are going to become "stable" in the next
> DPDK 26 version.
>
> Can I know the reason for this? As I would love to use them, however, it
> would be a shame if they change any time soon.
>
> Thank you for your help.
>
> Best regards,
> Zhanibek Bakin
Almost all functions that have been around a year or more should
be marked stable. It is just that nobody submitted patch to change
these.
prev parent reply other threads:[~2026-02-10 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 5:56 [ethdev]: question about the experimental functions Zhanibek Bakin
2026-02-10 14:24 ` Stephen Hemminger [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=20260210062429.6c1b4230@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=zhanibek.bakin@gmail.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