From: "Eugene Mavick" <m@mavick.dev>
To: "Joe Perches" <joe@perches.com>, "Eugene Mavick" <m@mavick.dev>,
"Andy Whitcroft" <apw@canonical.com>,
"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: MAINTAINERS: warn on missing paths
Date: Mon, 13 Jul 2026 22:47:11 +0800 [thread overview]
Message-ID: <DJXIXC41044G.1FP7HUU54L2UW@mavick.dev> (raw)
In-Reply-To: <1e63b7af71b174b24212831532c94d49877441e3.camel@perches.com>
On Sun Jul 12, 2026 at 5:04 PM +08, Joe Perches wrote:
> On Sun, 2026-07-12 at 16:14 +0800, Eugene Mavick wrote:
>> ```
>> Warn when F: or X: entries point to nonexistent files or patterns.
>> There have been instances of typos in file entries in the past, and this
>> patch helps prevents that.
>
> Just fyi:
>
> if you care to do something about the missing MAINTAINER file patterns
>
> $ ./scripts/get_maintainer.pl --self-test=patterns
> ./MAINTAINERS:2764: warning: no file matches F: arch/arm/mach-ep93xx/ts72xx.c
> ./MAINTAINERS:7654: warning: no file matches F: include/linux/dma-buf/
> ./MAINTAINERS:7897: warning: no file matches F: include/linux/drbd*
> ./MAINTAINERS:10017: warning: no file matches F: include/linux/fs_types.h
> ./MAINTAINERS:12694: warning: no file matches F: drivers/gpu/drm/ci/xfails/powervr*
> ./MAINTAINERS:16731: warning: no file matches F: Documentation/devicetree/bindings/display/bridge/megachips-stdpxxxx-ge-b850v3-fw.txt
> ./MAINTAINERS:21913: warning: no file matches F: sound/arm/pxa*
> ./MAINTAINERS:22364: warning: no file matches F: include/dt-bindings/media/*qcom*
> ./MAINTAINERS:25130: warning: no file matches F: tools/testing/selftests/net/so_txtime.c
> ./MAINTAINERS:25342: warning: no file matches F: Documentation/devicetree/bindings/media/i2c/sony,imx678.yaml
> ./MAINTAINERS:28376: warning: no file matches F: include/linux/vsi-iommu.h
Thanks, here's the patch:
https://lore.kernel.org/all/20260713-fix-maintainers-entries-v1-1-800c6ad14201@mavick.dev/
prev parent reply other threads:[~2026-07-13 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 8:14 [PATCH] checkpatch: MAINTAINERS: warn on missing paths Eugene Mavick
2026-07-12 8:20 ` Joe Perches
2026-07-12 9:04 ` Joe Perches
2026-07-13 14:47 ` Eugene Mavick [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=DJXIXC41044G.1FP7HUU54L2UW@mavick.dev \
--to=m@mavick.dev \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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