From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>,
"Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
"shirik@nvidia.com" <shirik@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] test/crypto: fix typo in AES test
Date: Wed, 1 Feb 2023 14:08:35 +0000 [thread overview]
Message-ID: <CO6PR18MB44847DE3A140CD72EDE2288CD8D19@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB340834C3CC99583D3C2D579581D39@SN6PR11MB3408.namprd11.prod.outlook.com>
> Acked-by: Kai Ji <kai.ji@intel.com>
>
> >
> > Fix the spelling of scater to scatter in cryptodev AES test vector
> > header file
> >
> > Fixes: 2692b02e03b2 ("test/crypto: add multi-segment out-of-place AES-
> > XTS")
> > Cc: shirik@nvidia.com
> >
> > Signed-off-by: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> > ---
Cc: stable@dpdk.org
Applied to dpdk-next-crypto
Thanks.
parent reply other threads:[~2023-02-01 14:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SN6PR11MB340834C3CC99583D3C2D579581D39@SN6PR11MB3408.namprd11.prod.outlook.com>]
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=CO6PR18MB44847DE3A140CD72EDE2288CD8D19@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=kai.ji@intel.com \
--cc=shirik@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vikash.chandrax.poddar@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).