From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andi Kleen <ak@linux•intel.com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Naoya Horiguchi <n-horiguchi@ah•jp.nec.com>,
Jun'ichi Nomura <j-nomura@ce•jp.nec.com>
Subject: Re: linux-next: build failure after merge of the final tree (hwpoison tree related)
Date: Wed, 29 Sep 2010 12:57:56 +1000 [thread overview]
Message-ID: <20100929125756.2e264f7a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100927155551.2e4e4b26.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hi Andi,
On Mon, 27 Sep 2010 15:55:51 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the final tree, today's linux-next build (powerpc allnoconfig)
> failed like this:
>
> mm/mprotect.o: In function `migrate_huge_page_move_mapping':
> mprotect.c:(.text+0x0): multiple definition of `migrate_huge_page_move_mapping'
> mm/shmem.o:shmem.c:(.text+0x0): first defined here
> mm/rmap.o: In function `migrate_huge_page_move_mapping':
> rmap.c:(.text+0x0): multiple definition of `migrate_huge_page_move_mapping'
> mm/shmem.o:shmem.c:(.text+0x0): first defined here
>
> Caused by commit 7b217c52ce7f33379beb27aa7685109fa74ed6bf ("hugetlb:
> hugepage migration core").
>
> This function is declared as "extern int ..." with a body in
> include/linux/migrate.h for the non CONFIG_MIGRATION case.
>
> I reverted the whole hwpoison tree for today.
This is still not fixed ... so I am still using the hwpoison tree from
next-20100924.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-09-29 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 5:55 linux-next: build failure after merge of the final tree (hwpoison tree related) Stephen Rothwell
2010-09-29 2:57 ` Stephen Rothwell [this message]
2010-10-03 23:36 ` Stephen Rothwell
2010-09-30 2:54 ` Naoya Horiguchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100929125756.2e264f7a.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ak@linux$(echo .)intel.com \
--cc=j-nomura@ce$(echo .)jp.nec.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=n-horiguchi@ah$(echo .)jp.nec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox