DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shally Verma <shallyv@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
	"shally.verma@caviumnetworks.com"
	<shally.verma@caviumnetworks.com>,
	"sunila.sahu@caviumnetworks.com" <sunila.sahu@caviumnetworks.com>,
	"ashish.gupta@caviumnetworks.com"
	<ashish.gupta@caviumnetworks.com>,
	"umesh.kartha@caviumnetworks.com"
	<umesh.kartha@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: rework mod exp and mod inv comments
Date: Wed, 6 Feb 2019 10:50:59 +0000	[thread overview]
Message-ID: <BN6PR1801MB2052D5F856CEC6E59EA64331AD6F0@BN6PR1801MB2052.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190206103426.1568-1-arkadiuszx.kusztal@intel.com>



>-----Original Message-----
>From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>Sent: 06 February 2019 16:04
>To: dev@dpdk.org
>Cc: akhil.goyal@nxp.com; fiona.trahe@intel.com; shally.verma@caviumnetworks.com; sunila.sahu@caviumnetworks.com;
>ashish.gupta@caviumnetworks.com; umesh.kartha@caviumnetworks.com; Arek Kusztal <arkadiuszx.kusztal@intel.com>
>Subject: [PATCH v3] cryptodev: rework mod exp and mod inv comments
>
>External Email
>
>This patch changes modular exponentiation and modular multiplicative
>inverse API comments to make it more precise.
>
>Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>---
>v2:
>- grammar fixes
>
>v3:
>- remove information about positive integer
>
> lib/librte_cryptodev/rte_crypto_asym.h | 43 ++++++++++++++++++++++------------
> 1 file changed, 28 insertions(+), 15 deletions(-)
>
Acked-by: Shally Verma <shally.verma@marvell.com>

Thanks
Shally

  parent reply	other threads:[~2019-02-06 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 10:34 Arek Kusztal
2019-02-06 10:43 ` Trahe, Fiona
2019-02-06 10:50 ` Shally Verma [this message]
2019-03-06 16:34 ` Akhil Goyal

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=BN6PR1801MB2052D5F856CEC6E59EA64331AD6F0@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=fiona.trahe@intel.com \
    --cc=shally.verma@caviumnetworks.com \
    --cc=sunila.sahu@caviumnetworks.com \
    --cc=umesh.kartha@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).