From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: web@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>,
Ed Czeck <ed.czeck@atomicrules.com>,
John Daley <johndale@cisco.com>,
Nelson Escobar <neescoba@cisco.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Stephen Hurd <stephen.hurd@broadcom.com>
Subject: Re: [dpdk-web] [PATCH 1/3] move ark pmd back to 17.05
Date: Thu, 06 Apr 2017 16:57:59 +0200 [thread overview]
Message-ID: <2727740.r8U1dgMsgJ@xps13> (raw)
In-Reply-To: <20170406143539.16391-1-ferruh.yigit@intel.com>
Series applied, thanks
http://dpdk.org/dev/roadmap
prev parent reply other threads:[~2017-04-06 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 14:35 Ferruh Yigit
2017-04-06 14:35 ` [dpdk-web] [PATCH 2/3] move bnxt pmd update to 17.08 Ferruh Yigit
2017-04-06 14:35 ` [dpdk-web] [PATCH 3/3] announce enic pmd update for 17.08 Ferruh Yigit
2017-04-06 14:57 ` Thomas Monjalon [this message]
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=2727740.r8U1dgMsgJ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=ed.czeck@atomicrules.com \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.com \
--cc=shepard.siegel@atomicrules.com \
--cc=stephen.hurd@broadcom.com \
--cc=web@dpdk.org \
/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).