From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, y-goto@jp.fujitsu.com
Subject: Re: [PATCH] refine for_each_pgdat() [1/4] refine for_each_pgdat
Date: Thu, 23 Feb 2006 09:20:16 +0900 [thread overview]
Message-ID: <43FCFFC0.1050405@jp.fujitsu.com> (raw)
In-Reply-To: <20060222145256.7b84f444.akpm@osdl.org>
Andrew Morton wrote:
> It's confusing and asymmetric. If you have time, it would be nice to later
> remove for_each_pgdat() and for_each_cpu() from the kernel altogether, use
> for_each_online_cpu(), for_each_possible_cpu(), for_each_online_node(),
> for_each_possible_node().
>
Okay, I'll rewrite my patch and post new one which represents what you mention.
BTW, I noticed refine-for_each_pgdat-remove-pgdat-sorting.patch
contains bug. (caller of ia64's insert_pgdat() is not removed...)
so please drop them :(, I'll post new ones to next -mm (with enough test...).
Thanks,
-- Kame
next prev parent reply other threads:[~2006-02-23 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 11:04 [PATCH] refine for_each_pgdat() [1/4] refine for_each_pgdat KAMEZAWA Hiroyuki
2006-02-22 22:52 ` Andrew Morton
2006-02-23 0:20 ` KAMEZAWA Hiroyuki [this message]
2006-02-23 0:29 ` Andrew Morton
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=43FCFFC0.1050405@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.fujitsu.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).