All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Becky Bruce <Becky.Bruce@freescale.com>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Interrupt mapping documentation
Date: Mon, 19 Jun 2006 18:03:46 -0500	[thread overview]
Message-ID: <E1FsSmY-0000Oz-P2@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 20 Jun 2006 00:22:02 +0200." <3E324A7E-388E-4917-B380-B0831A5F9D19@kernel.crashing.org>

So, like, the other day Segher Boessenkool mumbled:
> > Wow, you've been busy!  This mostly looks good to me - just a few
> > *minor* comments below. I've snipped out parts I'm not commenting on,
> > to shrink this email down.....
> 
> Yeah.  I've got some nits too, although mostly spelling.  Will get to
> those later, if I find the time :-)

BTW, Becky sent him an off-list correction for a series
of spelling and grammar related changes.  You might wait
for that... :-)


> Inheritance from the parent does not exist, in real OF.  Absence of
> #address-cells means "default to 2".  This needs to be fixed in DTC.
>
> [...]
>
> Just *require* #address-cells for everything with addressable sub-nodes,
> at least in DTC.  Doesn't cost much, and no confusion anymore.

Woot!  Send me a patch! :-)

jdl

  reply	other threads:[~2006-06-19 23:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18  2:45 [RFC] Interrupt mapping documentation Benjamin Herrenschmidt
2006-06-19 19:57 ` Becky Bruce
2006-06-19 22:22   ` Segher Boessenkool
2006-06-19 23:03     ` Jon Loeliger [this message]
2006-06-19 23:07       ` Segher Boessenkool
2006-06-19 23:14         ` Jon Loeliger
2006-06-19 23:17     ` Benjamin Herrenschmidt
2006-06-19 23:34       ` Segher Boessenkool
2006-06-20  0:23       ` Becky Bruce
2006-06-20  0:39         ` Segher Boessenkool
2006-06-20  3:06           ` Jon Loeliger
2006-06-20  1:18         ` Benjamin Herrenschmidt
2006-06-19 23:12   ` Benjamin Herrenschmidt

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=E1FsSmY-0000Oz-P2@jdl.com \
    --to=jdl@jdl.com \
    --cc=Becky.Bruce@freescale.com \
    --cc=linuxppc-dev@ozlabs.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 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.