From: Rohit Vaswani <rvaswani@codeaurora.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: David Brown <davidb@codeaurora.org>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
Russell King <linux@arm.linux.org.uk>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RESEND PATCH 1/2] ARM: msm: Add support for MSM8974
Date: Thu, 01 Aug 2013 20:36:38 -0700 [thread overview]
Message-ID: <51FB2946.2050503@codeaurora.org> (raw)
In-Reply-To: <51FB1987.3060806@wwwdotorg.org>
On 8/1/2013 7:29 PM, Stephen Warren wrote:
> On 08/01/2013 07:23 PM, Rohit Vaswani wrote:
>> This patch adds basic board support for MSM8974 which
>> belongs to the Snapdragon 800 family.
>> For now, just support a basic machine with device tree.
>> arch/arm/boot/dts/msm8974.dts | 26 ++++++++++++++++++++++++++
> That's odd. If this is support for an SoC, why not a *.dtsi file rather
> than *.dts?
I am not sure why I would need a dtsi if I am just adding the 1 file for
the SoC support ?
Thanks,
Rohit Vaswani
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-08-02 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 1:23 [RESEND PATCH 1/2] ARM: msm: Add support for MSM8974 Rohit Vaswani
2013-08-02 1:23 ` [RESEND PATCH 2/2] defconfig: msm_defconfig: Enable CONFIG_ARCH_MSM8974 Rohit Vaswani
2013-08-02 2:29 ` [RESEND PATCH 1/2] ARM: msm: Add support for MSM8974 Stephen Warren
2013-08-02 3:36 ` Rohit Vaswani [this message]
2013-08-02 4:21 ` David Brown
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=51FB2946.2050503@codeaurora.org \
--to=rvaswani@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dwalker@fifo99.com \
--cc=ian.campbell@citrix.com \
--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=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--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;
as well as URLs for NNTP newsgroup(s).