From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/aesni_mb: fix cpu crypto cipher auth
Date: Mon, 2 Nov 2020 19:56:44 +0000 [thread overview]
Message-ID: <VI1PR04MB3168D2A08BB74F8B892DCBCBE6100@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201029162604.1034183-1-roy.fan.zhang@intel.com>
Hi Fan,
> Subject: [PATCH] crypto/aesni_mb: fix cpu crypto cipher auth
>
> This patch fixes the AESNI-MB PMD CPU crypto process function. Orignally
> the function tried to access crypto vector's aad buffer even it is not
> needed.
>
> Fixes: 8d928d47a29a ("cryptodev: change crypto symmetric vector structure")
> Cc: roy.fan.zhang@intel.com
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
This patch need a rebase as it is conflicting with the recently added patch
From pablo.
Regards,
Akhil
next prev parent reply other threads:[~2020-11-02 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:26 Fan Zhang
2020-10-29 16:30 ` [dpdk-dev] [dpdk-dev v2] " Fan Zhang
2020-11-02 19:56 ` Akhil Goyal [this message]
2020-11-03 11:31 ` [dpdk-dev] [PATCH] " Zhang, Roy Fan
2020-11-03 12:24 ` Zhang, Roy Fan
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=VI1PR04MB3168D2A08BB74F8B892DCBCBE6100@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).