From: Jon Loeliger <jdl@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Jon Loeliger <jdl@jdl.com>,
"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: DTC/dts modifications
Date: Mon, 01 May 2006 14:33:32 -0500 [thread overview]
Message-ID: <1146512012.24239.28.camel@cashmere.sps.mot.com> (raw)
In-Reply-To: <5CA113BC-1614-4551-87E5-6926E14C2225@kernel.crashing.org>
On Sat, 2006-04-29 at 11:00, Kumar Gala wrote:
> All,
>
> What evilness would it be to change the use of '#' in the .dts format
> to some other character like '$' or '%'.
Uh, use of '#' for what? Current comment style is
either C or C++, ie, /* ... */ or //.
> The problem is the use of
> '#' prevents use from using cpp which would make some aspects of
> building up .dts for boards far more useful.
I think to get CPP to be usable, it will need to handle
the # emitted line-location markers, "# <line> <file> <level>".
> We can easily provide a one line script to convert people's .dts to
> the new format.
I don't think there is a conversion necessary yet.
Did I miss something here?
Thanks,
jdl
next prev parent reply other threads:[~2006-05-01 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 16:00 DTC/dts modifications Kumar Gala
2006-05-01 19:33 ` Jon Loeliger [this message]
2006-05-01 19:39 ` Kumar Gala
2006-05-01 19:45 ` Jon Loeliger
2006-05-01 19:52 ` Kumar Gala
2006-05-01 20:07 ` Kim Phillips
2006-05-01 20:28 ` Kumar Gala
2006-05-01 21:26 ` Segher Boessenkool
2006-05-01 22:00 ` Gabriel Paubert
2006-05-01 22:59 ` Andreas Schwab
2006-05-01 23:34 ` Benjamin Herrenschmidt
2006-05-02 0:17 ` Segher Boessenkool
2006-05-01 22:14 ` Paul Mackerras
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=1146512012.24239.28.camel@cashmere.sps.mot.com \
--to=jdl@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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).