dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/5] doc/guides/cryptodevs: cleanup for armv8 and	openssl PMDs
Date: Wed, 19 Jun 2019 14:53:53 +0000	[thread overview]
Message-ID: <VE1PR04MB6639A4A668AE7CC798C1BA0FE6E50@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <eedf1632bb8ac8d15524bf42aed23095566a055e.1558517518.git.thierry.herbelot@6wind.com>

> The perf tests were removed in a previous commit.
> 
> Fixes: 2ac67c32837a ('test/crypto: remove crypto perf tests')
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> ---
>  doc/guides/cryptodevs/armv8.rst   | 1 -
>  doc/guides/cryptodevs/openssl.rst | 1 -
>  2 files changed, 2 deletions(-)
> 
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Please add fixes line for every fix that you do. It was missing in a couple of your patches.

Cc: stable@dpdk.org
Patchset applied to dpdk-next-crypto

Thanks.

      parent reply	other threads:[~2019-06-19 14:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  9:44 [dpdk-dev] [PATCH 1/5] doc/guides/cryptodevs: cleanup for armv8 and openssl PMDs Thierry Herbelot
2019-05-22  9:44 ` [dpdk-dev] [PATCH 2/5] crypto/mvsam: fix typo Thierry Herbelot
2019-05-27 13:53   ` Tomasz Duszynski
2019-05-22  9:44 ` [dpdk-dev] [PATCH 3/5] doc/prog_guides: fix triplicated typo Thierry Herbelot
2019-05-22 11:25   ` Trahe, Fiona
2019-05-22  9:44 ` [dpdk-dev] [PATCH 4/5] doc/guides: fix grammar Thierry Herbelot
2019-05-22  9:58   ` Rami Rosen
2019-05-22 11:24   ` Trahe, Fiona
2019-05-22  9:44 ` [dpdk-dev] [PATCH 5/5] drivers/{bus,crypto}: fix typo Thierry Herbelot
2019-06-18 12:56 ` [dpdk-dev] [PATCH 1/5] doc/guides/cryptodevs: cleanup for armv8 and openssl PMDs Akhil Goyal
2019-06-19 14:53 ` Akhil Goyal [this message]

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=VE1PR04MB6639A4A668AE7CC798C1BA0FE6E50@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thierry.herbelot@6wind.com \
    --cc=thomas@monjalon.net \
    /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).