DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Adam Dybkowski <adamx.dybkowski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] doc: document new compress perf option
Date: Wed, 16 Oct 2019 08:39:05 +0000	[thread overview]
Message-ID: <VE1PR04MB663978DCD10E99F84A7CA84BE6920@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191015140930.5981-2-adamx.dybkowski@intel.com>

Hi Adam,

> 
> This patch documents the new compress perf tool
> option --external-mbufs.
> 
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> ---
This patch should have been merged with the 
" app/compress-perf: add --external-mbufs option"

Please make sure that all documentation related patches go in the corresponding code itself.
No separate patch should be there.

Now since the original patch is merged, you should change the title as
"doc: fix missing compress perf option" or something similar.
Please also add a fixes line for the original commit.

Regards,
Akhil



  parent reply	other threads:[~2019-10-16  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 11:37 [dpdk-dev] [PATCH] " Adam Dybkowski
2019-10-15 14:09 ` [dpdk-dev] [PATCH v2 0/1] " Adam Dybkowski
2019-10-15 14:09   ` [dpdk-dev] [PATCH v2 1/1] " Adam Dybkowski
2019-10-15 17:10     ` Trahe, Fiona
2019-10-16  8:39     ` Akhil Goyal [this message]
2019-10-16 12:00   ` [dpdk-dev] [PATCH v3 0/1] doc: fix missing " Adam Dybkowski
2019-10-16 12:00     ` [dpdk-dev] [PATCH v3 1/1] " Adam Dybkowski
2019-10-16 12:57       ` Akhil Goyal

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=VE1PR04MB663978DCD10E99F84A7CA84BE6920@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=adamx.dybkowski@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).