From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [v3 0/6] ARM: tegra: convert device tree files to use CLK defines
Date: Tue, 19 Feb 2013 10:08:16 -0700 [thread overview]
Message-ID: <5123B180.5060106@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ0Bkk0Ock5_WQxsni+qNMQnWURrLLqfNFVfKczN6OgLoQ@mail.gmail.com>
On 02/17/2013 03:20 PM, Simon Glass wrote:
> Hi Hiroshi,
>
> On Fri, Feb 15, 2013 at 12:43 AM, Hiroshi Doyu <hdoyu@nvidia•com> wrote:
>> Hi,
>>
>> With new dtc+cpp feature, we could get rid of magic numbers in dts*
>> files. This patch replaces CLK IDs.
...
> I wonder what sort of error message do you get when you make a mistake
> in the .dts or one of the .dtsi includes? If cpp is handling the
> including, does dtc just see a single file,
It is.
> in which case are the line
> numbers printed with each error not much use? Or does dtc handle the
> #line directives?
cpp does generate #line directives, which dtc does know how to
interpret, so this should all work just fine. IIRC, I did test out this
aspect when adding #line support to dtc.
prev parent reply other threads:[~2013-02-19 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 8:43 [v3 0/6] ARM: tegra: convert device tree files to use CLK defines Hiroshi Doyu
[not found] ` <1360917814-27236-3-git-send-email-hdoyu@nvidia.com>
2013-02-15 16:41 ` [v3 2/6] ARM: tegra20: " Stephen Warren
[not found] ` <1360917814-27236-6-git-send-email-hdoyu@nvidia.com>
2013-02-15 16:43 ` [v3 5/6] ARM: tegra114: create a DT header defining CLK IDs Stephen Warren
2013-02-17 22:05 ` [v3 0/6] ARM: tegra: convert device tree files to use CLK defines Rob Landley
2013-02-19 17:10 ` Stephen Warren
2013-02-23 19:51 ` Rob Landley
2013-02-23 23:52 ` Stephen Warren
2013-02-17 22:20 ` Simon Glass
2013-02-19 17:08 ` Stephen Warren [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=5123B180.5060106@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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