DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Declan Doherty <declan.doherty@intel.com>,
	Fan Zhang <roy.fan.zhang@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	dev@dpdk.org, Anoob Joseph <anoobj@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Archana Muniganti <marchana@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce crypto op struct changes
Date: Wed, 04 Aug 2021 18:31:03 +0200	[thread overview]
Message-ID: <9305674.WGLNCzWakc@thomas> (raw)
In-Reply-To: <CO6PR18MB4484A268F484AB61C3675786D8EF9@CO6PR18MB4484.namprd18.prod.outlook.com>

02/08/2021 14:36, Akhil Goyal:
> > One reserved byte in rte_crypto_op struct would be used to indicate
> > warnings and other information from the crypto/security operation. This
> > field will be used to communicate events such as soft expiry with IPsec
> > in lookaside mode.
> > 
> > Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> > ---
> Acked-by: Akhil Goyal <gakhil@marvell.com>

Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Applied, thanks.



  reply	other threads:[~2021-08-04 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 11:11 Anoob Joseph
2021-08-02 12:36 ` Akhil Goyal
2021-08-04 16:31   ` Thomas Monjalon [this message]
2021-08-02 21:18 ` Ananyev, Konstantin
2021-08-03  6:52   ` Hemant Agrawal

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=9305674.WGLNCzWakc@thomas \
    --to=thomas@monjalon.net \
    --cc=anoobj@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=ktejasree@marvell.com \
    --cc=marchana@marvell.com \
    --cc=roy.fan.zhang@intel.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).