From: Stuart Yoder <stuyoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linuxppc-dev list
<linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: Re: [RFC] Clock binding
Date: Fri, 28 Aug 2009 13:05:22 -0500 [thread overview]
Message-ID: <955e48b80908281105q60c057e8pfc16213f17da9138@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40908280906w7953017ek44ee498d57e0a642-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> Lets *not* do it on power.org. I'd like to see the bindings used by
> more than just powerpc people, and power.org might become a bit of a
> mental barrier for non-powerpc folks. kernel.org would be a good
> host. So would ozlabs or infradead. Or I'd be happy to maintain one
> on secretlab.
I think broadening it beyond power.org is good. Along those lines I'd prefer
not having this on kernel.org, as device trees are not Linux-centric. There
are other OS vendors I've interacted with that I'd like to see use device trees
and separating it from Linux may be better IMO.
We could also create a new domain like "devicetree.org" (?)..but it still
would nee a host.
Stuart
next prev parent reply other threads:[~2009-08-28 18:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 4:21 [RFC] Clock binding Benjamin Herrenschmidt
2009-08-18 7:45 ` [RFC/PATCH] Clock binding prototype implementation Benjamin Herrenschmidt
2009-08-27 4:09 ` [RFC] Clock binding Benjamin Herrenschmidt
2009-08-27 5:20 ` Grant Likely
2009-08-27 21:11 ` Mitch Bradley
[not found] ` <4A96F69A.5050003-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-08-27 22:18 ` Benjamin Herrenschmidt
2009-08-27 22:28 ` Mitch Bradley
2009-08-27 22:45 ` Mitch Bradley
[not found] ` <4A970C85.8090703-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-08-28 0:51 ` Benjamin Herrenschmidt
2009-08-28 2:36 ` Mitch Bradley
[not found] ` <4A974295.9020504-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-08-28 2:43 ` Benjamin Herrenschmidt
2009-08-28 2:53 ` Michael Ellerman
2009-08-28 10:58 ` Josh Boyer
[not found] ` <20090828105837.GC25303-jnIq6iUNB1CO8iYQgJmm/0EOCMrvLtNR@public.gmane.org>
2009-08-28 11:23 ` David Gibson
[not found] ` <20090828112322.GA16192-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2009-08-28 22:28 ` Benjamin Herrenschmidt
2009-08-28 12:16 ` Stuart Yoder
2009-08-28 16:06 ` Grant Likely
[not found] ` <fa686aa40908280906w7953017ek44ee498d57e0a642-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-28 18:05 ` Stuart Yoder [this message]
2009-08-28 18:23 ` M. Warner Losh
[not found] ` <955e48b80908281105q60c057e8pfc16213f17da9138-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-28 20:09 ` Grant Likely
2009-08-31 17:49 ` Stuart Yoder
2009-08-28 18:12 ` Mitch Bradley
2009-08-28 18:24 ` Rafal Jaworowski
[not found] ` <B7829AEE-B751-403D-9A16-CFE1A4E0FAB0-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
2009-08-28 22:33 ` Benjamin Herrenschmidt
2009-08-28 16:37 ` Grant Likely
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=955e48b80908281105q60c057e8pfc16213f17da9138@mail.gmail.com \
--to=stuyoder-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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