[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.03.1307231520280.15022@syhkavp.arg>
Date: Tue, 23 Jul 2013 15:26:15 -0400 (EDT)
From: Nicolas Pitre <nicolas.pitre@...aro.org>
To: Stephen Warren <swarren@...dotorg.org>
cc: Pawel Moll <pawel.moll@....com>,
Rob Herring <robherring2@...il.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Rutland <Mark.Rutland@....com>,
Ian Campbell <ian.campbell@...rix.com>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
Olof Johansson <olof@...om.net>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists