From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Yongseok Koh <yskoh@mellanox.com>
Cc: konstantin.ananyev@intel.com, olivier.matz@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] mbuf: remove deprecated macro
Date: Mon, 14 Jan 2019 10:50:50 +0100 [thread overview]
Message-ID: <2069315.XgEaZRbMEa@xps> (raw)
In-Reply-To: <210872a4-5e85-bef3-dca1-2e468be373bb@solarflare.com>
14/01/2019 08:40, Andrew Rybchenko:
> On 1/14/19 8:20 AM, Yongseok Koh wrote:
> > RTE_MBUF_INDIRECT() is replaced with RTE_MBUF_CLONED() and removed.
> > This macro was deprecated in release 18.05 when EXT_ATTACHED_MBUF was
> > introduced.
> >
> > Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
>
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
>
> <...>
>
> > diff --git a/doc/guides/rel_notes/release_19_02.rst b/doc/guides/rel_notes/release_19_02.rst
> > index 5a46f1acdc..c4ad072412 100644
> > --- a/doc/guides/rel_notes/release_19_02.rst
> > +++ b/doc/guides/rel_notes/release_19_02.rst
> > @@ -210,6 +210,9 @@ API Changes
> > function from now on. Failed to do so will cause
> > ``rte_cryptodev_sym_session_create()`` function call return error.
> >
> > +* mbuf: ``RTE_MBUF_INDIRECT()``, which was deprecated in 18.05, was replaced
> > + with ``RTE_MBUF_CLONED()`` and removed in 19.02.
> > +
>
> May be order in New Features should be applicable in API changes as well.
Yes
Usually I take care of it when applying, but would be better to be fixed
in the patch itself :)
next prev parent reply other threads:[~2019-01-14 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 5:20 Yongseok Koh
2019-01-14 5:20 ` [dpdk-dev] [PATCH 2/2] mbuf: remove experimental tag of external buffer attachment Yongseok Koh
2019-01-14 7:42 ` Andrew Rybchenko
2019-01-14 15:22 ` Olivier Matz
2019-01-14 7:40 ` [dpdk-dev] [PATCH 1/2] mbuf: remove deprecated macro Andrew Rybchenko
2019-01-14 9:50 ` Thomas Monjalon [this message]
2019-01-14 15:23 ` Olivier Matz
2019-01-14 15:40 ` Thomas Monjalon
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=2069315.XgEaZRbMEa@xps \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=yskoh@mellanox.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).