From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lhms <lhms-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
"Luck, Tony" <tony.luck@intel.com>,
Hirokazu Takahashi <taka@valinux.co.jp>
Subject: Re: [Lhms-devel] Re: [PATCH] no buddy bitmap patch : for ia64 [2/2]
Date: Fri, 08 Oct 2004 09:43:40 +0900 [thread overview]
Message-ID: <4165E2BC.3070906@jp.fujitsu.com> (raw)
In-Reply-To: <1097163793.3625.47.camel@localhost>
Dave Hansen wrote:
> The real way to do this is to put it in a Kconfig file.
>
> something like:
>
> config HOLES_IN_ZONE
> bool
> depends on VIRTUAL_MEM_MAP
>
> right below where 'config VIRTUAL_MEM_MAP' is defined. That way, if any
> other architectures need it, they alter their Kconfig files instead of
> headers. Also, it leaves the possibility of having an arch-independent
> Kconfig file for memory-related options which I'd like to do in the
> future.
>
Ok, it looks better. I'll move it.
Updated version will be posted in a day.
Kame <kamezawa.hiroyu@jp.fujitsu.com>
WARNING: multiple messages have this Message-ID (diff)
From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lhms <lhms-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
"Luck, Tony" <tony.luck@intel.com>,
Hirokazu Takahashi <taka@valinux.co.jp>
Subject: Re: [Lhms-devel] Re: [PATCH] no buddy bitmap patch : for ia64 [2/2]
Date: Fri, 08 Oct 2004 09:43:40 +0900 [thread overview]
Message-ID: <4165E2BC.3070906@jp.fujitsu.com> (raw)
In-Reply-To: <1097163793.3625.47.camel@localhost>
Dave Hansen wrote:
> The real way to do this is to put it in a Kconfig file.
>
> something like:
>
> config HOLES_IN_ZONE
> bool
> depends on VIRTUAL_MEM_MAP
>
> right below where 'config VIRTUAL_MEM_MAP' is defined. That way, if any
> other architectures need it, they alter their Kconfig files instead of
> headers. Also, it leaves the possibility of having an arch-independent
> Kconfig file for memory-related options which I'd like to do in the
> future.
>
Ok, it looks better. I'll move it.
Updated version will be posted in a day.
Kame <kamezawa.hiroyu@jp.fujitsu.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-08 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 12:42 [PATCH] no buddy bitmap patch : for ia64 [2/2] Hiroyuki KAMEZAWA
2004-10-07 12:42 ` Hiroyuki KAMEZAWA
2004-10-07 15:43 ` Dave Hansen
2004-10-07 15:43 ` Dave Hansen
2004-10-08 0:43 ` Hiroyuki KAMEZAWA [this message]
2004-10-08 0:43 ` [Lhms-devel] " Hiroyuki KAMEZAWA
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=4165E2BC.3070906@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
--cc=tony.luck@intel.com \
--cc=wli@holomorphy.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.