From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org, Stefan Roese <sr@denx•de>
Subject: Re: [PATCH] [POWERPC] 4xx: Add aliases node to 4xx dts files
Date: Mon, 17 Dec 2007 07:46:48 -0600 [thread overview]
Message-ID: <E1J4GIy-0006Xp-RT@jdl.com> (raw)
In-Reply-To: Your message of "Mon, 17 Dec 2007 09:33:42 +1100." <20071216223342.GD26307@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> On Sun, Dec 16, 2007 at 07:10:02PM +0100, Segher Boessenkool wrote:
> >
> > Hopefully some version that stores path strings in the properties
> > in /aliases, and not phandles.
Yes.
> > Or does that current version of DTC
> > do that correctly already, and just has an inconvenient source
> > syntax?
Feh. If there is an "inconvenient source syntax", or any other
annoying irregularity, please, by all means, suggest improvements
and offer patches!
> I don't think anyone's actually gone and generated phandles in
> /aliases, although it was suggested early on. The syntax is
> foo = < &bar >;
> to generate a phandle and
> foo = &bar;
> to generate a path.
>
> I was a bit worried about confusion between these forms, but at least
> Kumar and myself came up with this syntax independently, which
> suggests it's not too surprising to most people, and no-one had any
> other suggestions.
To be a bit more complete, Kumar and I discussed this as well.
jdl
next prev parent reply other threads:[~2007-12-17 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 7:55 [PATCH] [POWERPC] 4xx: Add aliases node to 4xx dts files Stefan Roese
2007-12-16 6:19 ` David Gibson
2007-12-16 14:58 ` Josh Boyer
2007-12-16 18:10 ` Segher Boessenkool
2007-12-16 18:45 ` Josh Boyer
2007-12-16 22:33 ` David Gibson
2007-12-16 22:44 ` Segher Boessenkool
2007-12-17 0:00 ` David Gibson
2007-12-17 13:46 ` Jon Loeliger [this message]
2007-12-16 22:30 ` David Gibson
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=E1J4GIy-0006Xp-RT@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sr@denx$(echo .)de \
/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