DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] doc: add deprecation notice about upcoming change to ethdev API
Date: Wed, 15 Jul 2026 10:15:18 +0100	[thread overview]
Message-ID: <aldPpq_U633rZTPN@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260603023207.31974-1-stephen@networkplumber.org>

On Tue, Jun 02, 2026 at 07:32:07PM -0700, Stephen Hemminger wrote:
> Inform users that rte_eth_dev_get_name_by_port() will add a size
> parameter in next release.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>


>  doc/guides/rel_notes/deprecation.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 17f90a6352..d390a1640a 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -158,3 +158,7 @@ Deprecation Notices
>  * net/iavf: The dynamic mbuf field used to detect LLDP packets on the
>    transmit path in the iavf PMD will be removed in a future release.
>    After removal, only packet type-based detection will be supported.
> +
> +* ethdev: Starting in 26.11, the function ``rte_eth_dev_get_name_by_port()``
> +  will take a size parameter as well as the string buffer.
> +  This will detect and prevent accidental overwriting of caller provided buffer.
> -- 
> 2.53.0
> 

  reply	other threads:[~2026-07-15  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  2:32 [PATCH] doc: add deprecation notice about upcoming change to ethdev API Stephen Hemminger
2026-07-15  9:15 ` Bruce Richardson [this message]
2026-07-21 10:07 ` David Marchand
2026-07-21 10:24   ` Nithin Dabilpuram
2026-07-22 12:57     ` Thomas Monjalon
2026-07-21 10:25   ` Jerin Jacob

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=aldPpq_U633rZTPN@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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