linux-kernel - Re: linux-next: build failure after merge of the s390 tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 20 May 2011 11:24:52 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the s390 tree

On Fri, 20 May 2011 11:56:51 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> 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.

Oops, sorry about that. Fixed the patch and updated git390.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/