From: "Eads, Gage" <gage.eads@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
"gavin.hu@arm.com" <gavin.hu@arm.com>,
"Ola.Liljedahl@arm.com" <Ola.Liljedahl@arm.com>,
"nd@arm.com" <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: announce ring API change
Date: Fri, 10 May 2019 14:53:56 +0000 [thread overview]
Message-ID: <9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com> (raw)
Message-ID: <20190510145356.mI5EEWB_0gk2FqpJMiFlvZQjZ7iDSyfSNwxcekDfYQA@z> (raw)
In-Reply-To: <1845234.OyIqJ6yfKh@xps>
> 01/02/2019 15:36, Gage Eads:
> > In order to support the non-blocking ring[1], an API change
> > (additional argument to rte_ring_get_memsize()) is required in
> > librte_ring. This commit updates the deprecation notice to pave the
> > way for its inclusion in 19.08.
> >
> > [1] http://mails.dpdk.org/archives/dev/2019-January/124162.html
> >
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
>
> There is still no agreement on this change?
>
Still none. I was hoping this discussion (http://mails.dpdk.org/archives/dev/2019-April/129229.html) would lead to some clear direction, but at this point the effort is stalled.
next prev parent reply other threads:[~2019-05-10 14:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 23:59 [dpdk-dev] [PATCH] doc: announce ring ABI and API changes Gage Eads
2019-01-16 0:34 ` Stephen Hemminger
2019-01-16 18:21 ` Eads, Gage
2019-01-18 15:28 ` [dpdk-dev] [PATCH v2] doc: announce ring API change Gage Eads
2019-01-18 15:31 ` [dpdk-dev] [PATCH v3] " Gage Eads
2019-02-01 11:16 ` Thomas Monjalon
2019-02-01 14:18 ` Eads, Gage
2019-02-01 14:36 ` [dpdk-dev] [PATCH v4] " Gage Eads
2019-05-09 23:29 ` Thomas Monjalon
2019-05-09 23:29 ` Thomas Monjalon
2019-05-10 14:53 ` Eads, Gage [this message]
2019-05-10 14:53 ` Eads, Gage
2019-05-10 14:58 ` Stephen Hemminger
2019-05-10 14:58 ` Stephen Hemminger
2019-05-10 15:19 ` Ola Liljedahl
2019-05-10 15:19 ` Ola Liljedahl
2019-05-10 16:28 ` Eads, Gage
2019-05-10 16:28 ` Eads, Gage
2019-05-13 11:46 ` Olivier Matz
2019-05-13 11:46 ` Olivier Matz
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=9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com \
--to=gage.eads@intel.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ola.Liljedahl@arm.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).