From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Avi Kivity <avi@qumranet•com>, Marcelo Tosatti <mtosatti@redhat•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Huang Ying <ying.huang@intel•com>,
David Miller <davem@davemloft•net>,
Andrew Morton <akpm@linux-foundation•org>
Subject: linux-next: build failure after merge of the final tree (kvm tree related)
Date: Mon, 21 Feb 2011 17:56:58 +1100 [thread overview]
Message-ID: <20110221175658.2dc4d1ac.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Hi all,
After merging the final tree, today's linux-next build (sparc64 defconfig)
failed like this:
mm/memory.c: In function '__get_user_pages':
mm/memory.c:1584: error: 'EHWPOISON' undeclared (first use in this function)
Caused by commit b1c4f2836370f5c8207d4c61e91c93bd6a4ce27a ("mm: make
__get_user_pages return -EHWPOISON for HWPOISON page optionally") from
the kvm tree.
Not all architectures use include/asm-generic/errno.h ...
I have reverted that commit (and commits
d47b742c5661385b927c03188549b2d2004b80f4 "KVM: Replace
is_hwpoison_address with __get_user_pages" and
eef8839430b72deac59e9ec51eb56c44512fcc66 "mm: remove is_hwpoison_address"
which depend on it) for today.
--
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 reply other threads:[~2011-02-21 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 6:56 Stephen Rothwell [this message]
2011-02-21 8:10 ` linux-next: build failure after merge of the final tree (kvm tree related) Huang Ying
2011-02-28 2:15 ` Stephen Rothwell
2011-02-28 2:28 ` Huang Ying
2011-02-28 9:36 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 3:28 Stephen Rothwell
2011-05-25 8:02 ` Heiko Carstens
2011-05-26 6:42 ` Avi Kivity
2010-09-03 1:32 Stephen Rothwell
2010-07-26 4:27 Stephen Rothwell
2010-08-02 0:33 ` Stephen Rothwell
2010-08-02 3:40 ` Avi Kivity
2010-08-02 4:25 ` Stephen Rothwell
2010-04-07 6:40 Stephen Rothwell
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=20110221175658.2dc4d1ac.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=avi@qumranet$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mtosatti@redhat$(echo .)com \
--cc=ying.huang@intel$(echo .)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