From: Jon Loeliger <jdl@jdl.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
Date: Sun, 21 Jul 2013 08:46:11 -0500 [thread overview]
Message-ID: <E1V0txk-0007v7-0J@jdl.com> (raw)
In-Reply-To: <CACRpkdb2bPQOD2CBzbF0K33mZZwKwGSCO6B4djesVd5DR-Z1tA@mail.gmail.com>
> On Sat, Jul 20, 2013 at 5:19 AM, 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.
> >
> > This group still needs to work out a process for maintainership and how
> > they are going to work together. I recommend that they set up a shared
> > tree on git.kernel.org that they each have commit access to similar to
> > the tip tree or the arm-soc tree, but it is up to them.
> >
> > Signed-off-by: Grant Likely <grant.likely@linaro.org>
> > Cc: Pawel Moll <pawel.moll@arm.com>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Stephen Warren <swarren@wwwdotorg.org>
> > Cc: Ian Campbell <ian.campbell@citrix.com>
> > Cc: Rob Herring <rob.herring@calxeda.com>
> > Cc: Olof Johansson <olof@lixom.net>
> > Cc: devicetree-discuss@lists.ozlabs.org
> > Cc: devicetree@vger.kernel.org
>
> Excellent move.
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
Perhaps it is time to also place the official repo
of the Device Tree Compiler on git,kernel.org as well?
Other opinions?
jdl
next prev parent reply other threads:[~2013-07-21 14:33 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 [this message]
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
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=E1V0txk-0007v7-0J@jdl.com \
--to=jdl@jdl.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.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
Powered by JetHome