From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Segher Boessenkool" <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] [POWERPC] Make it blatently clear; 5200 device tree is not yet stable
Date: Sat, 13 Jan 2007 17:42:30 -0700 [thread overview]
Message-ID: <528646bc0701131642w5a57607aha4e64e8ec4dcaa2e@mail.gmail.com> (raw)
In-Reply-To: <84dba8e3e19d453c2961c4022ddb77de@kernel.crashing.org>
On 1/13/07, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > Please apply for 2.6.20. This is documentation only, but I don't want
> > to give people false assumptions about the stability of the 5200 device
> > tree bindings
>
> Good idea.
Thanks. :)
> > +********** DRAFT ***********
> > +* WARNING: Do not depend on definiton remaining static between
> > +* kernel versions. The 5200 device tree conventions are still in flux
> > +* and could change without notice. Keep an eye on the linuxppc-dev
> > +* mailing list for more details
> > +*
> > +* Hopefully by 2.6.21 it will be stable. ---gcl, Jan 13, 2007
> > +********** DRAFT ***********
>
> But could you please rephrase in a way that doesn't suggest
> the *kernel* defines what the device bindings are? They are
> only documented in the kernel tree right now, sure, but that's
> not the same thing ;-)
Gah! Good point. I do *not* what to go down the "this is for Linux
only" path. In fact, perhaps I should start looking for a better
place to host this stuff. Maybe freescale or power.org?
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-01-14 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 23:58 [PATCH] [POWERPC] Make it blatently clear; 5200 device tree is not yet stable grant.likely
2007-01-14 0:31 ` Segher Boessenkool
2007-01-14 0:42 ` Grant Likely [this message]
2007-01-14 0:53 ` 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=528646bc0701131642w5a57607aha4e64e8ec4dcaa2e@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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