All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: Michal Simek <michal.simek@amd.com>, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH 3/3] MAINTAINERS: Remove references to not existing files
Date: Mon, 24 Aug 2026 09:28:28 -0600	[thread overview]
Message-ID: <20260824152703.GF523975@bill-the-cat> (raw)
In-Reply-To: <4d7ef207-189d-4b7b-8fb1-385dc1411add@cherry.de>

[-- Attachment #1: Type: text/plain, Size: 3076 bytes --]

[CC list trimmed, Google did not like that long list..]

On Mon, Aug 24, 2026 at 12:16:22PM +0200, Quentin Schulz wrote:
> 
> 
> On 8/24/26 12:14 PM, Michal Simek wrote:
> > 
> > 
> > On 8/24/26 12:11, Quentin Schulz wrote:
> > > 
> > > 
> > > On 8/24/26 12:07 PM, Michal Simek wrote:
> > > > 
> > > > 
> > > > On 8/24/26 11:54, Quentin Schulz wrote:
> > > > > Hi Michal,
> > > > > 
> > > > > On 8/24/26 9:18 AM, Michal Simek wrote:
> > > > > > A number of file (F:) entries across the MAINTAINERS files pointed to
> > > > > > files or directories which had been renamed or removed over time. Drop
> > > > > > these stale references so that every F: entry resolves to an existing
> > > > > > path.
> > > > > > 
> > > > > > Signed-off-by: Michal Simek <michal.simek@amd.com>
> > > > > > ---
> > > > > [...]
> > > > > > diff --git a/arch/arm/mach-rockchip/rk3576/MAINTAINERS
> > > > > > b/arch/arm/ mach- rockchip/rk3576/MAINTAINERS
> > > > > > index 79cf9e97f70b..62c3ce765e0d 100644
> > > > > > --- a/arch/arm/mach-rockchip/rk3576/MAINTAINERS
> > > > > > +++ b/arch/arm/mach-rockchip/rk3576/MAINTAINERS
> > > > > > @@ -13,7 +13,6 @@ F:    configs/nanopi-m5-rk3576_defconfig
> > > > > >   NANOPI-R76S-RK3576
> > > > > >   M:    Jonas Karlman <jonas@kwiboo.se>
> > > > > >   S:    Maintained
> > > > > > -F:    arch/arm/dts/rk3576-nanopi-r76s*
> > > > > 
> > > > > This is a leftover from v1 which had a file there, but we
> > > > > merged the v2. See
> > > > > https://eur02.safelinks.protection.outlook.com/?
> > > > > url=https%3A%2F%2Flore.kernel.org%2Fu-
> > > > > boot%2F20260108143551.4017839-3- jonas%40kwiboo.se%2F&data=05%7C02%7Cquentin.schulz%40cherry.de%7C20d22328c2c14b04e70608df01c79b5d%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639231628996802560%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BGNHaQOa3XRWnaRD%2BMBZJDH3t54Q17ZQGynxdQr34e8%3D&reserved=0
> > > > > and https://lore.kernel.org/u-boot/20260310000610.592998-3-jonas@kwiboo.se/
> > > > > 
> > > > > For now we don't have U-Boot-specific additions to the
> > > > > upstream DTS for the NanoPi R76S but we could in the future,
> > > > > so having a wildcard like that would allow Jonas to be
> > > > > notified if one ever gets added. So it's not completely
> > > > > useless. No strong opinion on still deleting it or not.
> > > > 
> > > > File is there or not. If you add it in future you should extend
> > > > that fragment and that's it.
> > > > 
> > > 
> > > And Jonas won't be Cc'ed on it being added if someone forgets to
> > > update MAINTAINERS (which honestly is very likely), that's my point.
> > > He maintains the board but won't be notified if something directly
> > > related to the board he maintains gets added.
> > 
> > you can use N: regex fragment for it.
> > 
> 
> Fair enough.

And part of the point of this series is to enable CI to make sure no
more mismatches get in, so we can't have speculative entries.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-08-24 15:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  7:18 [PATCH 0/3] MAINTAINERS: Cleanup non existing files arch/board Michal Simek
2026-08-24  7:18 ` [PATCH 1/3] xilinx: Correct zynqmp_r5 MAINTAINERS fragment Michal Simek
2026-08-24  7:18 ` [PATCH 2/3] scripts: Check F: entries in all MAINTAINERS files Michal Simek
2026-08-24  7:18 ` [PATCH 3/3] MAINTAINERS: Remove references to not existing files Michal Simek
2026-08-24  7:18   ` Michal Simek
2026-08-24  8:01   ` Johan Jonker
2026-08-24  9:03     ` Michal Simek
2026-08-24  9:54   ` Quentin Schulz
2026-08-24 10:07     ` Michal Simek
2026-08-24 10:11       ` Quentin Schulz
2026-08-24 10:14         ` Michal Simek
2026-08-24 10:16           ` Quentin Schulz
2026-08-24 15:28             ` Tom Rini [this message]
2026-08-24 16:24   ` Tom Rini
2026-08-25  5:12     ` Michal Simek
2026-08-25 13:40   ` Svyatoslav Ryhel
2026-08-25 13:48   ` Bryan Brattlof
2026-08-25 14:28     ` Tom Rini
2026-08-25 14:33       ` Michal Simek
2026-08-25 15:46         ` Bryan Brattlof
2026-08-25 15:52           ` Michal Simek

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=20260824152703.GF523975@bill-the-cat \
    --to=trini@konsulko.com \
    --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.