From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Lee Jones <lee@kernel.org>, Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file patterns in TQ SYSTEMS BOARD & DRIVER SUPPORT
Date: Fri, 03 Nov 2023 09:15:52 +0100 [thread overview]
Message-ID: <13490070.uLZWGnKmhe@steina-w> (raw)
In-Reply-To: <11135245.nUPlyArG6x@steina-w>
Hi,
Am Freitag, 25. August 2023, 08:19:32 CET schrieb Alexander Stein:
> Hi Lukas,
>
> Am Freitag, 25. August 2023, 07:58:21 CEST schrieb Lukas Bulwahn:
> > Commit 77da3f22b3d5 ("MAINTAINERS: Add entry for TQ-Systems device trees
> > and drivers") adds some file patterns for files in arch/arm/boot/dts/, but
> > those patterns do not match any files in the repository. Hence,
> > ./scripts/get_maintainer.pl --self-test=patterns complains about broken
> > references. The files of interest are actually in the directory
> > arch/arm/boot/dts/nxp/imx/.
>
> Nice, I didn't know about --self-test=patterns. But you are right, the
> patterns do not match anymore since arch/arm dts restructuring.
> I also suggest to add the Fixes tag:
>
> Fixes: 77da3f22b3d54 ("MAINTAINERS: Add entry for TQ-Systems device trees
> and drivers")
> Reviewed-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Any progress on this?
Thanks
Alexander
> > Adjust the file patterns to match the intended files.
> >
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > ---
> > Lee, please pick this minor clean-up patch.
> >
> > MAINTAINERS | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 52277ee9c1b8..f5d4058b7ff4 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -21817,9 +21817,9 @@ TQ SYSTEMS BOARD & DRIVER SUPPORT
> >
> > L: linux@ew.tq-group.com
> > S: Supported
> > W: https://www.tq-group.com/en/products/tq-embedded/
> >
> > -F: arch/arm/boot/dts/imx*mba*.dts*
> > -F: arch/arm/boot/dts/imx*tqma*.dts*
> > -F: arch/arm/boot/dts/mba*.dtsi
> > +F: arch/arm/boot/dts/nxp/imx/imx*mba*.dts*
> > +F: arch/arm/boot/dts/nxp/imx/imx*tqma*.dts*
> > +F: arch/arm/boot/dts/nxp/imx/mba*.dtsi
> >
> > F: arch/arm64/boot/dts/freescale/imx*mba*.dts*
> > F: arch/arm64/boot/dts/freescale/imx*tqma*.dts*
> > F: arch/arm64/boot/dts/freescale/mba*.dtsi
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-11-03 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 5:58 [PATCH] MAINTAINERS: adjust file patterns in TQ SYSTEMS BOARD & DRIVER SUPPORT Lukas Bulwahn
2023-08-25 6:19 ` Alexander Stein
2023-11-03 8:15 ` Alexander Stein [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-23 11:32 Lukas Bulwahn
2024-02-29 14:50 ` Alexander Stein
2024-05-22 11:00 ` Alexander Stein
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=13490070.uLZWGnKmhe@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=matthias.schiffer@ew.tq-group.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