From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add a user guidance document for igb
Date: Thu, 8 Feb 2018 13:49:57 +0000 [thread overview]
Message-ID: <e247efbb-2e63-f825-72a2-f5d4f5f7e9b3@intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E71AD65087@SHSMSX103.ccr.corp.intel.com>
On 2/7/2018 7:12 AM, Zhang, Helin wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mcnamara, John
>> Sent: Monday, February 5, 2018 5:35 PM
>> To: Zhao1, Wei; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v3] doc: add a user guidance document for igb
>>
>>
>>
>>> -----Original Message-----
>>> From: Zhao1, Wei
>>> Sent: Friday, February 2, 2018 3:30 AM
>>> To: dev@dpdk.org
>>> Cc: Mcnamara, John <john.mcnamara@intel.com>; Zhao1, Wei
>>> <wei.zhao1@intel.com>
>>> Subject: [PATCH v3] doc: add a user guidance document for igb
>>>
>>> This patch add a user guidance document specific for igb nic.
>>> By now, a doc like ixgbe.rst is also needed by igb nic. So this patch
>>> add igb.rst to record important information about igb, like feature
>>> supported and known issues.
>>>
>>
>>
>> Acked-by: John McNamara <john.mcnamara@intel.com>
> Applied to dpdk-next-net-intel, with commit log modifications. Thanks!
Pulled from next-net-intel, "igb" added to index.rst while merging to next-net.
next prev parent reply other threads:[~2018-02-08 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:40 [dpdk-dev] [PATCH] " Wei Zhao
2018-01-31 8:47 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-02-01 9:13 ` Mcnamara, John
2018-02-02 3:38 ` Zhao1, Wei
2018-02-02 3:29 ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-02-05 9:34 ` Mcnamara, John
2018-02-07 7:12 ` Zhang, Helin
2018-02-08 13:49 ` Ferruh Yigit [this message]
2018-02-08 11:38 ` Ferruh Yigit
2018-02-08 12:27 ` Mcnamara, John
2018-02-08 12:30 ` Ferruh Yigit
2018-02-13 3:30 ` Zhao1, Wei
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=e247efbb-2e63-f825-72a2-f5d4f5f7e9b3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=wei.zhao1@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).