From: Akhil Goyal <gakhil@marvell.com>
To: Jack Bond-Preston <jack.bond-preston@foss.arm.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] Re: [PATCH] doc: update Arm IPsec-MB dependency version
Date: Tue, 17 Sep 2024 18:51:48 +0000 [thread overview]
Message-ID: <CO6PR18MB44843FCA9E56801262B776DFD8612@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <325edeff-c5dc-4831-91de-6318fe1f2a8c@foss.arm.com>
> On 31/07/2024 22:26, Wathsala Vithanage wrote:
> > Updates the tag of Arm IPsec-MB library to SECLIB-IPSEC-2024.07.08
> > in snow3g and zuc documentation.
> >
> > Signed-off-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> > Reviewed-by: Dhruv Tripathi <dhruv.tripathi@arm.com>
> Acked-by: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2024-09-17 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 21:26 Wathsala Vithanage
2024-08-01 9:31 ` Jack Bond-Preston
2024-09-17 18:51 ` Akhil Goyal [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=CO6PR18MB44843FCA9E56801262B776DFD8612@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=jack.bond-preston@foss.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).