From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 18/21] [POWERPC] bamboo: remove bogus "ranges" property in EBC node
Date: Fri, 21 Dec 2007 16:08:45 -0600 [thread overview]
Message-ID: <20071221160845.331f35f6@zod.rchland.ibm.com> (raw)
In-Reply-To: <1198271815.6737.4.camel@pasglop>
On Sat, 22 Dec 2007 08:16:55 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> On Fri, 2007-12-21 at 06:09 -0600, Josh Boyer wrote:
> > On Fri, 21 Dec 2007 15:39:35 +1100
> > Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> >
> > > This removes a bogus empty "ranges" property in the EBC device node
> > > of the Bamboo board device-tree.
> > >
> > > The "ranges" property will be created by the boot wrapper, there is
> > > no need to have an empty property there, and that causes recent
> > > dtc to complain.
> >
> > The wrapper doesn't do anything with EBC for bamboo because the EBC
> > stuff is a nightmare on this board. The patch can stand, but I'll
> > fixup the comments in the changelog.
>
> The wrapper could still create ranges for the chip select settings no ?
It could. It doesn't though. Perhaps our interpretation of "will be
created" differed.
> In any case, empty "ranges" is bogus.
Correct. Which is why I said I'd just edit the changelog :).
josh
prev parent reply other threads:[~2007-12-21 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 4:39 [PATCH 18/21] [POWERPC] bamboo: remove bogus "ranges" property in EBC node Benjamin Herrenschmidt
2007-12-21 12:09 ` Josh Boyer
2007-12-21 21:16 ` Benjamin Herrenschmidt
2007-12-21 22:08 ` Josh Boyer [this message]
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=20071221160845.331f35f6@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).