From: David Marchand <david.marchand@redhat.com>
To: Fan Zhang <roy.fan.zhang@intel.com>
Cc: dev <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>,
ssarananaga@marvell.com, Anoob Joseph <anoobj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] examples/fips_validation: fix typo
Date: Fri, 14 Feb 2020 14:13:23 +0100 [thread overview]
Message-ID: <CAJFAV8x-5bGV0Jtr=yA5B5jPNuek-SAVAVL1-Li5y1LwqmXG9g@mail.gmail.com> (raw)
In-Reply-To: <20200214114118.87662-1-roy.fan.zhang@intel.com>
On Fri, Feb 14, 2020 at 12:41 PM Fan Zhang <roy.fan.zhang@intel.com> wrote:
>
> This patch fixes the cipher len keyword typo.
>
> Fixes: 07f5e4553293 ("examples/fips_validation: fix cipher length for AES-GCM")
>
Suggested-by: Akhil Goyal <akhil.goyal@nxp.com>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-02-14 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 11:41 Fan Zhang
2020-02-14 13:13 ` David Marchand [this message]
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='CAJFAV8x-5bGV0Jtr=yA5B5jPNuek-SAVAVL1-Li5y1LwqmXG9g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.com \
--cc=ssarananaga@marvell.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).