From: Tom Rini <trini@konsulko.com>
To: Michal Simek <michal.simek@amd.com>
Cc: u-boot@lists.u-boot-project.org, git@amd.com,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH 0/2] MAINTAINERS: Cleanup non existing files
Date: Fri, 21 Aug 2026 14:33:57 -0600 [thread overview]
Message-ID: <20260821203357.GU523975@bill-the-cat> (raw)
In-Reply-To: <20260821200507.GA3894128@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Fri, Aug 21, 2026 at 02:05:07PM -0600, Tom Rini wrote:
> On Thu, Aug 13, 2026 at 09:11:15AM +0200, Michal Simek wrote:
>
> > Hi,
> >
> > I found in my Microblaze fragment that cmd_mfsl.c doesn't exist but still
> > it is recorded. That's why I wanted to check all entries and found that
> > there are also other files which doesn't exist.
> >
> > Tom: maybe good to run it in a CI to make sure that we don't get out of
> > sync.
>
> Sounds like a good idea. I see between your posting and today another
> bad entry has been added, I'll go take care of it.
And, I'm going to take this series to start with, as it's a good place
to start. But it doesn't check all MAINTAINER files, just the top-level
one. Cleanly updating it for checking all files needs a small bit of
thinking. I Kludged it in and, whew, there's 252 bad listings. If you
update the script, I'll take care of the problems.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-08-21 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 7:11 [PATCH 0/2] MAINTAINERS: Cleanup non existing files Michal Simek
2026-08-13 7:11 ` [PATCH 1/2] scripts: Add MAINTAINERS F: file existence checker Michal Simek
2026-08-13 7:11 ` [PATCH 2/2] MAINTAINERS: Remove references to not existing files Michal Simek
2026-08-21 20:05 ` [PATCH 0/2] MAINTAINERS: Cleanup non " Tom Rini
2026-08-21 20:33 ` 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=20260821203357.GU523975@bill-the-cat \
--to=trini@konsulko.com \
--cc=git@amd.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michal.simek@amd.com \
--cc=quentin.schulz@cherry.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.