From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>,
Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: [DTC PATCH] Add support for decimal, octal and binary based cell values.
Date: Fri, 16 Feb 2007 09:14:12 +1100 [thread overview]
Message-ID: <20070215221412.GB19126@localhost.localdomain> (raw)
In-Reply-To: <DFBB231C-47A7-46B9-9D56-B651536B2C5A@kernel.crashing.org>
On Thu, Feb 15, 2007 at 12:41:50PM -0600, Kumar Gala wrote:
>
> On Feb 15, 2007, at 11:49 AM, Yoder Stuart-B08248 wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: linuxppc-dev-bounces+b08248=freescale.com@ozlabs.org
> >> [mailto:linuxppc-dev-bounces+b08248=freescale.com@ozlabs.org]
> >> On Behalf Of Kumar Gala
> > [snip]
> >>> New syntax d#, b#, o# and h# allow for an explicit prefix
> >>> on cell values to specify their base. Eg: <d# 123>
> >>>
> >>> Signed-off-by: Jon Loeliger <jdl@freescale.com>
> >>>
> >>> ---
> >>
> >> What are people's thoughts on supporting '0x' and '0X' for hex?
> >
> > Are you saying allow d#1234, h#5678, and 0x5678? Or use 0x instead
> > of h#?
>
> I'm saying in addition to supporting the d#, h# notation.
>
> The reason I'm suggesting support '0x' is its pretty natural from C
> and I know there have been a number of times when I forget that all
> int constants in .dts are hex.
I'd prefer not to do this. I agree it would be nice in some ways, but
I'm worried that if people see 0x all over the place, they'll assume
that things without an 0x are decimal, which they can't be for
compatibility.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-02-15 22:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 17:13 [DTC PATCH] Add support for decimal, octal and binary based cell values Jon Loeliger
2007-02-15 17:30 ` Kumar Gala
2007-02-15 17:49 ` Yoder Stuart-B08248
2007-02-15 18:41 ` Kumar Gala
2007-02-15 22:14 ` David Gibson [this message]
2007-02-16 0:04 ` Kumar Gala
2007-02-16 10:23 ` Segher Boessenkool
2007-02-15 17:45 ` Yoder Stuart-B08248
2007-02-15 18:00 ` Olof Johansson
2007-02-15 18:00 ` Yoder Stuart-B08248
2007-02-15 18:02 ` Scott Wood
2007-02-15 18:05 ` Jon Loeliger
2007-02-15 18:10 ` Yoder Stuart-B08248
2007-02-15 21:44 ` Benjamin Herrenschmidt
2007-02-15 22:12 ` David Gibson
2007-02-15 22:59 ` Jon Loeliger
2007-02-15 22:19 ` David Gibson
2007-02-15 23:43 ` Jon Loeliger
2007-02-15 22:33 ` Dan Malek
2007-02-15 22:57 ` David Gibson
2007-02-15 23:37 ` Dan Malek
2007-02-16 0:09 ` David Gibson
2007-02-16 10:21 ` Segher Boessenkool
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=20070215221412.GB19126@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stuart.yoder@freescale.com \
/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).