Re: [PATCH 6/6] Account for memmap and optionally the kernel image as holes | linuxppc-dev | Ratatoskr

[PATCH 0/6] Sizing zones and holes in an architecture independent manner V8 · Mel Gorman <hidden> · 2006-07-08
[PATCH 1/6] Introduce mechanism for registering active regions of memory · Mel Gorman <hidden> · 2006-07-08
[PATCH 2/6] Have Power use add_active_range() and free_area_init_nodes() · Mel Gorman <hidden> · 2006-07-08
[PATCH 3/6] Have x86 use add_active_range() and free_area_init_nodes · Mel Gorman <hidden> · 2006-07-08
[PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes · Mel Gorman <hidden> · 2006-07-08
[PATCH 5/6] Have ia64 use add_active_range() and free_area_init_nodes · Mel Gorman <hidden> · 2006-07-08
[PATCH 6/6] Account for memmap and optionally the kernel image as holes · Mel Gorman <hidden> · 2006-07-08
Re: [PATCH 6/6] Account for memmap and optionally the kernel image as holes · David Howells <dhowells@redhat.com> · 2006-07-10
Re: [PATCH 6/6] Account for memmap and optionally the kernel image as holes · Mel Gorman <hidden> · 2006-07-10
Re: [PATCH 0/6] Sizing zones and holes in an architecture independent manner V8 · Heiko Carstens <hidden> · 2006-07-08
Re: [PATCH 0/6] Sizing zones and holes in an architecture independent manner V8 · Mel Gorman <hidden> · 2006-07-09

Re: [PATCH 6/6] Account for memmap and optionally the kernel image as holes

From: David Howells <dhowells@redhat.com>
Date: 2006-07-10 11:31:31
Also in: linux-mm, lkml

Mel Gorman [off-list ref] wrote:

+unsigned long __initdata dma_reserve;

Should this be static?  Or should it be predeclared in a header file
somewhere?

David