From: Paul Mackerras <paulus@samba.org>
To: will schmidt <will_schmidt@vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, anton@samba.org
Subject: Re: [PATCH][PPC64] lparcfg seq_file update
Date: Wed, 30 Jun 2004 19:57:18 +1000 [thread overview]
Message-ID: <16610.36478.725698.303353@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <40E1F6FC.3030405@vnet.ibm.com>
will schmidt writes:
> Hi All,
> This patch includes updates and cleanup for the PPC64 proc/lparcfg
> interface.
> - use seq_file's seq_printf for output
> - remove redundant e2a function. (use viopath.c's instead)
> - change to Kconfig to allow building as a module.
> - export required symbols from LparData.c
>
> Please apply. (or make constructive comments, as necessary.. :-) )
Could you take out the vpurr stuff please? I know that it is all
inside #ifdef CONFIG_PPC_VPURR, and there is currently no way for that
to be defined, but it would be cleaner without it.
The vpurr stuff in ameslab is a bit problematic at present since it
will interact badly with hotplug cpu, according to Anton. I think
the vpurr stuff could be done very simply with a couple of lines of
code in timer_interrupt.
Paul.
prev parent reply other threads:[~2004-06-30 11:36 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
2004-06-30 9:57 ` Paul Mackerras [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=16610.36478.725698.303353@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.