[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <0618B96B-2F6C-4D67-9D32-0B74E898496F@codeaurora.org>
Date: Tue, 17 Sep 2013 10:52:02 -0500
From: Kumar Gala <galak@...eaurora.org>
To: Olof Johansson <olof@...om.net>
Cc: Rohit Vaswani <rvaswani@...eaurora.org>,
David Brown <davidb@...eaurora.org>,
Rob Herring <rob.herring@...xeda.com>,
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>,
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 16, 2013, at 1:50 PM, Olof Johansson wrote:
> On Mon, Sep 16, 2013 at 11:46 AM, Kumar Gala <galak@...eaurora.org> wrote:
>
>> I think the two options are either:
>>
>> qcom-msm*, qcom-apq*, etc
>>
>> or
>>
>> qcom/msm-*, qcom/apq*, etc
>>
>> I'm guessing we'll end up without the dir and in the future have:
>>
>> qcom/qcom-msm-*, qcom/qcom-apq-*
>>
>> Olof???
>
>
> When you create the dir, you can go from qcom-msm-* to qcom/msm-*, but
> still produce qcom-msm-*.dtb as the build output. We care about
> keeping the DTB name stable, not DTS. As long as they just conform to
> those two patterns it's easy to handle through makefile targets.
Sounds good, Rohit let's go ahead with qcom-msm-*, qcom-apq-*.
- k
--
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