linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: wmb@firmworks.com, linuxppc-dev@ozlabs.org,
	sparclinux@vger.kernel.org, devicetree-discuss@ozlabs.org,
	scottwood@freescale.com
Subject: Re: [PATCH 0/3]: Sparc OF I2C support.
Date: Thu, 21 Aug 2008 21:37:47 -0700 (PDT)	[thread overview]
Message-ID: <20080821.213747.159824681.davem@davemloft.net> (raw)
In-Reply-To: <fa686aa40808212134l1e226845q41831ee567bb1a2@mail.gmail.com>

From: "Grant Likely" <grant.likely@secretlab.ca>
Date: Thu, 21 Aug 2008 22:34:31 -0600

> On Thu, Aug 21, 2008 at 10:30 PM, Grant Likely
> <grant.likely@secretlab.ca> wrote:
> > On Thu, Aug 21, 2008 at 10:29 PM, Mitch Bradley <wmb@firmworks.com> wrote:
> >> Hi, I wrote most of 1275.
> >>
> >> Mitch Bradley  (wmb@firmworks.com)
> >
> > Hi Mitch,
> >
> > What is your suggestion.  Where should we be discussing new device
> > tree bindings?  Whether it be real Open Firmware, or flattened device
> > tree, or something in between
> 
> ...and along those lines: is there a place for documenting new
> bindings?  Lacking anything better, those of us in PowerPC-Linux-land
> have been adding documentation to Documentation/powerpc/dts-bindings/*
> in the Linux kernel tree.

In a discussion I am having with Greg Onufer, David K. and Tayfun
at Sun, Greg said the some of the newer binding documents are
being published on the opensolaris site, and he is trying to
get some of the older cases (like this I2C one) published there
too.

  reply	other threads:[~2008-08-22  4:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  7:10 [PATCH 0/3]: Sparc OF I2C support David Miller
2008-08-21 16:32 ` Scott Wood
2008-08-21 21:21   ` David Miller
2008-08-21 21:35     ` Scott Wood
2008-08-21 21:45       ` David Miller
2008-08-21 22:05         ` Benjamin Herrenschmidt
2008-08-21 22:27           ` David Miller
2008-08-21 22:38             ` Benjamin Herrenschmidt
2008-08-21 22:05       ` Benjamin Herrenschmidt
2008-08-21 22:28         ` David Miller
2008-08-21 22:39           ` Benjamin Herrenschmidt
2008-08-21 23:14       ` Grant Likely
2008-08-21 23:32         ` David Miller
2008-08-22  1:15           ` Josh Boyer
2008-08-22  3:53             ` David Miller
2008-08-22  4:18               ` Grant Likely
2008-08-22  4:22                 ` David Miller
2008-08-22  4:29                   ` Mitch Bradley
2008-08-22  4:30                     ` Grant Likely
2008-08-22  4:34                       ` Grant Likely
2008-08-22  4:37                         ` David Miller [this message]
2008-08-22  5:19                           ` Mitch Bradley
2008-08-22 16:00                             ` Yoder Stuart
2008-08-22 16:13                               ` Josh Boyer
2008-08-22 10:50               ` Josh Boyer
2008-08-22 11:06                 ` David Miller
2008-08-21 23:45         ` Jon Smirl
2008-08-22  2:33           ` Grant Likely
2008-08-22  2:39             ` Jon Smirl
2008-08-22 15:58               ` Scott Wood
2008-08-22 16:44               ` Grant Likely
2008-08-21 22:01   ` Benjamin Herrenschmidt
2008-08-21 21:53 ` Jon Smirl
2008-08-21 21:58   ` David Miller

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=20080821.213747.159824681.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=wmb@firmworks.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).