From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [PATCH] maintainers: fix app/test attributions
Date: Wed, 29 Apr 2026 09:29:13 -0700 [thread overview]
Message-ID: <20260429162913.272259-1-stephen@networkplumber.org> (raw)
Two app/test entries were attributed to the wrong section:
* test_event_ring.c exercises rte_event_ring
not the standalone app/test-eventdev/ binary.
Move it from "Eventdev test application" to "Eventdev API"
alongside test_eventdev.c, matching how test_event_eth_*_adapter.c and
test_event_*_adapter.c are grouped with their corresponding
lib/eventdev/*adapter* sub-libraries.
* The "test_*hash*" glob in the Hashes section unintentionally matched
three crypto hash test vector headers which belong only
to the Crypto API section. Replace with the two narrower globs
"test_hash*" and "test_thash*" which together cover every legitimate
hash test source (test_hash*.c and test_thash*.c) without leaking into
cryptodev.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
MAINTAINERS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0f5539f851..928e695abb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -540,6 +540,7 @@ F: lib/eventdev/
F: doc/guides/prog_guide/eventdev/eventdev.rst
F: drivers/event/skeleton/
F: app/test/test_eventdev.c
+F: app/test/test_event_ring.c
F: examples/l3fwd/l3fwd_event*
Eventdev Ethdev Rx Adapter API
@@ -1754,7 +1755,8 @@ M: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
F: lib/hash/
F: doc/guides/prog_guide/hash_lib.rst
F: doc/guides/prog_guide/toeplitz_hash_lib.rst
-F: app/test/test_*hash*
+F: app/test/test_hash*
+F: app/test/test_thash*
F: app/test/test_func_reentrancy.c
LPM
@@ -1985,7 +1987,6 @@ T: git://dpdk.org/next/dpdk-next-eventdev
F: app/test-eventdev/
F: doc/guides/tools/testeventdev.rst
F: doc/guides/tools/img/eventdev_*
-F: app/test/test_event_ring.c
Graph application
M: Sunil Kumar Kori <skori@marvell.com>
--
2.53.0
reply other threads:[~2026-04-29 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260429162913.272259-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--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