From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Doherty, Declan" <declan.doherty@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [RFC 1/5] version: 17.11.0
Date: Thu, 21 Dec 2017 09:07:26 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC60FA8@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1513805689-28202-2-git-send-email-qi.z.zhang@intel.com>
Hi Qi,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qi Zhang
> Sent: Wednesday, December 20, 2017 9:35 PM
> To: adrien.mazarguil@6wind.com
> Cc: dev@dpdk.org; Doherty, Declan <declan.doherty@intel.com>; Thomas
> Monjalon <thomas@monjalon.net>
> Subject: [dpdk-dev] [RFC 1/5] version: 17.11.0
>
> From: Thomas Monjalon <thomas@monjalon.net>
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> lib/librte_eal/common/include/rte_version.h | 4 ++--
> pkg/dpdk.spec | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Your patchset should not change these files.
Regards,
Pablo
next prev parent reply other threads:[~2017-12-21 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 21:34 [dpdk-dev] [RFC 0/5] rte_flow extension for vSwitch acceleration Qi Zhang
2017-12-20 21:34 ` [dpdk-dev] [RFC 1/5] version: 17.11.0 Qi Zhang
2017-12-21 9:07 ` De Lara Guarch, Pablo [this message]
2017-12-21 9:13 ` Zhang, Qi Z
2017-12-20 21:34 ` [dpdk-dev] [RFC 2/5] ether: add flow action to redirect packet in a switch domain Qi Zhang
2017-12-20 21:34 ` [dpdk-dev] [RFC 3/5] ether: add flow last hit query support Qi Zhang
2017-12-20 21:34 ` [dpdk-dev] [RFC 4/5] ether: Add flow timeout support Qi Zhang
2017-12-20 21:34 ` [dpdk-dev] [RFC 5/5] ether: add packet modification aciton in rte_flow Qi Zhang
2018-01-02 8:12 ` [dpdk-dev] [RFC 0/5] rte_flow extension for vSwitch acceleration Nelio Laranjeiro
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=E115CCD9D858EF4F90C690B0DCB4D8976CC60FA8@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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).