From: Patrick Robb <probb@iol.unh.edu>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Jack Bond-Preston <jack.bond-preston@foss.arm.com>,
Thomas Monjalon <thomas@monjalon.net>, Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: Re: [EXTERNAL] [PATCH v3] doc/ipsec_mb: update Arm IPsec-MB library tag
Date: Thu, 14 Mar 2024 15:54:59 -0400 [thread overview]
Message-ID: <CAJvnSUD5jnRft5gAUnxkPejbKTFfCr4eYopqZTkRhC_OGG8oQw@mail.gmail.com> (raw)
In-Reply-To: <CO6PR18MB4484639112FAFE8F65E329FFD8292@CO6PR18MB4484.namprd18.prod.outlook.com>
We are rebuilding from this tag right now. I know the IPSEC update is
now postponed until after 24.03, but once this install is done, do you
want me to issue retests for all the recent patches which had failed
for ARM on this library previously? Then I guess it will be verified
as you say.
On Thu, Mar 14, 2024 at 2:50 PM Akhil Goyal <gakhil@marvell.com> wrote:
>
> > Subject: [EXTERNAL] [PATCH v3] doc/ipsec_mb: update Arm IPsec-MB library tag
> >
> > Updates the tag of Arm IPsec-MB library to SECLIB-IPSEC-2024.03.12
> > in snow3g and zuc documentation.
> >
> > Signed-off-by: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
> > Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> Is this tag verified in CI?
next prev parent reply other threads:[~2024-03-14 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 17:52 [PATCH] crypto/ipsec_mb: " Wathsala Vithanage
2024-03-01 8:15 ` [EXTERNAL] " Akhil Goyal
2024-03-05 16:06 ` 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 [this message]
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=CAJvnSUD5jnRft5gAUnxkPejbKTFfCr4eYopqZTkRhC_OGG8oQw@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jack.bond-preston@foss.arm.com \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas@monjalon.net \
--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).