DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Wathsala Vithanage <wathsala.vithanage@arm.com>,
	Kai Ji <kai.ji@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: "ciara.power@intel.com" <ciara.power@intel.com>,
	"probb@iol.unh.edu" <probb@iol.unh.edu>,
	"dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>,
	Ruifeng Wang <ruifeng.wang@arm.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Jack Bond-Preston <Jack.Bond-Preston@arm.com>
Subject: RE: [EXTERNAL] [PATCH] crypto/ipsec_mb: update Arm IPsec-MB library tag
Date: Fri, 1 Mar 2024 08:15:28 +0000	[thread overview]
Message-ID: <CO6PR18MB44848D22B3DBFB6D7A377313D85E2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240228175250.340922-1-wathsala.vithanage@arm.com>

> Updates the tag of Arm IPsec-MB library to SECLIB-IPSEC-2023.10.13
> in snow3g and zuc documentation. Tag SECLIB-IPSEC-2023.10.13 updates
> IPSec-MB library version to 1.4.
> 
> Signed-off-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Jack Bond-Preston <Jack.Bond-Preston@arm.com>
> ---
I believe this patch would need a rework due to the issue found in 
https://patches.dpdk.org/project/dpdk/patch/20240228113301.934291-1-brian.dooley@intel.com/

  reply	other threads:[~2024-03-01  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 17:52 Wathsala Vithanage
2024-03-01  8:15 ` Akhil Goyal [this message]
2024-03-05 16:06   ` [EXTERNAL] " Akhil Goyal
2024-03-05 17:44     ` Wathsala Wathawana Vithanage
2024-03-06 14:49 ` [PATCH V2] doc/ipsec_mb: " Wathsala Vithanage
2024-03-12 17:33 ` [PATCH v3] " Jack Bond-Preston
2024-03-14 18:50   ` [EXTERNAL] " Akhil Goyal
2024-03-14 19:54     ` Patrick Robb
2024-03-14 20:04       ` Akhil Goyal
2024-03-15 18:17         ` Patrick Robb
2024-03-22 19:38           ` 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=CO6PR18MB44848D22B3DBFB6D7A377313D85E2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=Jack.Bond-Preston@arm.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=kai.ji@intel.com \
    --cc=nd@arm.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=probb@iol.unh.edu \
    --cc=ruifeng.wang@arm.com \
    --cc=wathsala.vithanage@arm.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).