From: Thomas Monjalon <thomas@monjalon.net>
To: Gage Eads <gage.eads@intel.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, mdr@ashroe.eu,
nhorman@tuxdriver.com, phil.yang@arm.com,
honnappa.nagarahalli@arm.com
Subject: Re: [dpdk-dev] [20.11] [PATCH v2] stack: remove experimental tag from API
Date: Thu, 28 May 2020 17:29:41 +0200 [thread overview]
Message-ID: <7469181.umUMbf5e9f@thomas> (raw)
In-Reply-To: <20200528150442.321-1-gage.eads@intel.com>
28/05/2020 17:04, Gage Eads:
> The stack library was first released in 19.05, and its interfaces have been
> stable since their initial introduction. This commit promotes the full
> interface to stable, starting with the 20.11 major version.
>
> Signed-off-by: Gage Eads <gage.eads@intel.com>
> ---
> doc/guides/rel_notes/release_20_11.rst | 3 +++
> lib/librte_stack/rte_stack.h | 29 -----------------------------
> lib/librte_stack/rte_stack_lf.h | 2 --
> lib/librte_stack/rte_stack_std.h | 3 ---
> lib/librte_stack/rte_stack_version.map | 2 +-
> 5 files changed, 4 insertions(+), 35 deletions(-)
>
> v2:
> - Added 20.11 tag, will set patch status to 'Deferred' so it is skipped
> for the 20.08 development period.
> - Added release notes announcement. release_20_11.rst doesn't exist yet,
> so I made the change to release_20_08.rst then edited the filename
> directly in the patch. This will not apply cleanly.
> - Changed rte_stack_version.map version to DPDK_21.
I think you did it right.
next prev parent reply other threads:[~2020-05-28 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 1:04 [dpdk-dev] [PATCH] " Gage Eads
2020-05-28 5:46 ` Ray Kinsella
2020-05-28 8:10 ` Thomas Monjalon
2020-05-28 8:22 ` Ray Kinsella
2020-05-28 14:18 ` Eads, Gage
2020-05-28 14:33 ` Bruce Richardson
2020-05-28 15:04 ` [dpdk-dev] [20.11] [PATCH v2] " Gage Eads
2020-05-28 15:29 ` Thomas Monjalon [this message]
2020-09-30 18:49 ` David Marchand
2020-09-30 21:39 ` [dpdk-dev] [PATCH] " Gage Eads
2020-10-05 9:07 ` Kinsella, Ray
2020-10-05 9:53 ` Kinsella, Ray
2020-10-05 12:57 ` 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=7469181.umUMbf5e9f@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=phil.yang@arm.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).