From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: RE: [PATCH v2 1/3] crypto/ipsec_mb: improve CPU code path
Date: Tue, 7 Oct 2025 11:13:23 +0000 [thread overview]
Message-ID: <CO6PR18MB4484FB7C3691A4998082AE3AD8E0A@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <DS0PR11MB74589FB5F44DE9D4A0349BBC81E6A@DS0PR11MB7458.namprd11.prod.outlook.com>
> Series-acked-by: Kai Ji <kai.ji@intel.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2025-10-07 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 13:14 Radu Nicolau
2025-09-11 13:14 ` [PATCH v2 2/3] test/crypto: improve CPU mode coverage Radu Nicolau
2025-09-11 13:14 ` [PATCH v2 3/3] test/crypto: fix uninitialised vector fields Radu Nicolau
2025-10-01 11:01 ` [PATCH v2 1/3] crypto/ipsec_mb: improve CPU code path Ji, Kai
2025-10-07 11:13 ` 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=CO6PR18MB4484FB7C3691A4998082AE3AD8E0A@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@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).