From: Thomas Monjalon <thomas@monjalon.net>
To: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
stephen@networkplumber.org, david.marchand@redhat.com,
mdr@ashroe.eu
Subject: Re: [dpdk-dev] [PATCH v2] doc: add deprecation notice on EAL mem config
Date: Mon, 13 May 2019 23:03:04 +0200 [thread overview]
Message-ID: <7849576.mvPdfgfWhC@xps> (raw)
Message-ID: <20190513210304.qxixYLqBeWzfTiSVN3BbAh9z-nLAch62wVlszHfxbk8@z> (raw)
In-Reply-To: <20190510093404.GC76@bricha3-MOBL.ger.corp.intel.com>
10/05/2019 11:34, Bruce Richardson:
> On Fri, May 10, 2019 at 10:31:21AM +0100, Burakov, Anatoly wrote:
> > On 09-May-19 7:51 PM, Erik Gabriel Carrillo wrote:
> > > It is planned to make the rte_mem_config struct of the EAL private to
> > > remove it from the visible ABI. Add a notice to announce the intention.
> > >
> > > Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
> > > ---
> > > changes in v2:
> > > - Original deprecation notice announced a change to the rte_mem_config
> > > struct that would break ABI. Update the notice to instead announce
> > > the struct will be made private. (Stephen, Anatoly, David)
> > >
> > > --- a/doc/guides/rel_notes/deprecation.rst
> > > +++ b/doc/guides/rel_notes/deprecation.rst
> > > +* eal: the ``rte_mem_config`` struct will be made private to remove it from the
> > > + externally visible ABI and allow it to be updated in the future.
> >
> > Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: David Marchand <david.marchand@redhat.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-13 21:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 22:48 [dpdk-dev] [PATCH] doc: add deprecation notice on timer lib cleanup Erik Gabriel Carrillo
2019-05-08 22:48 ` Erik Gabriel Carrillo
2019-05-09 1:11 ` Stephen Hemminger
2019-05-09 1:11 ` Stephen Hemminger
2019-05-09 7:05 ` David Marchand
2019-05-09 7:05 ` David Marchand
2019-05-09 8:33 ` Burakov, Anatoly
2019-05-09 8:33 ` Burakov, Anatoly
2019-05-09 9:06 ` Bruce Richardson
2019-05-09 9:06 ` Bruce Richardson
2019-05-09 9:37 ` Burakov, Anatoly
2019-05-09 9:37 ` Burakov, Anatoly
2019-05-09 9:38 ` Thomas Monjalon
2019-05-09 9:38 ` Thomas Monjalon
2019-05-09 9:50 ` Ray Kinsella
2019-05-09 9:50 ` Ray Kinsella
2019-05-09 10:08 ` Burakov, Anatoly
2019-05-09 10:08 ` Burakov, Anatoly
2019-05-09 19:02 ` Stephen Hemminger
2019-05-09 19:02 ` Stephen Hemminger
2019-05-10 14:42 ` Stephen Hemminger
2019-05-10 14:42 ` Stephen Hemminger
2019-05-09 11:53 ` Burakov, Anatoly
2019-05-09 11:53 ` Burakov, Anatoly
2019-05-09 18:51 ` [dpdk-dev] [PATCH v2] doc: add deprecation notice on EAL mem config Erik Gabriel Carrillo
2019-05-09 18:51 ` Erik Gabriel Carrillo
2019-05-10 9:31 ` Burakov, Anatoly
2019-05-10 9:31 ` Burakov, Anatoly
2019-05-10 9:34 ` Bruce Richardson
2019-05-10 9:34 ` Bruce Richardson
2019-05-13 21:03 ` Thomas Monjalon [this message]
2019-05-13 21:03 ` Thomas Monjalon
2019-05-10 13:44 ` David Marchand
2019-05-10 13:44 ` 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=7849576.mvPdfgfWhC@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=mdr@ashroe.eu \
--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).