From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add mlx5 release notes
Date: Fri, 4 Nov 2016 09:28:42 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20264A60C@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <b3884e8811837a97492d7820edea3351b5407d8a.1478180639.git.nelio.laranjeiro@6wind.com>
> -----Original Message-----
> From: Nelio Laranjeiro [mailto:nelio.laranjeiro@6wind.com]
> Sent: Thursday, November 3, 2016 1:46 PM
> To: dev@dpdk.org
> Cc: Mcnamara, John <john.mcnamara@intel.com>; Adrien Mazarguil
> <adrien.mazarguil@6wind.com>
> Subject: [PATCH v2] doc: add mlx5 release notes
>
> Add list of tested and validated NICs too.
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Hi Nelio,
Nice to see such an extensive list of tested platforms and NICs.
I don't know if it is generally okay to update only part of a patchset
but apart from that:
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2016-11-04 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 13:46 [dpdk-dev] [PATCH 0/2] update mlx5 release note and guide Nelio Laranjeiro
2016-11-02 13:46 ` [dpdk-dev] [PATCH 1/2] doc: update mlx5 dependencies Nelio Laranjeiro
2016-11-03 12:20 ` Mcnamara, John
2016-11-02 13:46 ` [dpdk-dev] [PATCH 2/2] doc: add mlx5 release notes Nelio Laranjeiro
2016-11-03 12:25 ` Mcnamara, John
2016-11-03 12:48 ` Nélio Laranjeiro
2016-11-03 13:45 ` [dpdk-dev] [PATCH v2] " Nelio Laranjeiro
2016-11-04 9:28 ` Mcnamara, John [this message]
2016-11-02 15:58 ` [dpdk-dev] [PATCH 0/2] update mlx5 release note and guide Adrien Mazarguil
2016-11-07 18:09 ` 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=B27915DBBA3421428155699D51E4CFE20264A60C@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@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).