DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Fiona Trahe <fiona.trahe@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "ashish.gupta@marvell.com" <ashish.gupta@marvell.com>,
	"arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc/crypto: fix missing asymmetric algo table
Date: Tue, 16 Apr 2019 13:53:10 +0000	[thread overview]
Message-ID: <VI1PR04MB48933AB692AF331708F70E78E6240@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190416135310.cp3SdgiNlg9n53h47qRqvupeLQ1xEQ0BKW3wNd_6ww8@z> (raw)
In-Reply-To: <6e5c8c23-d425-dc6c-b51f-179525f4d430@nxp.com>

> Hi Fiona,
> 
> On 4/3/2019 4:08 PM, Fiona Trahe wrote:
> > Fixes: 11e5ba72cf67 ("doc: add crypto asymmetric feature list")
> > cc: stable@dpdk.org
> >
> > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> > ---
> >   .gitignore                                   | 1 +
> >   doc/guides/conf.py                           | 5 +++++
> >   doc/guides/cryptodevs/features/aesni_gcm.ini | 5 +++++
> >   doc/guides/cryptodevs/features/aesni_mb.ini  | 5 +++++
> >   doc/guides/cryptodevs/features/armv8.ini     | 5 +++++
> >   doc/guides/cryptodevs/features/caam_jr.ini   | 5 +++++
> >   doc/guides/cryptodevs/features/ccp.ini       | 5 +++++
> >   doc/guides/cryptodevs/features/default.ini   | 9 +++++++++
> >   doc/guides/cryptodevs/features/dpaa2_sec.ini | 5 +++++
> >   doc/guides/cryptodevs/features/dpaa_sec.ini  | 5 +++++
> >   doc/guides/cryptodevs/features/kasumi.ini    | 5 +++++
> >   doc/guides/cryptodevs/features/mvsam.ini     | 5 +++++
> >   doc/guides/cryptodevs/features/null.ini      | 5 +++++
> >   doc/guides/cryptodevs/features/octeontx.ini  | 5 +++++
> >   doc/guides/cryptodevs/features/qat.ini       | 5 +++++
> I believe qat need to be updated with the supported asym features.
> >   doc/guides/cryptodevs/features/snow3g.ini    | 5 +++++
> >   doc/guides/cryptodevs/features/virtio.ini    | 5 +++++
> >   doc/guides/cryptodevs/features/zuc.ini       | 5 +++++
> >   doc/guides/cryptodevs/openssl.rst            | 8 ++++++++
> >   doc/guides/cryptodevs/overview.rst           | 7 +++++++
> >   20 files changed, 105 insertions(+)
> >
> >
> rest of the patch looks good.
> 
> -Akhil

Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

  parent reply	other threads:[~2019-04-16 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 10:38 Fiona Trahe
2019-04-03 10:38 ` Fiona Trahe
2019-04-03 11:00 ` Akhil Goyal
2019-04-03 11:00   ` Akhil Goyal
2019-04-03 11:11   ` Trahe, Fiona
2019-04-03 11:11     ` Trahe, Fiona
2019-04-03 11:58     ` Akhil Goyal
2019-04-03 11:58       ` Akhil Goyal
2019-04-16 13:53   ` Akhil Goyal [this message]
2019-04-16 13:53     ` Akhil Goyal
2019-04-16 14:57     ` Akhil Goyal
2019-04-16 14: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=VI1PR04MB48933AB692AF331708F70E78E6240@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ashish.gupta@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=stable@dpdk.org \
    /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).