From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] test/crypto: Add AES-256 DOCSIS test vectors
Date: Mon, 6 Apr 2020 18:23:01 +0000 [thread overview]
Message-ID: <SN6PR11MB31011F82336C54BEC0A699D284C20@SN6PR11MB3101.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1586187346-19020-2-git-send-email-mairtin.oloingsigh@intel.com>
> -----Original Message-----
> From: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Sent: Monday, April 6, 2020 4:36 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Subject: [PATCH v2 2/2] test/crypto: Add AES-256 DOCSIS test vectors
>
> This patch adds test vectors for AES-256 and sets AESNI-MB as the target PMD
>
> Signed-off-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
Acked-by: Pablo de Lara <Pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2020-04-06 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 15:35 [dpdk-dev] [PATCH v2 1/2] crypto/aesni_mb: support DOCSIS AES-256 Mairtin o Loingsigh
2020-04-06 15:35 ` [dpdk-dev] [PATCH v2 2/2] test/crypto: Add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-04-06 18:23 ` De Lara Guarch, Pablo [this message]
2020-04-06 17:47 ` [dpdk-dev] [PATCH v2 1/2] crypto/aesni_mb: support DOCSIS AES-256 De Lara Guarch, Pablo
-- strict thread matches above, loose matches on Subject: below --
2020-02-26 9:04 [dpdk-dev] [PATCH v2 1/2] crypto/qat: " Mairtin o Loingsigh
2020-02-26 9:04 ` [dpdk-dev] [PATCH v2 2/2] test/crypto: Add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-02-26 10:42 ` Trahe, Fiona
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=SN6PR11MB31011F82336C54BEC0A699D284C20@SN6PR11MB3101.namprd11.prod.outlook.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=mairtin.oloingsigh@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).