From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Olga Shern <olgas@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 1/3] doc: merge release notes sections
Date: Tue, 14 Feb 2017 00:28:49 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026CB4C8@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <4afaca8471a3c216b0e67e1eb61c52bf99b0566f.1486628949.git.nelio.laranjeiro@6wind.com>
> -----Original Message-----
> From: Nelio Laranjeiro [mailto:nelio.laranjeiro@6wind.com]
> Sent: Thursday, February 9, 2017 8:32 AM
> To: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Thomas
> Monjalon <thomas.monjalon@6wind.com>
> Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>; Olga Shern
> <olgas@mellanox.com>
> Subject: [PATCH 1/3] doc: merge release notes sections
>
> These sections do not provide the exact tests that were done nor whether
> specific NICs are supported by all platforms.
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2017-02-14 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 8:31 [dpdk-dev] [PATCH 0/3] doc: update release notes Nelio Laranjeiro
2017-02-09 8:31 ` [dpdk-dev] [PATCH 1/3] doc: merge release notes sections Nelio Laranjeiro
2017-02-14 0:28 ` Mcnamara, John [this message]
2017-02-09 8:32 ` [dpdk-dev] [PATCH 2/3] doc: update release notes for mlx4 Nelio Laranjeiro
2017-02-14 0:29 ` Mcnamara, John
2017-02-09 8:32 ` [dpdk-dev] [PATCH 3/3] doc: update release notes for mlx5 Nelio Laranjeiro
2017-02-14 0:29 ` Mcnamara, John
2017-02-13 17:48 ` [dpdk-dev] [PATCH 0/3] doc: update release notes Thomas Monjalon
2017-02-13 18:35 ` Mcnamara, John
2017-02-14 13:25 ` 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=B27915DBBA3421428155699D51E4CFE2026CB4C8@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=olgas@mellanox.com \
--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).