From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: "Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove entry to non-existing file in MOBILEYE MIPS SOCS
Date: Mon, 4 Mar 2024 14:28:28 +0100 [thread overview]
Message-ID: <ZeXMfP6UeFcV7k4y@alpha.franken.de> (raw)
In-Reply-To: <20240222143312.27757-1-lukas.bulwahn@gmail.com>
On Thu, Feb 22, 2024 at 03:33:12PM +0100, Lukas Bulwahn wrote:
> Commit f34158edd249 ("MAINTAINERS: Add entry for Mobileye MIPS SoCs") adds
> the section MOBILEYE MIPS SOCS with a file entry to the non-existing file
> include/dt-bindings/soc/mobileye,eyeq5.h.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
>
> Possibly, this file was part of an early patch series, but in the final
> patch series, this file does not appear anymore.
>
> Delete this file entry in the MOBILEYE MIPS SOCS section.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 28b2013031bd..19ac6a8e46b2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14914,7 +14914,6 @@ F: Documentation/devicetree/bindings/mips/mobileye.yaml
> F: arch/mips/boot/dts/mobileye/
> F: arch/mips/configs/eyeq5_defconfig
> F: arch/mips/mobileye/board-epm5.its.S
> -F: include/dt-bindings/soc/mobileye,eyeq5.h
>
> MODULE SUPPORT
> M: Luis Chamberlain <mcgrof@kernel.org>
> --
> 2.17.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2024-03-04 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 14:33 Lukas Bulwahn
2024-03-04 13:19 ` Gregory CLEMENT
2024-03-04 13:28 ` Thomas Bogendoerfer [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=ZeXMfP6UeFcV7k4y@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=gregory.clement@bootlin.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=theo.lebrun@bootlin.com \
--cc=vladimir.kondratiev@mobileye.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
all inboxes | Powered by JetHome®