From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
Stephen Hemminger <stephen@networkplumber.org>,
dev <dev@dpdk.org>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH] mbuf: promote some helpers to stable
Date: Tue, 5 Oct 2021 10:20:29 +0200 [thread overview]
Message-ID: <CAJFAV8y38xABieOPetcd0WG8b7gQK6vD8P+mrDghV+ZMUNUesQ@mail.gmail.com> (raw)
In-Reply-To: <5e7778e3-d62e-f259-070a-8ac3c2ca696a@oktetlabs.ru>
On Tue, Oct 5, 2021 at 9:34 AM Andrew Rybchenko
<andrew.rybchenko@oktetlabs.ru> wrote:
>
> On 10/5/21 10:33 AM, Olivier Matz wrote:
> > On Mon, Oct 04, 2021 at 12:29:42PM -0700, Stephen Hemminger wrote:
> >> 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).
rte_mbuf_to_priv was introduced in v18.08. Fixed when applying.
> >>> 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>
> > Acked-by: Olivier Matz <olivier.matz@6wind.com>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Applied.
--
David Marchand
prev parent reply other threads:[~2021-10-05 8:20 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
2021-10-05 7:33 ` Olivier Matz
2021-10-05 7:34 ` Andrew Rybchenko
2021-10-05 8:20 ` David Marchand [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=CAJFAV8y38xABieOPetcd0WG8b7gQK6vD8P+mrDghV+ZMUNUesQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).