From: Andrew Rybchenko <arybchenko@solarflare.com>
To: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: declare tx prepare api as not experimental
Date: Fri, 11 Jan 2019 16:32:08 +0300 [thread overview]
Message-ID: <a66232f5-9b7f-fe2d-d27b-6d67653278f9@solarflare.com> (raw)
In-Reply-To: <1547212498-14999-1-git-send-email-david.marchand@redhat.com>
On 1/11/19 4:14 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: Andrew Rybchenko <arybchenko@solarflare.com>
with few nits: tx -> Tx, api -> API
next prev parent reply other threads:[~2019-01-11 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 13:14 David Marchand
2019-01-11 13:30 ` Ferruh Yigit
2019-01-11 13:32 ` Andrew Rybchenko [this message]
2019-01-11 13:53 ` Ananyev, Konstantin
2019-01-11 14:11 ` [dpdk-dev] [PATCH v2] ethdev: declare Tx prepare API " David Marchand
2019-01-11 16:52 ` Ferruh Yigit
2019-01-11 17:19 ` 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=a66232f5-9b7f-fe2d-d27b-6d67653278f9@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).