The patch titled
Subject: mm/nommu.c: export symbol max_mapnr
has been added to the -mm tree. Its filename is
mm-nommu-export-symbol-max_mapnr.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-nommu-export-symbol-max_mapnr.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-nommu-export-symbol-max_mapnr.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: gchen gchen <xili_gchen_5257@xxxxxxxxxxx>
Subject: mm/nommu.c: export symbol max_mapnr
Several modules may need max_mapnr, so export, the related error with
allmodconfig under c6x:
MODPOST 3327 modules
ERROR: "max_mapnr" [fs/pstore/ramoops.ko] undefined!
ERROR: "max_mapnr" [drivers/media/v4l2-core/videobuf2-dma-contig.ko] undefined!
Signed-off-by: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
Cc: Mark Salter <msalter@xxxxxxxxxx>
Cc: Aurelien Jacquiot <a-jacquiot@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/nommu.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/nommu.c~mm-nommu-export-symbol-max_mapnr mm/nommu.c
--- a/mm/nommu.c~mm-nommu-export-symbol-max_mapnr
+++ a/mm/nommu.c
@@ -62,6 +62,7 @@ void *high_memory;
EXPORT_SYMBOL(high_memory);
struct page *mem_map;
unsigned long max_mapnr;
+EXPORT_SYMBOL(max_mapnr);
unsigned long highest_memmap_pfn;
struct percpu_counter vm_committed_as;
int sysctl_overcommit_memory = OVERCOMMIT_GUESS; /* heuristic overcommit */
_
Patches currently in -mm which might be from xili_gchen_5257@xxxxxxxxxxx are
mm-nommu-export-symbol-max_mapnr.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
