From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Pawel Moll <pawel.moll@arm.com>,
Rob Herring <robherring2@gmail.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <Mark.Rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Olof Johansson <olof@lixom.net>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
Date: Tue, 23 Jul 2013 15:26:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.03.1307231520280.15022@syhkavp.arg> (raw)
In-Reply-To: <51EEC49A.4080909@wwwdotorg.org>
On Tue, 23 Jul 2013, Stephen Warren wrote:
> Or perhaps, we could move *.dts around in the kernel to match the
> proposed DT tree structure before that point in time?
>
> >> we will still need
> >> to copy dt-bindings into the kernel. Also, I think we should move all
> >> dts files out of arch subdirs and arrange by vendor or soc family. I'm
> >> sure there are some cases that structure doesn't fit well, but there is
> >> very little in a dts tied to a cpu architecture.
> >
> > I couldn't agree more. So:
> >
> > <root>/include/dt-bindings/vendor/*?
>
> > <root>/dts/vendor/*?
>
> I would tend to prefer that option, ...
Please make a generic top-level directory for DT and move the dtc code
in there as well. Something like:
<root>/devicetree/dtc/*
<root>/devicetree/dts/*
Nicolas
prev parent reply other threads:[~2013-07-23 19:26 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
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 [this message]
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=alpine.LFD.2.03.1307231520280.15022@syhkavp.arg \
--to=nicolas.pitre@linaro.org \
--cc=Mark.Rutland@arm.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.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
all inboxes | Powered by JetHome®