From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>
Cc: Steve Wahl <steve.wahl@hpe.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>
Subject: Re: [PATCH] MAINTAINERS: Add entry for HPE Superdome Flex (UV) maintainers
Date: Fri, 21 Aug 2020 11:35:50 -0700 [thread overview]
Message-ID: <745aba13716b91cf58a45468083b59201d1530fc.camel@perches.com> (raw)
In-Reply-To: <CAL_JsqL0v6PXgMLVZzqZwjpZ4KTUGmutg6Z0YuvTccdAUa-=mw@mail.gmail.com>
On Fri, 2020-08-21 at 12:17 -0600, Rob Herring wrote:
> I have another reason for wanting the split. I want to generate a
> MAINTAINERS file from the DT schema files. We have the data there and
> it's checked automatically. I don't care to either continually tell
> folks to add a MAINTAINERS entry or tell them to run checkpatch.pl to
> tell them that. But if the infrastructure got merged, would that
> already work?
It already gets addresses from yaml files.
The same could be done for dts/dtsi files.
Last month I proposed:
https://lore.kernel.org/linux-arm-kernel/da52724655ff2161add7fb27fea8fc673028b9fc.camel@perches.com/
next prev parent reply other threads:[~2020-08-21 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 15:48 Steve Wahl
2020-08-21 16:45 ` Rob Herring
2020-08-21 17:05 ` Joe Perches
2020-08-21 18:17 ` Rob Herring
2020-08-21 18:35 ` Joe Perches [this message]
2020-08-21 17:40 ` [PATCH] get_maintainer: Exclude MAINTAINERS file(s) from --git-fallback and --git-blame Joe Perches
2020-08-21 18:05 ` [PATCH V2] get_maintainer: Exclude MAINTAINERS file(s) from --git-fallback Joe Perches
2020-08-24 14:45 ` [PATCH] MAINTAINERS: Add entry for HPE Superdome Flex (UV) maintainers Steve Wahl
2020-08-24 15:36 ` Borislav Petkov
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=745aba13716b91cf58a45468083b59201d1530fc.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=dimitri.sivanich@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh@kernel.org \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.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®