From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] crypto/qat: support DOCSIS AES-256
Date: Wed, 26 Feb 2020 10:41:42 +0000 [thread overview]
Message-ID: <BN6PR11MB179634F46A3DD072F3B47AA7E4EA0@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1582707851-32026-1-git-send-email-mairtin.oloingsigh@intel.com>
> -----Original Message-----
> From: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Sent: Wednesday, February 26, 2020 9:04 AM
> To: Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com
> Cc: dev@dpdk.org; O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Subject: [PATCH v2 1/2] crypto/qat: support DOCSIS AES-256
>
> This patch adds support for DOCSIS AES-256 when using qat
>
> Signed-off-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2020-02-26 10:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 9:04 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
2020-02-26 10:41 ` Trahe, Fiona [this message]
2020-03-25 19:10 ` [dpdk-dev] [PATCH v2 1/2] crypto/qat: support DOCSIS AES-256 Akhil Goyal
2020-05-11 10:19 ` [dpdk-dev] [PATCH v3] " Mairtin o Loingsigh
2020-05-11 10:19 ` [dpdk-dev] [PATCH v3] test/crypto: add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-05-11 13:10 ` Akhil Goyal
2020-05-11 10:19 ` [dpdk-dev] [PATCH v3] doc: QAT support for AES-256 DOCSIS Mairtin o Loingsigh
2020-05-11 13:12 ` Akhil Goyal
2020-05-11 13:14 ` [dpdk-dev] [PATCH v3] crypto/qat: support DOCSIS AES-256 Akhil Goyal
2020-05-11 14:03 ` O'loingsigh, Mairtin
2020-05-11 16:14 ` 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=BN6PR11MB179634F46A3DD072F3B47AA7E4EA0@BN6PR11MB1796.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.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).