From: David Howells <dhowells@redhat.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@osdl.org, davej@codemonkey.org.uk, tony.luck@intel.com,
linux-mm@kvack.org, ak@suse.de, bob.picco@hp.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 6/6] Account for memmap and optionally the kernel image as holes
Date: Mon, 10 Jul 2006 12:30:55 +0100 [thread overview]
Message-ID: <7220.1152531055@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060708111243.28664.74956.sendpatchset@skynet.skynet.ie>
Mel Gorman <mel@csn.ul.ie> wrote:
> +unsigned long __initdata dma_reserve;
Should this be static? Or should it be predeclared in a header file
somewhere?
David
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-07-10 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 11:10 [PATCH 0/6] Sizing zones and holes in an architecture independent manner V8 Mel Gorman
2006-07-08 11:11 ` [PATCH 1/6] Introduce mechanism for registering active regions of memory Mel Gorman
2006-07-08 11:11 ` [PATCH 2/6] Have Power use add_active_range() and free_area_init_nodes() Mel Gorman
2006-07-08 11:11 ` [PATCH 3/6] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-07-08 11:12 ` [PATCH 4/6] Have x86_64 " Mel Gorman
2006-07-08 11:12 ` [PATCH 5/6] Have ia64 " Mel Gorman
2006-07-08 11:12 ` [PATCH 6/6] Account for memmap and optionally the kernel image as holes Mel Gorman
2006-07-08 11:42 ` [PATCH 0/6] Sizing zones and holes in an architecture independent manner V8 Heiko Carstens
2006-07-09 15:32 ` Mel Gorman
2006-07-10 11:30 ` David Howells [this message]
2006-07-10 15:31 ` [PATCH 6/6] Account for memmap and optionally the kernel image as holes Mel Gorman
2006-08-21 13:45 [PATCH 0/6] Sizing zones and holes in an architecture independent manner V9 Mel Gorman
2006-08-21 13:47 ` [PATCH 6/6] Account for memmap and optionally the kernel image as holes Mel Gorman
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=7220.1152531055@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=tony.luck@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