From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>
Subject: Re: [PATCH 4/4] DTC: Begin the path to sane literals and expressions.
Date: Tue, 23 Oct 2007 02:57:51 +0200 [thread overview]
Message-ID: <a2dc4530efef0e434975b135e3d6ed35@kernel.crashing.org> (raw)
In-Reply-To: <20071023003309.GE31839@localhost.localdomain>
>>>> Property names have been limited to start with
>>>> characters from the set [a-zA-Z,._#?]. That is, the
>>>> digits and the expression symbols have been removed.
>>>
>>> This cannot work; many property names start with a digit,
>>> for example.
>>
>> Are any of those property names in use in any
>> of our DTS files or b-w-o.txt? Not really, no.
>> In fact, with this lexical change, all of our
>> DTS files still produce byte-identical results.
>>
>> I really think this is one of those areas where
>> we may need to stray from the other guideline.
>>
>> Is there a compelling reason somewhere? Really?
>
> We may have deprecated te '64-bit' and '32-64-bridge' properties in
> cpu nodes for the flattened tree, but it already exists in a great
> number of Apple and IBM trees.
Huh? "64-bit" isn't deprecated I hope, just the "32-bit" thing
(that never was defined) is.
> It would be poor form for dtc to choke on these trees.
Yah. Small incompatibilities add up :-(
Segher
prev parent reply other threads:[~2007-10-23 0:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 17:43 [PATCH 4/4] DTC: Begin the path to sane literals and expressions Jon Loeliger
2007-10-20 8:47 ` David Gibson
2007-10-21 5:32 ` Segher Boessenkool
2007-10-22 0:37 ` David Gibson
2007-10-25 18:24 ` Jon Loeliger
2007-10-26 1:28 ` David Gibson
2007-10-26 13:07 ` Jon Loeliger
2007-10-26 14:03 ` David Gibson
2007-10-21 5:30 ` Segher Boessenkool
2007-10-22 0:51 ` David Gibson
2007-10-22 12:36 ` Jon Loeliger
2007-10-23 0:33 ` David Gibson
2007-10-23 0:57 ` Segher Boessenkool [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=a2dc4530efef0e434975b135e3d6ed35@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.