DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Yang, Qiming" <qiming.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add i40e firmware upgrade guide
Date: Mon, 4 Sep 2017 16:35:05 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23ED9E143@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1502767615-13240-1-git-send-email-qiming.yang@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiming Yang
> Sent: Tuesday, August 15, 2017 4:27 AM
> To: dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Yang, Qiming <qiming.yang@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: add i40e firmware upgrade guide
> 
> This patch adds one link to DPDK i40e doc, which is for users on how to
> upgrade firmware.
> 
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>


> +- Upgrade the NVM/FW version follow the `Intel® Ethernet NVM Update
> +Tool Quick Usage Guide for Linux
> +  <https://www-
> ssl.intel.com/content/www/us/en/embedded/products/networking/nvm-update-
> tool-quick-linux-usage-guide.html>`_ if need.
> 

Slightly better would be:

s/follow/following/
s/if need/if needed/

But these changes could be make inline during commit so:

Acked-by: John McNamara <john.mcnamara@intel.com>



  parent reply	other threads:[~2017-09-04 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  3:26 Qiming Yang
2017-08-15  8:52 ` Ferruh Yigit
2017-08-16  9:12   ` Yang, Qiming
2017-09-04 16:35 ` Mcnamara, John [this message]
2017-09-05  9:41   ` Ferruh Yigit

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=B27915DBBA3421428155699D51E4CFE23ED9E143@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=qiming.yang@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).