From: Kumar Gala <galak@codeaurora.org>
To: Olof Johansson <olof@lixom.net>
Cc: David Brown <davidb@codeaurora.org>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Russell King <linux@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org list"
<linux-kernel@vger.kernel.org>,
Rohit Vaswani <rvaswani@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: msm: Move msm devicetrees under a Qualcomm dir
Date: Thu, 12 Sep 2013 12:55:36 -0500 [thread overview]
Message-ID: <3E38F48E-EE41-4564-84A1-36CF07B08811@codeaurora.org> (raw)
In-Reply-To: <CAOesGMhfdvyJ_2AA2e8iO_2e=q7KgpyNbcriPKFw-RLormG6bA@mail.gmail.com>
On Sep 12, 2013, at 12:06 PM, Olof Johansson wrote:
> On Thu, Sep 12, 2013 at 9:53 AM, Kumar Gala <galak@codeaurora.org> wrote:
>>
>> On Sep 12, 2013, at 11:46 AM, Olof Johansson wrote:
>>
>>> On Thu, Sep 12, 2013 at 9:37 AM, Kumar Gala <galak@codeaurora.org> wrote:
>>>> Use the Qualcomm vendor prefix (qcom) as the directory name for
>>>> Qualcomm MSM devicetrees going forward.
>>>>
>>>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>>>
>>> Let's not move just one platform like this. If we are to do this, we
>>> should move everything, and that will be really painful and needs to
>>> be done in a controlled manner, probably scripted and right before a
>>> -rc1 or such.
>>
>>
>> Than I suggest we deal with it when we pull the device trees out of the kernel tree.
>>
>> As such, I'd tell Rohit to go forward with the file being named apq8074-dragonboard.dtb for the time being.
>
> My original request to please use a common prefix for your product
> families stands. Please prefix with msm-*, or if you have to, qcom-*
> instead, since you guys can't seem to make your mind up on standard
> prefixes (msm, apq, etc).
This is silly, I dont see the reason to go with qcom-apq<SOC>-<BOARD>.dts and than in the future drop qcom- when we mostly likely shift to a dir structure. As engineers we are all too aware of the lack of sanity in marketing names, but its what we have so we have to live with it.
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-09-12 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 16:37 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 [this message]
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
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=3E38F48E-EE41-4564-84A1-36CF07B08811@codeaurora.org \
--to=galak@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rvaswani@codeaurora.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®