From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, "Doherty, Declan" <declan.doherty@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
"John Daley (johndale)" <johndale@cisco.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v1 0/4] doc: announce API changes for flow rules
Date: Wed, 14 Feb 2018 16:55:25 +0100 [thread overview]
Message-ID: <20180214155525.psiopmzfzzffezm7@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <20180214152847.19774-1-adrien.mazarguil@6wind.com>
On Wed, Feb 14, 2018 at 04:37:26PM +0100, Adrien Mazarguil wrote:
> Series of API/ABI change announcements for rte_flow to enable proper
> encap/decap support and address various design issues that can't be
> addressed without ABI impact.
>
> Adrien Mazarguil (4):
> doc: announce API change for flow actions
> doc: announce API change for flow RSS action
> doc: announce API change for flow RSS/RAW actions
> doc: announce API change for flow VLAN pattern item
>
> doc/guides/rel_notes/deprecation.rst | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> --
> 2.11.0
For the series,
Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2018-02-14 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 15:37 Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 1/4] doc: announce API change for flow actions Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 2/4] doc: announce API change for flow RSS action Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 3/4] doc: announce API change for flow RSS/RAW actions Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 4/4] doc: announce API change for flow VLAN pattern item Adrien Mazarguil
2018-02-14 15:55 ` Nélio Laranjeiro [this message]
2018-02-14 16:06 ` [dpdk-dev] [PATCH v1 0/4] doc: announce API changes for flow rules Andrew Rybchenko
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=20180214155525.psiopmzfzzffezm7@laranjeiro-vm.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
--cc=nhorman@tuxdriver.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=xuemingl@mellanox.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).