From: galak@codeaurora.org (Kumar Gala)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: msm: Move msm devicetrees under a Qualcomm dir
Date: Tue, 17 Sep 2013 10:52:02 -0500 [thread overview]
Message-ID: <0618B96B-2F6C-4D67-9D32-0B74E898496F@codeaurora.org> (raw)
In-Reply-To: <CAOesGMgCvnuX918pt6vT0_QsHdfJ8b813iu2tXRHvdpL8GZ3dg@mail.gmail.com>
On Sep 16, 2013, at 1:50 PM, Olof Johansson wrote:
> On Mon, Sep 16, 2013 at 11:46 AM, Kumar Gala <galak@codeaurora.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
prev parent reply other threads:[~2013-09-17 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 16:37 [PATCH] ARM: msm: Move msm devicetrees under a Qualcomm dir Kumar Gala
2013-09-12 16:46 ` Olof Johansson
2013-09-12 16:53 ` Kumar Gala
2013-09-12 17:06 ` Olof Johansson
2013-09-12 17:55 ` Kumar Gala
2013-09-12 18:04 ` Olof Johansson
2013-09-12 18:15 ` Kumar Gala
2013-09-12 18:20 ` Rob Herring
2013-09-12 18:46 ` Olof Johansson
2013-09-12 19:26 ` Kumar Gala
2013-09-12 22:47 ` David Brown
2013-09-13 2:05 ` Kumar Gala
2013-09-16 18:28 ` Rohit Vaswani
2013-09-16 18:46 ` Kumar Gala
2013-09-16 18:50 ` Olof Johansson
2013-09-17 15:52 ` Kumar Gala [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=0618B96B-2F6C-4D67-9D32-0B74E898496F@codeaurora.org \
--to=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).