From: Joe Perches <joe@perches.com>
To: Grant Likely <grant.likely@linaro.org>
Cc: Olof Johansson <olof@lixom.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
Date: Sun, 21 Jul 2013 17:43:51 -0700 [thread overview]
Message-ID: <1374453831.2061.10.camel@joe-AO722> (raw)
In-Reply-To: <CACxGe6tJedLnM6FmvuQWTpGNFsefTn14cbnBMoWnr1gfA0seoQ@mail.gmail.com>
On Mon, 2013-07-22 at 01:36 +0100, Grant Likely wrote:
> On Sun, Jul 21, 2013 at 10:46 AM, Grant Likely <grant.likely@linaro.org> wrote:
> > On Sun, Jul 21, 2013 at 1:29 AM, Joe Perches <joe@perches.com> wrote:
> >> On Sat, 2013-07-20 at 17:17 -0700, Olof Johansson wrote:
> >>> On Fri, Jul 19, 2013 at 8:19 PM, Grant Likely <grant.likely@linaro.org> wrote:
> >>> > Device tree bindings require a lot more attention than they used to.
> >>> > We've got a group of volunteers willing to take over maintaining
> >>> > bindings. This patch adds them to the MAINTAINERS file.
> >> []
> >>> > diff --git a/MAINTAINERS b/MAINTAINERS
> >> []
> >>> > +OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
> >> []
> >>> > +F: arch/*/
> >> []
> >>> This seems a bit broad.
> >>
> >> Yep, that's every file anywhere under arch.
> >
> > yeah, that was a c/p mistake. I'll drop that line before committing.
>
> In fact, if things go well with the schema tool, it would be possible
> to leave out the .dts files entirely as far as binding review goes.
> The binding would be the important part and the .dts files would be
> checked against that. That's something for the future though.
btw: please add a terminating slash to
the file pattern directories
+F: Documentation/devicetree/
+F: arch/*/boot/dts/
+F: include/dt-bindings/
next prev parent reply other threads:[~2013-07-22 0:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 3:19 [PATCH 1/3] MAINTAINERS: Remove Grant Likely Grant Likely
2013-07-20 3:19 ` [PATCH 2/3] MAINTAINERS: Change device tree mailing list Grant Likely
2013-07-20 3:19 ` [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership Grant Likely
2013-07-20 16:20 ` Linus Walleij
2013-07-21 13:46 ` Jon Loeliger
2013-07-22 0:33 ` Grant Likely
2013-07-22 1:27 ` David Gibson
2013-07-22 17:38 ` Jon Loeliger
2013-07-21 0:17 ` Olof Johansson
2013-07-21 0:29 ` Joe Perches
2013-07-21 9:46 ` Grant Likely
2013-07-22 0:36 ` Grant Likely
2013-07-22 0:43 ` Joe Perches [this message]
2013-07-22 0:48 ` Grant Likely
2013-07-22 17:29 ` Olof Johansson
2013-07-21 18:56 ` Rob Herring
2013-07-22 0:35 ` Grant Likely
2013-07-22 20:31 ` Rob Herring
2013-07-22 21:36 ` Jon Loeliger
2013-07-23 3:27 ` Rob Herring
2013-07-22 16:50 ` Pawel Moll
2013-07-22 20:03 ` Rob Herring
2013-07-23 17:14 ` Pawel Moll
2013-07-23 17:59 ` Stephen Warren
2013-07-23 18:09 ` Ian Campbell
2013-07-23 18:44 ` Rob Herring
2013-07-23 18:55 ` Ian Campbell
2013-07-23 19:28 ` Rob Herring
2013-07-23 19:53 ` Stephen Warren
2013-08-07 10:53 ` Ian Campbell
2013-07-23 19:26 ` Nicolas Pitre
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=1374453831.2061.10.camel@joe-AO722 \
--to=joe@perches.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=swarren@wwwdotorg.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