From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Pei, Yulong" <yulong.pei@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add tested platforms and nics and OSes
Date: Tue, 07 Feb 2017 11:30:14 +0100 [thread overview]
Message-ID: <1536831.f8OfG4YADt@xps13> (raw)
In-Reply-To: <188971FCDA171749BED5DA74ABF3E6F03B68950B@shsmsx102.ccr.corp.intel.com>
2017-02-04 03:57, Pei, Yulong:
> Hi Thomas,
>
> Did you notice this patch ? do you have any comments ?
Hi,
For this patch, I prefer waiting the go (ack) from John.
next prev parent reply other threads:[~2017-02-07 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1485160698-5252-1-git-send-email-yulong.pei@intel.com>
2017-02-04 3:57 ` Pei, Yulong
2017-02-07 10:30 ` Thomas Monjalon [this message]
2017-02-09 8:42 ` Nélio Laranjeiro
2017-02-13 18:06 ` Thomas Monjalon
2017-02-08 17:53 ` Mcnamara, John
2017-02-14 0:31 ` Mcnamara, John
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=1536831.f8OfG4YADt@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@intel.com \
--cc=yulong.pei@intel.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).