From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Marko Kovacevic <marko.kovacevic@intel.com>, web@dpdk.org
Cc: john.mcnamara@intel.com
Subject: Re: [dpdk-web] [PATCH v2] update roadmap for 18.11
Date: Tue, 11 Sep 2018 17:06:43 +0100 [thread overview]
Message-ID: <a78acd76-f2df-6297-b4ae-01ce2457bc6d@intel.com> (raw)
In-Reply-To: <20180911154447.4325-1-marko.kovacevic@intel.com>
On 9/11/2018 4:44 PM, Marko Kovacevic wrote:
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-09-11 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 15:44 Marko Kovacevic
2018-09-11 16:06 ` Ferruh Yigit [this message]
2018-09-11 17:53 ` Thomas Monjalon
2018-09-12 10:59 ` [dpdk-web] [PATCH v3] " Marko Kovacevic
2018-09-12 12:41 ` [dpdk-web] [PATCH v4] update Intel " Thomas Monjalon
2018-09-12 15:10 ` Ferruh Yigit
2018-09-12 16:20 ` Thomas Monjalon
2018-09-12 16:47 ` Ferruh Yigit
2018-10-16 9:18 ` Thomas Monjalon
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=a78acd76-f2df-6297-b4ae-01ce2457bc6d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).