From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [PATCH v2] doc: document NIC features
Date: Sun, 2 Jul 2017 20:20:47 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23ED1DEFD@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20170622190233.67933-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Thursday, June 22, 2017 8:03 PM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>; Olivier Matz <olivier.matz@6wind.com>
> Subject: [PATCH v2] doc: document NIC features
>
> Document NIC features, add more information about them and add more
> implementation related support.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
This is a good idea and a good start. I'll send you some additions you can use
for a V2. Agreed that it would be good to get more community input for this.
next prev parent reply other threads:[~2017-07-02 20:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 16:37 [RFC] doc: document NIC features Ferruh Yigit
2017-06-21 13:25 ` [PATCH] " Ferruh Yigit
2017-06-22 19:02 ` [PATCH v2] " Ferruh Yigit
2017-07-02 20:20 ` Mcnamara, John [this message]
2017-07-05 13:20 ` [PATCH v3] " Ferruh Yigit
2017-07-05 16:03 ` Mcnamara, John
2017-07-07 10:55 ` Andrew Rybchenko
2017-07-07 13:37 ` Ferruh Yigit
2017-07-07 13:53 ` Thomas Monjalon
2017-07-07 13:57 ` Ferruh Yigit
2017-07-07 14:02 ` Thomas Monjalon
2017-07-07 14:13 ` Ferruh Yigit
2017-07-07 14:20 ` Wiles, Keith
2017-07-07 20:37 ` Thomas Monjalon
2017-07-07 23:54 ` Wiles, Keith
2017-07-07 15:06 ` Ferruh Yigit
2017-07-07 15:38 ` Andrew Rybchenko
2017-07-07 17:21 ` [PATCH v4] " Ferruh Yigit
2017-07-08 9:47 ` Andrew Rybchenko
2017-07-20 9:10 ` Ferruh Yigit
2017-07-20 9:23 ` [PATCH v5] " Ferruh Yigit
2017-07-26 5:08 ` Shreyansh Jain
2017-08-01 10:15 ` Ferruh Yigit
2017-08-01 15:23 ` [PATCH v6] " Ferruh Yigit
2017-08-03 8:56 ` Shreyansh Jain
2017-08-03 8:57 ` Shreyansh Jain
2017-08-03 10:42 ` Mcnamara, John
2017-08-03 22:57 ` Thomas Monjalon
2017-08-04 8:56 ` Ferruh Yigit
2017-08-04 9:32 ` Thomas Monjalon
2017-08-04 10:04 ` Ferruh Yigit
2017-08-04 10:10 ` Thomas Monjalon
2017-08-04 11:11 ` Mcnamara, John
2017-08-04 11:40 ` Ferruh Yigit
2017-08-04 13:06 ` [PATCH v7] " Ferruh Yigit
2017-08-04 13:34 ` Mcnamara, John
2017-08-05 9:34 ` 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=B27915DBBA3421428155699D51E4CFE23ED1DEFD@IRSMSX104.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.