linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	David Gibson <dgibson@ozlabs.org>
Subject: Re: [PATCH] powerpc: #address-cells & #size-cells properties not inherited
Date: Thu, 3 Jan 2008 10:01:31 -0600	[thread overview]
Message-ID: <20080103100131.5b1c64b8@zod.rchland.ibm.com> (raw)
In-Reply-To: <20080103153256.GA18716@mag.az.mvista.com>

On Thu, 3 Jan 2008 08:32:56 -0700
"Mark A. Greer" <mgreer@mvista.com> wrote:

> On Wed, Jan 02, 2008 at 07:46:40PM -0600, Josh Boyer wrote:
> > On Wed, 2 Jan 2008 17:07:50 -0700
> > "Mark A. Greer" <mgreer@mvista.com> wrote:
> > 
> > > From: Mark A. Greer <mgreer@mvista.com>
> > > 
> > > Fix error in booting-without-of.txt that indicates that a node can inherit
> > > its #address-cells and #size-cells definitions from its parent's parent.
> > > This is not correct and the latest dtc enforces it.
> > 
> > I'm lazy so I haven't checked myself, but by "latest dtc" does that
> > mean the DTC that's in the kernel now?
> > 
> > Things are going to be fun when we start saying generic things like
> > "latest DTC".  And when upstream DTC gets new features or enforcements,
> > we'll have to have all the in-kernel DTS files patched up when that
> > version of DTC gets merged in-kernel.  Just something to keep in mind
> > as we move along.
> 
> Yeah, I thought about that last night, actually.
> I think I'll just change that sentence to "This is not correct."
> 
> Avoid the issue :)

Lazy!  I like it ;)

josh

  reply	other threads:[~2008-01-03 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  0:07 [PATCH] powerpc: #address-cells & #size-cells properties not inherited Mark A. Greer
2008-01-03  1:46 ` Josh Boyer
2008-01-03 15:32   ` Mark A. Greer
2008-01-03 16:01     ` Josh Boyer [this message]
2008-01-03 15:40   ` [PATCH v2] " Mark A. Greer
2008-01-03  9:46 ` [PATCH] " 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=20080103100131.5b1c64b8@zod.rchland.ibm.com \
    --to=jwboyer@gmail.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=dgibson@ozlabs.org \
    --cc=mgreer@mvista.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).