* Stephen Rothwell <s...@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> arch/x86/kernel/paravirt.c:66:0: warning: "DEF_NATIVE" redefined [enabled by
> default]
> #define DEF_NATIVE(ops, name, code) \
> ^
> In file included from arch/x86/include/asm/ptrace.h:65:0,
> from arch/x86/include/asm/alternative.h:8,
> from arch/x86/include/asm/bitops.h:16,
> from include/linux/bitops.h:22,
> from include/linux/kernel.h:10,
> from include/linux/cache.h:4,
> from include/linux/time.h:4,
> from include/linux/stat.h:18,
> from include/linux/module.h:10,
> from arch/x86/kernel/paravirt.c:22:
> arch/x86/include/asm/paravirt_types.h:391:0: note: this is the location of
> the previous definition
> #define DEF_NATIVE(ops, name, code) \
> ^
>
> Introduced by commit 9a55fdbe941e ("x86, asmlinkage, paravirt: Add
> __visible/asmlinkage to xen paravirt ops"). The 2 definitions used to be
> identical ... maybe there should be only one.
Andi, please send a fix for this build warning, against
tip:x86/asmlinkage.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
