lkml.org 
[lkml]   [2013]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-next: build warning after merge of the tip tree

* Stephen Rothwell <sfr@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



\
 
 \ /
  Last update: 2013-08-19 09:21    [W:1.204 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site