[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <584008C3-983C-4423-A76E-38DD67C2F1D9@codeaurora.org>
Date: Thu, 12 Sep 2013 14:26:53 -0500
From: Kumar Gala <galak@...eaurora.org>
To: Olof Johansson <olof@...om.net>
Cc: Rob Herring <robherring2@...il.com>,
David Brown <davidb@...eaurora.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Stephen Warren <swarren@...dotorg.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Russell King <linux@....linux.org.uk>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org list" <linux-kernel@...r.kernel.org>,
Rohit Vaswani <rvaswani@...eaurora.org>,
linux-arm-msm@...r.kernel.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: msm: Move msm devicetrees under a Qualcomm dir
On Sep 12, 2013, at 1:46 PM, Olof Johansson wrote:
> On Thu, Sep 12, 2013 at 11:20 AM, Rob Herring <robherring2@...il.com> wrote:
>
>> As Stephen W has pointed out previously, the dtb filename itself is or
>> may be an ABI and the bootloader may be hardcoded to a name. So we
>> should avoid future renames.
>
> We still have the choice of producing the dtb files under
> arch/arm/boot/dts even if we move dts/dtsi files one level deeper, as
> long as we keep the filenames consistent. So we can do a move, just
> not a rename.
Looking at arch/arm/boot/dts/ we are all over the place, so what's the naming convention we are going forward with?
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
--
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