linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
	Johannes Weiner <hannes@saeurebad.de>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 8/8] mem_map/max_mapnr are specific to the FLATMEM memory model
Date: Mon, 02 Jun 2008 16:13:25 +0100	[thread overview]
Message-ID: <48440E15.4080008@goop.org> (raw)
In-Reply-To: <1207824082.0@pinky>

Andy Whitcroft wrote:
> mem_map and max_mapnr are variables used in the FLATMEM memory model
> only.  Ensure they are only defined when that memory model is enabled.
>   

Is this series queued to be applied?

BTW, how does max_mapnr differ from x86-64's end_pfn?

> Signed-off-by: Andy Whitcroft <apw@shadowen.org>
> ---
>  mm/memory.c |    3 +--
>   

I think you need to fix the declaration in linux/mm.h as well.

>  1 files changed, 1 insertions(+), 2 deletions(-)
> diff --git a/mm/memory.c b/mm/memory.c
> index 0d14d1e..091324e 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -61,8 +61,7 @@
>  #include <linux/swapops.h>
>  #include <linux/elf.h>
>  
> -#ifndef CONFIG_NEED_MULTIPLE_NODES
> -/* use the per-pgdat data instead for discontigmem - mbligh */
> +#ifdef CONFIG_FLATMEM
>  unsigned long max_mapnr;
>  struct page *mem_map;
>  
>   

Thanks,
    J

--
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>

  reply	other threads:[~2008-06-02 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1207340609.26869.20.camel@nimitz.home.sr71.net>
2008-04-10 10:33 ` max_mapnr config option Andy Whitcroft
2008-04-10 10:40   ` [PATCH 1/8] alpha: mem_map/max_mapnr -- init is FLATMEM use correct defines Andy Whitcroft
2008-04-10 10:41   ` [PATCH 2/8] arm: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 3/8] m32r: mem_map/max_mapnr -- definition is specific to FLATMEM Andy Whitcroft
2008-04-10 10:41   ` [PATCH 4/8] mips: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 5/8] parisc: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 6/8] powerpc: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 7/8] sparc64: " Andy Whitcroft
2008-04-10 10:41   ` [PATCH 8/8] mem_map/max_mapnr are specific to the FLATMEM memory model Andy Whitcroft
2008-06-02 15:13     ` Jeremy Fitzhardinge [this message]
     [not found] ` <20080407091756.GC17915@shadowen.org>
     [not found]   ` <87iqyuhth2.fsf@saeurebad.de>
     [not found]     ` <20080408105137.GD17915@shadowen.org>
2008-05-23 13:09       ` max_mapnr config option apw
2008-05-23 19:52         ` Johannes Weiner

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=48440E15.4080008@goop.org \
    --to=jeremy@goop.org \
    --cc=apw@shadowen.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=hannes@saeurebad.de \
    --cc=linux-mm@kvack.org \
    /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