mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: joe@perches.com
Cc: linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: [PATCH] get_maintainer: add --json output mode
Date: Mon,  6 Apr 2026 13:01:38 -0400	[thread overview]
Message-ID: <20260406170138.4034983-1-sashal@kernel.org> (raw)

Add a --json flag to get_maintainer.pl that emits structured JSON
output, making results machine-parseable for CI systems, IDE
integrations, and AI-assisted development tools.

The JSON output includes a maintainers array with structured name,
email, and role fields, plus optional arrays for scm, status,
subsystem, web, and bug information when those flags are enabled.

Normal text output behavior is completely unchanged when --json is
not specified.

Assisted-by: Claude:claude-opus-4-6
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 scripts/get_maintainer.pl | 114 +++++++++++++++++++++++++++++---------
 1 file changed, 87 insertions(+), 27 deletions(-)

diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 4414194bedcfd..37817ca701bd6 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -68,6 +68,7 @@ my $pattern_depth = 0;
 my $self_test = undef;
 my $version = 0;
 my $help = 0;
+my $json = 0;
 my $find_maintainer_files = 0;
 my $maintainer_path;
 my $vcs_used = 0;
@@ -285,6 +286,7 @@ if (!GetOptions(
 		'find-maintainer-files' => \$find_maintainer_files,
 		'mpath|maintainer-path=s' => \$maintainer_path,
 		'self-test:s' => \$self_test,
+		'json!' => \$json,
 		'v|version' => \$version,
 		'h|help|usage' => \$help,
 		)) {
@@ -648,39 +650,74 @@ my %deduplicate_name_hash = ();
 my %deduplicate_address_hash = ();
 
 my @maintainers = get_maintainers();
-if (@maintainers) {
-    @maintainers = merge_email(@maintainers);
-    output(@maintainers);
-}
 
-if ($scm) {
-    @scm = uniq(@scm);
-    output(@scm);
-}
+if ($json) {
+    my @json_maintainers;
+    if (@maintainers) {
+	my %saw;
+	for (@maintainers) {
+	    my ($address, $role) = @$_;
+	    if (!$saw{$address}) {
+		my ($name, $email_addr) = parse_email($address);
+		my $entry = '{"name":"' . json_escape_str($name) .
+			    '","email":"' . json_escape_str($email_addr) . '"';
+		$entry .= ',"role":"' . json_escape_str($role) . '"' if ($output_roles && $role ne '');
+		$entry .= '}';
+		push(@json_maintainers, $entry);
+		$saw{$address} = 1;
+	    }
+	}
+    }
 
-if ($output_substatus) {
-    @substatus = uniq(@substatus);
-    output(@substatus);
-}
+    @scm = uniq(@scm) if ($scm);
+    @status = uniq(@status) if ($status);
+    @subsystem = uniq(@subsystem) if ($subsystem);
+    @web = uniq(@web) if ($web);
+    @bug = uniq(@bug) if ($bug);
 
-if ($status) {
-    @status = uniq(@status);
-    output(@status);
-}
+    my @fields;
+    push(@fields, '"maintainers":[' . join(',', @json_maintainers) . ']');
+    push(@fields, '"scm":' . json_str_array(@scm)) if ($scm);
+    push(@fields, '"status":' . json_str_array(@status)) if ($status);
+    push(@fields, '"subsystem":' . json_str_array(@subsystem)) if ($subsystem);
+    push(@fields, '"web":' . json_str_array(@web)) if ($web);
+    push(@fields, '"bug":' . json_str_array(@bug)) if ($bug);
+    print('{' . join(',', @fields) . '}' . "\n");
+} else {
+    if (@maintainers) {
+	@maintainers = merge_email(@maintainers);
+	output(@maintainers);
+    }
 
-if ($subsystem) {
-    @subsystem = uniq(@subsystem);
-    output(@subsystem);
-}
+    if ($scm) {
+	@scm = uniq(@scm);
+	output(@scm);
+    }
 
-if ($web) {
-    @web = uniq(@web);
-    output(@web);
-}
+    if ($output_substatus) {
+	@substatus = uniq(@substatus);
+	output(@substatus);
+    }
 
-if ($bug) {
-    @bug = uniq(@bug);
-    output(@bug);
+    if ($status) {
+	@status = uniq(@status);
+	output(@status);
+    }
+
+    if ($subsystem) {
+	@subsystem = uniq(@subsystem);
+	output(@subsystem);
+    }
+
+    if ($web) {
+	@web = uniq(@web);
+	output(@web);
+    }
+
+    if ($bug) {
+	@bug = uniq(@bug);
+	output(@bug);
+    }
 }
 
 exit($exit);
@@ -1099,6 +1136,7 @@ Output type options:
   --separator [, ] => separator for multiple entries on 1 line
     using --separator also sets --nomultiline if --separator is not [, ]
   --multiline => print 1 entry per line
+  --json => output results as JSON
 
 Other options:
   --pattern-depth => Number of pattern directory traversals (default: 0 (all))
@@ -2549,6 +2587,28 @@ sub merge_email {
     return @lines;
 }
 
+sub json_escape_str {
+    my ($str) = @_;
+    $str =~ s/\\/\\\\/g;
+    $str =~ s/"/\\"/g;
+    $str =~ s/\n/\\n/g;
+    $str =~ s/\r/\\r/g;
+    $str =~ s/\t/\\t/g;
+    $str =~ s/\x08/\\b/g;
+    $str =~ s/\x0c/\\f/g;
+    $str =~ s/([\x00-\x07\x0b\x0e-\x1f])/sprintf("\\u%04x", ord($1))/ge;
+    return $str;
+}
+
+sub json_str_array {
+    my (@arr) = @_;
+    my @quoted;
+    foreach my $s (@arr) {
+	push(@quoted, '"' . json_escape_str($s) . '"');
+    }
+    return '[' . join(',', @quoted) . ']';
+}
+
 sub output {
     my (@parms) = @_;
 
-- 
2.53.0


             reply	other threads:[~2026-04-06 17:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 17:01 Sasha Levin [this message]
2026-04-07  2:38 ` Joe Perches
2026-04-08 19:45 ` [PATCH v2] " Sasha Levin
2026-04-08 20:06   ` Joe Perches

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=20260406170138.4034983-1-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@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®