DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, <dev@dpdk.org>
Cc: <pablo.de.lara.guarch@intel.com>, <alok.makhariya@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/dpaa2_sec: support for scatter gather
Date: Fri, 19 Jan 2018 19:36:02 +0530	[thread overview]
Message-ID: <3e09cb10-2c2c-1cb2-8c74-4d92a9544647@nxp.com> (raw)
In-Reply-To: <20180119115102.2247-1-akhil.goyal@nxp.com>

On 1/19/2018 5:21 PM, Akhil Goyal wrote:
> Signed-off-by: Alok Makhariya <alok.makhariya@nxp.com>
> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
> ---
>  doc/guides/cryptodevs/features/default.ini   |   1 +
>  doc/guides/cryptodevs/features/dpaa2_sec.ini |   1 +
>  drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c  | 588 +++++++++++++++++++++++++--
>  test/test/test_cryptodev.c                   |  10 +
>  test/test/test_cryptodev_aes_test_vectors.h  |  22 +-
>  test/test/test_cryptodev_hash_test_vectors.h |  14 +
>  6 files changed, 596 insertions(+), 40 deletions(-)
>

Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

  parent reply	other threads:[~2018-01-19 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 11:51 Akhil Goyal
2018-01-19 11:51 ` [dpdk-dev] [PATCH 2/2] crypto/dpaa_sec: " Akhil Goyal
2018-01-19 14:08   ` Hemant Agrawal
2018-01-19 14:06 ` Hemant Agrawal [this message]
2018-01-19 20:45 ` [dpdk-dev] [PATCH 1/2] crypto/dpaa2_sec: " De Lara Guarch, Pablo
2018-01-22  8:46 ` [dpdk-dev] [PATCH v2 1/3] doc: update feature list for cryptodevs Akhil Goyal
2018-01-22  8:46   ` [dpdk-dev] [PATCH v2 2/3] crypto/dpaa2_sec: support for scatter gather Akhil Goyal
2018-01-22  8:46   ` [dpdk-dev] [PATCH v2 3/3] crypto/dpaa_sec: " Akhil Goyal
2018-01-22 11:55   ` [dpdk-dev] [PATCH v2 1/3] doc: update feature list for cryptodevs De Lara Guarch, Pablo
2018-01-22 12:22   ` De Lara Guarch, Pablo

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=3e09cb10-2c2c-1cb2-8c74-4d92a9544647@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alok.makhariya@nxp.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).