From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: add chacha20-poly1305 aead algorithm
Date: Tue, 14 Jan 2020 12:52:04 +0000 [thread overview]
Message-ID: <BN6PR11MB1796C80B7161C51CD84871DBE4340@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN6PR11MB1796A37D604445087B560C1EE4340@BN6PR11MB1796.namprd11.prod.outlook.com>
Hi Arek,
Sorry, my bad.
That comment was not for this patch - it was intended for the QAT patch.
This patch has no checkpatch warnings.
> -----Original Message-----
> From: Trahe, Fiona
> Sent: Tuesday, January 14, 2020 12:50 PM
> To: Kusztal, ArkadiuszX <ArkadiuszX.Kusztal@intel.com>; dev@dpdk.org
> Cc: akhil.goyal@nxp.com
> Subject: RE: [PATCH v3] cryptodev: add chacha20-poly1305 aead algorithm
>
> Hi Arek,
>
> There's a bunch of checkpatch warnings about line length that can be easily fixed.
> Can you send a v4 please.
>
> Fiona
>
> > -----Original Message-----
> > From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> > Sent: Monday, January 13, 2020 10:44 AM
> > To: dev@dpdk.org
> > Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; Kusztal, ArkadiuszX
> > <arkadiuszx.kusztal@intel.com>
> > Subject: [PATCH v3] cryptodev: add chacha20-poly1305 aead algorithm
> >
> > This patch adds Chacha20-Poly1305 AEAD algorithm to Cryptodev.
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2020-01-14 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 10:43 Arek Kusztal
2020-01-14 12:49 ` Trahe, Fiona
2020-01-14 12:52 ` Trahe, Fiona [this message]
2020-01-14 13:18 ` Anoob Joseph
2020-01-15 15:53 ` Akhil Goyal
2020-02-05 14:28 ` Thomas Monjalon
2020-02-05 14:41 ` Trahe, Fiona
2020-02-05 15:21 ` Thomas Monjalon
2020-04-17 15:43 Arek Kusztal
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=BN6PR11MB1796C80B7161C51CD84871DBE4340@BN6PR11MB1796.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@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).