From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Hemant Agrawal (OSS)" <hemant.agrawal@oss.nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/4] crypto/dpaax_sec: fix inline query for descriptors
Date: Tue, 7 Jul 2020 22:32:34 +0000 [thread overview]
Message-ID: <VI1PR04MB3168377E80EEB9537FE610ADE6660@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM6PR04MB44560FA1BD821FBDF091A07B89660@AM6PR04MB4456.eurprd04.prod.outlook.com>
> Series-
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Tuesday, July 7, 2020 12:05 AM
> To: dev@dpdk.org; Hemant Agrawal <hemant.agrawal@nxp.com>
> Cc: Akhil Goyal <akhil.goyal@nxp.com>
> Subject: [PATCH 1/4] crypto/dpaax_sec: fix inline query for descriptors
>
> The maximum length of job descriptor which is formed is 13 words and hence
> rta_inline_query should take care of the max descriptor(shared + job) lengths
> and thus find out of the key can be referenced or immediate.
>
> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
> ---
Added Fixes in commit logs.
Fixes: 05b12700cd4c ("crypto/dpaa_sec: support null algos for protocol offload")
Fixes: 13273250eec5 ("crypto/dpaa2_sec: support AES-GCM and CTR")
Cc: stable@dpdk.org
Applied to dpdk-next-crypto
next parent reply other threads:[~2020-07-07 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200706183500.29862-1-akhil.goyal@nxp.com>
[not found] ` <AM6PR04MB44560FA1BD821FBDF091A07B89660@AM6PR04MB4456.eurprd04.prod.outlook.com>
2020-07-07 22:32 ` Akhil Goyal [this message]
[not found] ` <20200706183500.29862-2-akhil.goyal@nxp.com>
2020-07-07 22:34 ` [dpdk-stable] [PATCH 2/4] crypto/dpaa2_sec: fix HFN override Akhil Goyal
[not found] ` <20200706183500.29862-3-akhil.goyal@nxp.com>
2020-07-07 22:35 ` [dpdk-stable] [PATCH 3/4] common/dpaax/caamflib: fix 12 bit NULL auth case 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=VI1PR04MB3168377E80EEB9537FE610ADE6660@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@oss.nxp.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).