From: Anoob Joseph <anoobj@marvell.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 1/1] cryptodev: fix SHA-1 digest enum comment
Date: Thu, 21 May 2020 12:02:20 +0000 [thread overview]
Message-ID: <MN2PR18MB2877025C4F8E66BDFC078C7FDFB70@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB2880ADBCA3692206477D8A8AE4B70@SN6PR11MB2880.namprd11.prod.outlook.com>
> > -----Original Message-----
> > From: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> > Sent: Thursday, May 21, 2020 12:38 PM
> > To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>;
> > akhil.goyal@nxp.com
> > Cc: Dybkowski, AdamX <adamx.dybkowski@intel.com>; stable@dpdk.org
> > Subject: [PATCH v3 1/1] cryptodev: fix SHA-1 digest enum comment
> >
> > This patch fixes improper SHA-1 digest size in the enum comment and
> > also adds the note about HMAC-SHA-1-96.
> >
> > Fixes: 1bd407fac80b ("cryptodev: extract symmetric operations")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2020-05-21 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 11:38 [dpdk-dev] [PATCH v3 0/1] " Adam Dybkowski
2020-05-21 11:38 ` [dpdk-dev] [PATCH v3 1/1] " Adam Dybkowski
2020-05-21 11:44 ` Trahe, Fiona
2020-05-21 12:02 ` Anoob Joseph [this message]
2020-05-21 12:46 ` Akhil Goyal
2020-05-21 14:48 ` [dpdk-dev] [PATCH v4 0/1] " Adam Dybkowski
2020-05-21 14:48 ` [dpdk-dev] [PATCH v4 1/1] " Adam Dybkowski
2020-05-21 15:32 ` Akhil Goyal
2020-05-24 9:54 ` Thomas Monjalon
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=MN2PR18MB2877025C4F8E66BDFC078C7FDFB70@MN2PR18MB2877.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.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).