DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "Padubidri, Sanjay A" <sanjay.padubidri@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: remove redundant information from the guide
Date: Thu, 9 May 2019 15:21:44 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F615DAF@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20190506090012.30302-1-vipin.varghese@intel.com>



> -----Original Message-----
> From: Varghese, Vipin
> Sent: Monday, May 6, 2019 10:00 AM
> To: dev@dpdk.org; Kovacevic, Marko <marko.kovacevic@intel.com>; Mcnamara,
> John <john.mcnamara@intel.com>
> Cc: Padubidri, Sanjay A <sanjay.padubidri@intel.com>; Varghese, Vipin
> <vipin.varghese@intel.com>
> Subject: [PATCH v2] doc: remove redundant information from the guide
> 
> Remove redundant information from section Performance issue isolation.
> Re-word for section header for packet capture.
> 


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

  parent reply	other threads:[~2019-05-09 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  4:21 [dpdk-dev] [PATCH] doc: remove redudant information from guide Vipin Varghese
2019-05-06  4:21 ` Vipin Varghese
2019-05-06  9:00 ` [dpdk-dev] [PATCH v2] doc: remove redundant information from the guide Vipin Varghese
2019-05-06  9:00   ` Vipin Varghese
2019-05-09 15:21   ` Mcnamara, John [this message]
2019-05-09 15:21     ` Mcnamara, John
2019-05-09 22:34     ` Thomas Monjalon
2019-05-09 22: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=B27915DBBA3421428155699D51E4CFE23F615DAF@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@intel.com \
    --cc=sanjay.padubidri@intel.com \
    --cc=vipin.varghese@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).