On Tue, 12 Feb 2013 16:11:33 -0800
Tony Luck <tony.luck@xxxxxxxxx> wrote:
> Building linux-next today (tag next-20130212) I get the following errors when
> building arch/ia64/configs/{tiger_defconfig, zx1_defconfig, bigsur_defconfig,
> sim_defconfig}
>
> arch/ia64/mm/init.c: In function 'free_initrd_mem':
> arch/ia64/mm/init.c:215: error: 'max_addr' undeclared (first use in
> this function)
> arch/ia64/mm/init.c:215: error: (Each undeclared identifier is
> reported only once
> arch/ia64/mm/init.c:215: error: for each function it appears in.)
> arch/ia64/mm/init.c:216: error: implicit declaration of function
> 'GRANULEROUNDDOWN'
>
> with "git blame" saying that these lines in init.c were added/changed by
>
> commit 5a54b4fb8f554b15c6113e30ca8412b7fe11c62e
> Author: Xishi Qiu <qiuxishi@xxxxxxxxxx>
> Date: Thu Feb 7 12:25:59 2013 +1100
>
> ia64/mm: fix a bad_page bug when crash kernel booting
>
Presumably this:
--- a/arch/ia64/mm/init.c~ia64-mm-fix-a-bad_page-bug-when-crash-kernel-booting-fix
+++ a/arch/ia64/mm/init.c
@@ -27,6 +27,7 @@
#include <asm/machvec.h>
#include <asm/numa.h>
#include <asm/patch.h>
+#include <asm/meminit.h>
#include <asm/pgalloc.h>
#include <asm/sal.h>
#include <asm/sections.h>
_
But, umm, why am I sitting here trying to maintain an ia64 bugfix and
handling bug reports from the ia64 maintainer? Wanna swap?
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|