From: Dave Hansen <haveblue@us.ibm.com>
To: will schmidt <will_schmidt@vnet.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Anton Blanchard <anton@samba.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH][PPC64] lparcfg seq_file update
Date: Tue, 29 Jun 2004 16:58:11 -0700 [thread overview]
Message-ID: <1088553490.26704.43.camel@nighthawk> (raw)
In-Reply-To: <40E1F6FC.3030405@vnet.ibm.com>
On Tue, 2004-06-29 at 16:10, will schmidt wrote:
> Hi All,
> This patch includes updates and cleanup for the PPC64 proc/lparcfg
> interface.
I think your mailer whitespace-munged the patch.
Also, why do you need this information:
+ seq_printf(m, "partition_active_processors=%d\n",
+ (int) lparcfg_count_active_processors());
Doesn't that duplicate information already exported in /proc/cpuinfo and
/sys/devices/system/cpu?
-- Dave
next prev parent reply other threads:[~2004-06-29 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 23:10 [PATCH][PPC64] lparcfg seq_file update will schmidt
2004-06-29 23:58 ` Dave Hansen [this message]
2004-06-30 9:57 ` Paul Mackerras
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=1088553490.26704.43.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=will_schmidt@vnet.ibm.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