DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com
Subject: Re: [dpdk-dev] [PATCH] mbuf: promote some helpers to stable
Date: Mon, 4 Oct 2021 12:29:42 -0700	[thread overview]
Message-ID: <20211004122942.3b9dad7a@hermes.local> (raw)
In-Reply-To: <20211002141614.14784-1-david.marchand@redhat.com>

On Sat,  2 Oct 2021 16:16:14 +0200
David Marchand <david.marchand@redhat.com> wrote:

> Those accessors have been introduced more than two years ago
> (rte_mbuf_to_priv in v18.05, rte_mbuf_*_addr* in v19.02).
> Time to mark them stable.
> 
> rte_mbuf_to_baddr() could be removed, but since we lack a deprecation
> notice, keep it as a simple wrapper.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  reply	other threads:[~2021-10-04 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 14:16 David Marchand
2021-10-04 19:29 ` Stephen Hemminger [this message]
2021-10-05  7:33   ` Olivier Matz
2021-10-05  7:34     ` Andrew Rybchenko
2021-10-05  8:20       ` David Marchand

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=20211004122942.3b9dad7a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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;
as well as URLs for NNTP newsgroup(s).