DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "sunila.sahu@caviumnetworks.com" <sunila.sahu@caviumnetworks.com>,
	"shally.verma@caviumnetworks.com"
	<shally.verma@caviumnetworks.com>,
	"ashish.gupta@caviumnetworks.com"
	<ashish.gupta@caviumnetworks.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] openssl: fix bad reference of modinv
Date: Wed, 6 Mar 2019 16:41:07 +0000	[thread overview]
Message-ID: <75c2d5cf-3ef6-8d9d-589c-f2cc89823758@nxp.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435896DA7EF@IRSMSX101.ger.corp.intel.com>



On 2/5/2019 10:24 PM, Trahe, Fiona wrote:
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Arek Kusztal
>> Sent: Tuesday, February 5, 2019 9:13 AM
>> To: dev@dpdk.org
>> Cc: sunila.sahu@caviumnetworks.com; akhil.goyal@nxp.com; shally.verma@caviumnetworks.com;
>> ashish.gupta@caviumnetworks.com; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
>> Subject: [dpdk-dev] [PATCH] openssl: fix bad reference of modinv
>>
>> 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>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
> Also cc'ed stable@dpdk.org
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto

Thanks.

  reply	other threads:[~2019-03-06 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05  9:13 Arek Kusztal
2019-02-05 16:54 ` Trahe, Fiona
2019-03-06 16:41   ` Akhil Goyal [this message]
2019-02-06  5:11 ` [dpdk-dev] [EXT] " Shally Verma

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=75c2d5cf-3ef6-8d9d-589c-f2cc89823758@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ashish.gupta@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=shally.verma@caviumnetworks.com \
    --cc=stable@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).