From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes for e1000 base code update
Date: Wed, 4 Nov 2015 09:59:13 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202398DC1@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1446444820-13846-1-git-send-email-wenzhuo.lu@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wenzhuo Lu
> Sent: Monday, November 2, 2015 6:14 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: update release notes for e1000 base code
> update
>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
There are a few very minor changes that could be made but rather than re-spinning the patch I'll make them in the final review pass of the release notes.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2015-11-04 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 6:13 Wenzhuo Lu
2015-11-04 9:59 ` Mcnamara, John [this message]
2015-12-13 23:00 ` 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=B27915DBBA3421428155699D51E4CFE202398DC1@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@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).