DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ankur Dwivedi <adwivedi@marvell.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/octeontx2: fix sessionless code
Date: Wed, 23 Sep 2020 05:07:03 +0000	[thread overview]
Message-ID: <DM5PR1801MB1884C97563BD98FD72B334C8DD380@DM5PR1801MB1884.namprd18.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB3168AE1B8D6815B2265793F6E63B0@VI1PR04MB3168.eurprd04.prod.outlook.com>



>-----Original Message-----
>From: Akhil Goyal <akhil.goyal@nxp.com>
>Sent: Wednesday, September 23, 2020 1:19 AM
>To: Ankur Dwivedi <adwivedi@marvell.com>; dev@dpdk.org
>Cc: Anoob Joseph <anoobj@marvell.com>; Tejasree Kondoj
><ktejasree@marvell.com>
>Subject: [EXT] RE: [PATCH v2] crypto/octeontx2: fix sessionless code
>
>External Email
>
>----------------------------------------------------------------------
>> A temporary session is created for sessionless crypto operations.
>> rte_cryptodev_sym_session_create() should be used for creating the
>> temporary session as it initializes the session structure in the
>> correct way. Also the session should be set to 0 before freeing it.
>>
>> Fixes: 17ac2a72191b ("crypto/octeontx2: add enqueue/dequeue ops")
>>
>> Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com>
>> ---
>> v2:
>> * Use local variable to hold session size
>
>Please supersede your previous versions from the patchworks. It creates
>unnecessary confusion.
Sorry for the confusion. I will supersede previous versions.
>
>Applied to dpdk-next-crypto
>
>Thanks.


      reply	other threads:[~2020-09-23  5:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  9:19 [dpdk-dev] [PATCH] " Ankur Dwivedi
2020-09-08 11:00 ` Anoob Joseph
2020-09-18 13:45 ` [dpdk-dev] [PATCH v2] " Ankur Dwivedi
2020-09-22 19:49   ` Akhil Goyal
2020-09-23  5:07     ` Ankur Dwivedi [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=DM5PR1801MB1884C97563BD98FD72B334C8DD380@DM5PR1801MB1884.namprd18.prod.outlook.com \
    --to=adwivedi@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ktejasree@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).