From: Matteo Croce <technoboy85@gmail.com>
To: Joe Perches <joe@perches.com>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] get_maintainer: add KUnit maintainers for KUnit test files
Date: Sun, 1 Mar 2026 02:11:31 +0100 [thread overview]
Message-ID: <20260301011131.4057-1-teknoraver@meta.com> (raw)
KUnit test files are scattered across the tree and don't always match
the F: patterns in the KERNEL UNIT TESTING FRAMEWORK MAINTAINERS entry.
Add the KUnit maintainers automatically when the file path matches
common KUnit naming conventions: _kunit.c, -kunit.c, _kunit_test.c,
and -kunit-tests.c.
Signed-off-by: Matteo Croce <teknoraver@meta.com>
---
v2: added missing SOB
scripts/get_maintainer.pl | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 4414194bedcf..c07723af4132 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -966,6 +966,20 @@ sub get_maintainers {
}
}
+ ## Add KUnit maintainers for KUnit test files
+ if ($file =~ m/[_-]kunit[_-]?.*\.c$/) {
+ my $kunit_tvi = find_first_section();
+ while ($kunit_tvi < @typevalue) {
+ my $kunit_start = find_starting_index($kunit_tvi);
+ if ($typevalue[$kunit_start] =~ m/^KERNEL UNIT TESTING FRAMEWORK/) {
+ $hash{$kunit_tvi} = 0;
+ add_categories($kunit_tvi, "");
+ last;
+ }
+ $kunit_tvi = find_ending_index($kunit_tvi) + 1;
+ }
+ }
+
maintainers_in_file($file);
}
--
2.53.0
next reply other threads:[~2026-03-01 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 1:11 Matteo Croce [this message]
2026-03-01 2:36 ` Joe Perches
2026-03-01 11:17 ` Matteo Croce
2026-03-01 11:34 ` Thomas Weißschuh
2026-03-01 16:42 ` Joe Perches
2026-03-02 0:50 ` Matteo Croce
2026-03-02 2:05 ` Joe Perches
2026-03-02 2:34 ` Matteo Croce
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=20260301011131.4057-1-teknoraver@meta.com \
--to=technoboy85@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
/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
all inboxes | Powered by JetHome®