From: Sachin Sant <sachinp@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org
Subject: Next March 18: defconfig build break on s390
Date: Wed, 18 Mar 2009 15:51:09 +0530 [thread overview]
Message-ID: <49C0CB15.1090308@in.ibm.com> (raw)
In-Reply-To: <20090318173830.7ea03dfb.sfr@canb.auug.org.au>
Today's next defconfig build on s390 fails with
In file included from arch/s390/include/asm/tlb.h:29,
from arch/s390/mm/init.c:36:
arch/s390/include/asm/tlbflush.h: In function __tlb_flush_full:
arch/s390/include/asm/tlbflush.h:54: error: incompatible type for argument 2 of cpumask_equal
In file included from arch/s390/kernel/smp.c:46:
arch/s390/include/asm/tlbflush.h: In function __tlb_flush_full:
arch/s390/include/asm/tlbflush.h:54: error: incompatible type for argument 2 of cpumask_equal
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-03-18 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 6:38 linux-next: Tree for March 18 Stephen Rothwell
2009-03-18 10:21 ` Sachin Sant [this message]
2009-03-18 10:28 ` Next March 18: defconfig build break on s390 Sachin Sant
2009-03-18 10:58 ` Next March 18: [staging/net ??] build break Sachin Sant
2009-03-18 15:27 ` Greg KH
2009-03-18 16:18 ` linux-next: Tree for March 18 (mm.h #error) Randy Dunlap
2009-03-19 16:47 ` Randy Dunlap
2009-03-18 16:31 ` linux-next: Tree for March 18 (staging/comedi) Randy Dunlap
2009-03-18 16:33 ` Greg KH
2009-03-21 4:36 ` Greg KH
2009-03-21 5:10 ` Stephen Rothwell
2009-03-18 17:00 ` [PATCH] staging/line6: fix build error, select SND_RAWMIDI Randy Dunlap
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=49C0CB15.1090308@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).