From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Yoder Stuart-B08248" <stuart.yoder@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: #cpus property
Date: Tue, 27 Feb 2007 00:33:05 +0100 [thread overview]
Message-ID: <213956050aa89759f6329f518e46f42b@kernel.crashing.org> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA302AA0181@az33exm25.fsl.freescale.net>
> 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.
> It's obviously describing how many cpus exist. However, greping the
> kernel source turns up no references to it.
>
> Is it supposed to be required for all cpus nodes? Are there plans to
> actually use it?
It is utterly redundant as simply looking at the number
of child nodes of /cpus/ will tell you the same thing.
Well *hopefully* the same thing, heh.
Segher
next prev parent reply other threads:[~2007-02-26 23:33 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 [this message]
2007-02-27 2:11 ` David Gibson
2007-02-27 6:48 ` 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=213956050aa89759f6329f518e46f42b@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--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).