From: "Ji, Kai" <kai.ji@intel.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "gakhil@marvell.com" <gakhil@marvell.com>
Subject: Re: [PATCH v1 1/2] maintainers: update for crypto performance test
Date: Fri, 21 Mar 2025 10:30:56 +0000 [thread overview]
Message-ID: <DS0PR11MB7458FE1EF46B36E8F91FE6C781DB2@DS0PR11MB7458.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250320142113.1130872-1-brian.dooley@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Acked-by: Kai Ji <kai.ji@intel.com>
________________________________
From: Dooley, Brian <brian.dooley@intel.com>
Sent: 20 March 2025 14:21
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org <dev@dpdk.org>; gakhil@marvell.com <gakhil@marvell.com>; Ji, Kai <kai.ji@intel.com>; Dooley, Brian <brian.dooley@intel.com>
Subject: [PATCH v1 1/2] maintainers: update for crypto performance test
Replacing myself as Crypto Perf App maintainer with Kai Ji.
Signed-off-by: Brian Dooley <brian.dooley@intel.com>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 82f6e2f917..cdcea9aa72 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1936,7 +1936,7 @@ F: app/test-compress-perf/
F: doc/guides/tools/comp_perf.rst
Crypto performance test application
-M: Brian Dooley <brian.dooley@intel.com>
+M: Kai Ji <kai.ji@intel.com>
T: git://dpdk.org/next/dpdk-next-crypto
F: app/test-crypto-perf/
F: doc/guides/tools/cryptoperf.rst
--
2.25.1
[-- Attachment #2: Type: text/html, Size: 2072 bytes --]
prev parent reply other threads:[~2025-03-21 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 14:21 Brian Dooley
2025-03-20 14:21 ` [PATCH v1 2/2] maintainers: update for FIPS example app Brian Dooley
2025-03-21 10:43 ` Ji, Kai
2025-03-21 10:30 ` Ji, Kai [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=DS0PR11MB7458FE1EF46B36E8F91FE6C781DB2@DS0PR11MB7458.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=thomas@monjalon.net \
/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).