From: Rajendra Nayak <rnayak@codeaurora.org>
To: Bryan Huntsman <bryanh@codeaurora.org>, agross@codeaurora.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
sboyd@codeaurora.org
Subject: Re: [PATCH v2] arm64: dts: qcom: Add apq8096 dragonboard dts skeletons
Date: Wed, 02 Dec 2015 07:59:01 +0530 [thread overview]
Message-ID: <565E576D.9010501@codeaurora.org> (raw)
In-Reply-To: <565E1146.7050207@codeaurora.org>
On 12/02/2015 02:59 AM, Bryan Huntsman wrote:
> On 12/01/2015 08:11 AM, Rajendra Nayak wrote:
>> Add new dtsi and dts files for the apq8096 dragonboards with just
>> a serial device used as debug console
>>
>> While at it, also rearrange the Makefile so we have one dtb per line
>> so as to be consistent with whats done on other platforms.
>>
>> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
>> ---
>> arch/arm64/boot/dts/qcom/Makefile | 4 ++-
>> arch/arm64/boot/dts/qcom/apq8096-dragonboard.dts | 21 ++++++++++++++++
>> arch/arm64/boot/dts/qcom/apq8096-dragonboard.dtsi | 30 +++++++++++++++++++++++
>> 3 files changed, 54 insertions(+), 1 deletion(-)
>> create mode 100644 arch/arm64/boot/dts/qcom/apq8096-dragonboard.dts
>> create mode 100644 arch/arm64/boot/dts/qcom/apq8096-dragonboard.dtsi
>
> One problem. The board you have is not called a dragonboard. Let's
> check with the marketing folks on what they're calling it now. We need
> to explicitly avoid using dragonboard here as that name applies to a
> different class of products. Thanks.
Thanks Bryan, I'll update with the new board name.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2015-12-02 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:11 [PATCH v2] arm64: dts: qcom: Add apq8096 dragonboard dts skeletons Rajendra Nayak
2015-12-01 21:29 ` Bryan Huntsman
2015-12-02 2:29 ` Rajendra Nayak [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=565E576D.9010501@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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).