patches for DPDK stable branches
 help / color / mirror / Atom feed
* Re: [dpdk-stable] [PATCH v2] ethdev: declare Tx prepare API as not experimental
       [not found]   ` <16ee2092-551c-42cb-b271-69aab6dba407@intel.com>
@ 2019-01-11 17:19     ` David Marchand
  0 siblings, 0 replies; only message in thread
From: David Marchand @ 2019-01-11 17:19 UTC (permalink / raw)
  To: Ferruh Yigit
  Cc: dev, Thomas Monjalon, Andrew Rybchenko, konstantin.ananyev, dpdk stable

On Fri, Jan 11, 2019 at 5:52 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 1/11/2019 2:11 PM, David Marchand wrote:
> > The Tx prepare API was introduced at a time when the experimental API
> > tag mechanism did not exist yet and is missing the tag.
> > However, this API has been there since 17.02 and did not suffer any
> > change since its introduction.
> >
> > Let's just remove the warning from the documentation.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> > Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>
> Applied to dpdk-next-net/master, thanks.
>

As discussed offlist and on ovs ml, once it reaches master, could we
backport at least to 18.11 ?
Thanks.

-- 
David Marchand

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-01-11 17:19 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1547212498-14999-1-git-send-email-david.marchand@redhat.com>
     [not found] ` <1547215897-22272-1-git-send-email-david.marchand@redhat.com>
     [not found]   ` <16ee2092-551c-42cb-b271-69aab6dba407@intel.com>
2019-01-11 17:19     ` [dpdk-stable] [PATCH v2] ethdev: declare Tx prepare API as not experimental David Marchand

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).