From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org,
Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: #cpus property
Date: Tue, 27 Feb 2007 07:48:54 +0100 [thread overview]
Message-ID: <1172558934.11949.45.camel@localhost.localdomain> (raw)
In-Reply-To: <20070227021151.GB1861@localhost.localdomain>
On Tue, 2007-02-27 at 13:11 +1100, David Gibson wrote:
> On Tue, Feb 27, 2007 at 12:33:05AM +0100, Segher Boessenkool wrote:
> > > Anyone know the origin of the #cpus property that seems to be in most
> > > of
> > > the DTS files. It seems to be documented nowhere.
> >
> > It was there in the first DTS file to hit the kernel
> > source tree. Probably all others just copied that.
>
> That sounds likely. We should probably get rid of it, the kernel
> doesn't use it. BenH, Paulus, you can't see any use for this one?
Nope.
Ben.
prev parent reply other threads:[~2007-02-27 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 22:54 #cpus property Yoder Stuart-B08248
2007-02-26 23:33 ` Segher Boessenkool
2007-02-27 2:11 ` David Gibson
2007-02-27 6:48 ` Benjamin Herrenschmidt [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=1172558934.11949.45.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=stuart.yoder@freescale.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).