From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the s390 tree
Date: Fri, 20 May 2011 11:56:51 +1000 [thread overview]
Message-ID: <20110520115651.fc0fc63f.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Hi all,
After merging the s390 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/rmap.c:788:54: error: macro "page_test_and_clear_dirty" passed 2 arguments, but takes just 1
mm/rmap.c: In function 'page_mkclean':
mm/rmap.c:788: error: 'page_test_and_clear_dirty' undeclared (first use in this function)
mm/rmap.c:788: error: (Each undeclared identifier is reported only once
mm/rmap.c:788: error: for each function it appears in.)
mm/rmap.c:983:52: error: macro "page_test_and_clear_dirty" passed 2 arguments, but takes just 1
mm/rmap.c: In function 'page_remove_rmap':
mm/rmap.c:983: error: 'page_test_and_clear_dirty' undeclared (first use in this function)
Caused by commit 4cbfc8b9f58c ("[S390] merge page_test_dirty and page_clear_dirty").
I have used the s390 tree from next-20110519 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-05-20 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 1:56 Stephen Rothwell [this message]
2011-05-20 9:24 ` linux-next: build failure after merge of the s390 tree Martin Schwidefsky
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 9:22 Stephen Rothwell
2023-01-10 14:22 ` Heiko Carstens
2024-08-08 3:58 Stephen Rothwell
2024-09-11 8:09 ` 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=20110520115651.fc0fc63f.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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