[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160203055819.GA5528@sudip-pc>
Date: Wed, 3 Feb 2016 11:28:19 +0530
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Matthew Wilcox <willy@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the akpm-current tree
On Wed, Feb 03, 2016 at 04:10:30PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (i386
> defconfig) failed like this:
>
> In file included from include/linux/mm.h:67:0,
> from include/linux/suspend.h:8,
> from arch/x86/kernel/asm-offsets.c:12:
> arch/x86/include/asm/pgtable.h:212:24: error: redefinition of 'pud_trans_huge'
> #define pud_trans_huge pud_trans_huge
> ^
> include/asm-generic/pgtable.h:696:19: note: in expansion of macro 'pud_trans_huge'
> static inline int pud_trans_huge(pud_t pud)
> ^
> arch/x86/include/asm/pgtable.h:208:19: note: previous definition of 'pud_trans_huge' was here
> static inline int pud_trans_huge(pud_t pud)
> ^
>
> Caused by commit
>
> 42416e8d1a10 ("x86-add-support-for-pud-sized-transparent-hugepages-fix")
>
> Which, it turns out, is "wrong/hacky" :-)
>
> I have reverted that patch for today and added this (also maybe
> wrong/hacky) patch:
And x86_64 defconfig also fails with:
../fs/proc/task_mmu.c: In function ‘smaps_pud_range’:
../fs/proc/task_mmu.c:596:2: error: implicit declaration of function
‘is_huge_zero_pud’ [-Werror=implicit-function-declaration]
regards
sudip
Powered by blists - more mailing lists