From: Joe Perches <joe@perches.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>, Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH] get_maintainer: add email addresses from dts files
Date: Sun, 12 Feb 2023 13:13:19 -0800 [thread overview]
Message-ID: <b82c782ee8c789a0bdc702526fd993952cabb6a2.camel@perches.com> (raw)
In-Reply-To: <0d1f5d23-7a91-eee9-c7fe-044db8869735@linaro.org>
On Sun, 2023-02-12 at 16:51 +0100, Krzysztof Kozlowski wrote:
> On 11/02/2023 17:27, Joe Perches wrote:
> > On Sat, 2023-02-11 at 13:14 +0100, Krzysztof Kozlowski wrote:
> > > The DTS/DTSI files represent hardware description for Linux kernel,
> > > which is necessary to properly recognize and configure hardware by
> > > Linux. DTS is usually created by people having the actual hardware and
> > > having interest in keeping it in good shape. Such people can provide
> > > review (they might have board schematics) and testing. Unfortunately
> > > they mostly do not appear in MAINTAINERS file. Adding per-DTS entries
> > > to MAINTAINERS would quickly make it bloated (hundreds of new per-DTS
> > > entries).
> > >
> > > On the other hand there is no point in CC-ing every Copyright email
> > > appearing in files, because it might be outdated.
That's what .mailmap is for.
> > > Add new in-file
> > > pattern for storing maintainers dedicated to specific boards:
I think adding Maintainer: who <who@foo.tld>
to each dts and dtsi file would be a lot of unnecessary changes
$ git ls-files | grep -P '\.dtsi?$' | wc -l
4673
> > > This is rework of earlier approach:
> > > Link: https://lore.kernel.org/r/20210809080204.8381-1-shawnguo@kernel.org
> >
> > Why the rework? I think the older one is much simpler.
> >
> > I believe I forwarded the older one to Andrew Morton awhile back.
> > I'll check to see what happened to it.
>
> It was never merged, thus I assumed some changes are needed, e.g. to
> ignore emails in copyrights.
I think the old one is fine.
next prev parent reply other threads:[~2023-02-12 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 12:14 Krzysztof Kozlowski
2023-02-11 12:34 ` Krzysztof Kozlowski
2023-02-11 16:27 ` Joe Perches
2023-02-12 15:51 ` Krzysztof Kozlowski
2023-02-12 21:13 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-30 12:29 Shawn Guo
2020-09-30 10:54 ` Krzysztof Kozlowski
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=b82c782ee8c789a0bdc702526fd993952cabb6a2.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.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 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®