[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51ED9018.1020003@gmail.com>
Date: Mon, 22 Jul 2013 15:03:36 -0500
From: Rob Herring <robherring2@...il.com>
To: Pawel Moll <pawel.moll@....com>
CC: Grant Likely <grant.likely@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Rutland <Mark.Rutland@....com>,
Stephen Warren <swarren@...dotorg.org>,
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 07/22/2013 11:50 AM, Pawel Moll wrote:
> On Sat, 2013-07-20 at 04:19 +0100, Grant Likely wrote:
>> +F: include/dt-bindings
>
> One thing we didn't finish talking about was the question if this
> directory is supposed to contain *.dtsi files as well? The obvious
> problem I have is a vexpress motherboard being (well, actually not bein
> right now) shared between arch/arm/boot/dts and arch/arm64/boot/dts.
Please no. When we move dts files out of the kernel, 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.
Rob
> Pawel
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
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