From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.u-boot-project.org
Cc: Michal Simek <michal.simek@amd.com>
Subject: [PATCH v3 7/7] CI: Run scripts/check_maintainers_files.sh in the existing MAINTAINERS job
Date: Thu, 10 Sep 2026 14:03:09 -0600 [thread overview]
Message-ID: <20260910200310.3503830-8-trini@konsulko.com> (raw)
In-Reply-To: <20260910200310.3503830-1-trini@konsulko.com>
Rename the existing job that does some checking of MAINTAINERS file
contents already to be a little clearer that it's doing two things now,
and then also run scripts/check_maintainers_files.sh in this job.
Suggested-by: Michal Simek <michal.simek@amd.com>
Signed-off-by: Tom Rini <trini@konsulko.com>
---
.azure-pipelines.yml | 3 ++-
.gitlab-ci.yml | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 015fc15d5c29..5130058925d5 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -90,7 +90,7 @@ stages:
make infodocs
- job: maintainers
- displayName: 'Ensure all configs have MAINTAINERS entries'
+ displayName: 'Check all configs are in MAINTAINERS and validate MAINTAINERS'
pool:
vmImage: $(ubuntu_vm)
container:
@@ -99,6 +99,7 @@ stages:
steps:
- script: |
./tools/buildman/buildman --maintainer-check
+ ./scripts/check_maintainers_files.sh
- job: allyesconfig_and_tools
displayName: 'Ensure allyesconfig, tools-only and envtools build'
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 9831dd61bc18..e08068f1cbf5 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -189,11 +189,11 @@ docs:
- make htmldocs KDOC_WERROR=1
- make infodocs
-# ensure all configs have MAINTAINERS entries
-Check for configs without MAINTAINERS entry:
+Check all configs are in MAINTAINERS and validate MAINTAINERS:
extends: .testsuites
script:
- ./tools/buildman/buildman --maintainer-check
+ - ./scripts/check_maintainers_files.sh
# Ensure host tools build
Build allyesconfig, tools-only and envtools:
--
2.43.0
prev parent reply other threads:[~2026-09-10 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:03 [PATCH v3 0/7] Cleanup MAINTAINERS entries Tom Rini
2026-09-10 20:03 ` [PATCH v3 1/7] scripts: Check F: entries in all MAINTAINERS files Tom Rini
2026-09-10 20:03 ` [PATCH v3 2/7] MAINTAINERS: tegra: Update and correct entries Tom Rini
2026-09-11 16:33 ` Svyatoslav Ryhel
2026-09-10 20:03 ` [PATCH v3 3/7] MAINTAINERS: rockchip: Use N for rk3576-nanopi-r76s Tom Rini
2026-09-10 20:03 ` [PATCH v3 4/7] MAINTAINERS: Fix "typo" and similar incorrect entries Tom Rini
2026-09-10 20:03 ` [PATCH v3 5/7] MAINTAINERS: Correct entries missed during renames Tom Rini
2026-09-10 20:03 ` [PATCH v3 6/7] MAINTAINERS: Removed files Tom Rini
2026-09-10 20:03 ` Tom Rini [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=20260910200310.3503830-8-trini@konsulko.com \
--to=trini@konsulko.com \
--cc=michal.simek@amd.com \
--cc=u-boot@lists.u-boot-project.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