From: Shally Verma <shallyv@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "sunila.sahu@caviumnetworks.com" <sunila.sahu@caviumnetworks.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"ashish.gupta@caviumnetworks.com"
<ashish.gupta@caviumnetworks.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] openssl: fix bad reference of modinv
Date: Wed, 6 Feb 2019 05:11:32 +0000 [thread overview]
Message-ID: <BN6PR1801MB2052A028F9A3E65E03F73BDDAD6F0@BN6PR1801MB2052.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190205091319.11776-1-arkadiuszx.kusztal@intel.com>
>-----Original Message-----
>From: dev <dev-bounces@dpdk.org> On Behalf Of Arek Kusztal
>Sent: 05 February 2019 14:43
>To: dev@dpdk.org
>Cc: sunila.sahu@caviumnetworks.com; akhil.goyal@nxp.com; shally.verma@caviumnetworks.com;
>ashish.gupta@caviumnetworks.com; Arek Kusztal <arkadiuszx.kusztal@intel.com>
>Subject: [EXT] [dpdk-dev] [PATCH] openssl: fix bad reference of modinv
>
>External Email
>
>----------------------------------------------------------------------
>Fixes bad reference of modinv struct in openssl pmd
>
>Fixes: 3e9d6bd447fb ("crypto/openssl: add RSA and mod asym operations")
>
>Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>---
> drivers/crypto/openssl/rte_openssl_pmd.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Acked-by: Shally Verma <shally.verma@marvell.com>
Thanks
Shally
prev parent reply other threads:[~2019-02-06 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 9:13 [dpdk-dev] " Arek Kusztal
2019-02-05 16:54 ` Trahe, Fiona
2019-03-06 16:41 ` Akhil Goyal
2019-02-06 5:11 ` Shally Verma [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=BN6PR1801MB2052A028F9A3E65E03F73BDDAD6F0@BN6PR1801MB2052.namprd18.prod.outlook.com \
--to=shallyv@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ashish.gupta@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=sunila.sahu@caviumnetworks.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).