From: Paul Mundt <lethal@linux-sh.org>
To: Shaohui Zheng <shaohui.zheng@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [v2,5/8] NUMA Hotplug emulator
Date: Tue, 16 Nov 2010 14:47:47 +0900 [thread overview]
Message-ID: <20101116054747.GA1064@linux-sh.org> (raw)
In-Reply-To: <20101116041330.GA20694@shaohui>
On Tue, Nov 16, 2010 at 12:13:30PM +0800, Shaohui Zheng wrote:
> >This looks like an incredibly painful interface. How about scrapping all
> >of this _emu() mess and just reworking the register_cpu() interface?
> > Something like:
>
> hi, Paul
> I saw your reply on patchwork.kernel.org, but I did not find your email
> in my mailbox, you might forget to cc to me.
>
Then fix your mailer. You are presently forcing Mail-Followup-To to the
list, which in turn is dropping you from the cc on a group reply.
> I think that your register_cpu_node interface seems good, but this will
> remove the interface register_cpu. it is not the original purpose of the
> emulator, we want to emulate the oringal process, but we did not want to change
> the old interface, that is a rule.
>
Wait, what? How does my patch remove register_cpu()? It does no such
thing, all it does is add a supplemental register_cpu_node() for you to
call in to, without needing to carry any of the _emu() damage around. The
old interface has not been modified in any way whatsoever.
next prev parent reply other threads:[~2010-11-16 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 4:13 [v2,5/8] NUMA Hotplug emulator Shaohui Zheng
2010-11-16 5:47 ` Paul Mundt [this message]
[not found] ` <A24AE1FFE7AEC5489F83450EE98351BF27D53BCC36@shsmsx502.ccr.corp.intel.com>
2010-11-16 5:05 ` Shaohui Zheng
2010-11-16 7:04 ` Paul Mundt
2010-11-16 6:21 ` Shaohui Zheng
-- strict thread matches above, loose matches on Subject: below --
2010-11-13 6:16 Shaohui Zheng
2010-11-15 6:58 ` Paul Mundt
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=20101116054747.GA1064@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohui.zheng@intel.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