From: "Qiu, Michael" <michael.qiu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2 v2] fm10k: update doc for Atwood Channel
Date: Fri, 5 Feb 2016 05:04:05 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028622F38F45@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1838815.DS5HQ19sJV@xps13>
On 2/4/2016 5:05 PM, Thomas Monjalon wrote:
> Hi Michael,
>
> 2016-02-04 16:36, Michael Qiu:
>> Atwood Channel is 25GbE NIC and belongs to Intel FM10K family,
>> update the doc for it.
>>
>> Signed-off-by: Michael Qiu <michael.qiu@intel.com>
>> Acked-by: John McNamara <john.mcnamara@intel.com>
> Next time, it would be better to send the doc changes and the related code
> changes in the same patch. Thanks
OK, I will do it next time.
Thanks,
Michael
next prev parent reply other threads:[~2016-02-05 5:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 7:28 [dpdk-dev] [PATCH 1/2] fm10k: Add Atwood Channel Support Michael Qiu
2016-01-11 7:28 ` [dpdk-dev] [PATCH 2/2] fm10k: update doc for Atwood Channel Michael Qiu
2016-01-12 13:31 ` Mcnamara, John
2016-02-03 7:25 ` Chen, Jing D
2016-01-12 13:31 ` [dpdk-dev] [PATCH 1/2] fm10k: Add Atwood Channel Support Mcnamara, John
2016-02-04 8:36 ` [dpdk-dev] [PATCH 1/2 v2] " Michael Qiu
2016-02-04 8:36 ` [dpdk-dev] [PATCH 2/2 v2] fm10k: update doc for Atwood Channel Michael Qiu
2016-02-04 9:03 ` Thomas Monjalon
2016-02-05 5:04 ` Qiu, Michael [this message]
2016-02-04 8:40 ` [dpdk-dev] [PATCH 1/2 v2] fm10k: Add Atwood Channel Support Chen, Jing D
2016-02-04 13:55 ` Liu, Yong
2016-03-09 8:56 ` Qiu, Michael
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=533710CFB86FA344BFBF2D6802E6028622F38F45@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).