>>> Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 08.12.09 00:35 >>> >(cc linux-ia64) > >On Mon, 07 Dec 2009 16:24:03 +0000 >"Jan Beulich" <JBeulich@xxxxxxxxxx> wrote: > >> At least on ia64 vmalloc_end is a global variable that VMALLOC_END >> expands to. Hence having a local variable named vmalloc_end and >> initialized from VMALLOC_END won't work on such platforms. Rename >> these variables, and for consistency also rename vmalloc_start. >> > >erk. So does 2.6.32's vmalloc() actually work correctly on ia64? According to Tejun the problem is just cosmetic (i.e. causes build warnings), since the functions affected aren't being used (yet) on ia64. So feel free to drop the patch again, given that he has a patch queued to address the issue by renaming the arch variable. I wonder though why that code is being built on ia64 at all if it's not being used (i.e. why it doesn't depend on a CONFIG_*, HAVE_*, or NEED_* manifest constant). Jan -- 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
|