DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, Radu Nicolau <radu.nicolau@intel.com>
Cc: Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Vamsi Krishna Attunuru <vattunuru@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 4/9] crypto/octeontx2: add cryptodev sec registration
Date: Thu, 16 Jul 2020 05:04:51 +0000	[thread overview]
Message-ID: <MWHPR18MB1104DE9E87FD00BFCAE1CE0DA87F0@MWHPR18MB1104.namprd18.prod.outlook.com> (raw)
In-Reply-To: <AM5PR04MB315376ED02838E3203358103E67E0@AM5PR04MB3153.eurprd04.prod.outlook.com>

Hi Akhil,

Please see inline.

Thanks
Tejasree

> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Wednesday, July 15, 2020 10:28 PM
> To: Tejasree Kondoj <ktejasree@marvell.com>; Radu Nicolau
> <radu.nicolau@intel.com>
> Cc: Narayana Prasad Raju Athreya <pathreya@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; Vamsi Krishna Attunuru <vattunuru@marvell.com>;
> dev@dpdk.org
> Subject: [EXT] RE: [PATCH v2 4/9] crypto/octeontx2: add cryptodev sec
> registration
> 
> External Email
> 
> ----------------------------------------------------------------------
> >  			     RTE_CRYPTODEV_FF_OOP_SGL_IN_SGL_OUT |
> >  			     RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO |
> >  			     RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_QT |
> > -			     RTE_CRYPTODEV_FF_SYM_SESSIONLESS;
> > +			     RTE_CRYPTODEV_FF_SYM_SESSIONLESS |
> > +			     RTE_CRYPTODEV_FF_SECURITY;
> >
> Missed the corresponding change in
> doc/guides/cryptodevs/features/octeontx2.ini
[Tejasree] Will add it.


  reply	other threads:[~2020-07-16  5:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  9:26 [dpdk-dev] [PATCH v2 0/9] add OCTEON TX2 lookaside IPsec support Tejasree Kondoj
2020-07-15  9:26 ` [dpdk-dev] [PATCH v2 1/9] crypto/octeontx2: move capabilities initialization into probe Tejasree Kondoj
2020-07-15  9:26 ` [dpdk-dev] [PATCH v2 2/9] net/octeontx2: move otx2_sec_session struct to otx2_security.h Tejasree Kondoj
2020-07-15  9:26 ` [dpdk-dev] [PATCH v2 3/9] crypto/octeontx2: add lookaside SA context definitions Tejasree Kondoj
2020-07-15  9:26 ` [dpdk-dev] [PATCH v2 4/9] crypto/octeontx2: add cryptodev sec registration Tejasree Kondoj
2020-07-15 16:57   ` Akhil Goyal
2020-07-16  5:04     ` Tejasree Kondoj [this message]
2020-07-15  9:26 ` [dpdk-dev] [PATCH v2 5/9] crypto/octeontx2: add cryptodev sec capabilities Tejasree Kondoj
2020-07-15  9:27 ` [dpdk-dev] [PATCH v2 6/9] crypto/octeontx2: add cryptodev sec misc callbacks Tejasree Kondoj
2020-07-15  9:27 ` [dpdk-dev] [PATCH v2 7/9] crypto/octeontx2: add cryptodev sec session create Tejasree Kondoj
2020-07-15  9:27 ` [dpdk-dev] [PATCH v2 8/9] crypto/octeontx2: add cryptodev sec enqueue routine Tejasree Kondoj
2020-07-15  9:27 ` [dpdk-dev] [PATCH v2 9/9] crypto/octeontx2: add cryptodev sec dequeue routine Tejasree Kondoj
2020-07-15 17:10   ` Akhil Goyal
2020-07-16  5:05     ` Tejasree Kondoj

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=MWHPR18MB1104DE9E87FD00BFCAE1CE0DA87F0@MWHPR18MB1104.namprd18.prod.outlook.com \
    --to=ktejasree@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=pathreya@marvell.com \
    --cc=radu.nicolau@intel.com \
    --cc=vattunuru@marvell.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).