From: Heiko Carstens <heiko.carstens@de•ibm.com>
To: Sachin Sant <sachinp@in•ibm.com>, Ingo Molnar <mingo@elte•hu>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: Next March 26: s390 allnoconfig build failure still exists
Date: Thu, 26 Mar 2009 11:12:23 +0100 [thread overview]
Message-ID: <20090326111223.3a8ad942@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <49CB5165.4060401@in.ibm.com>
On Thu, 26 Mar 2009 15:26:53 +0530
Sachin Sant <sachinp@in•ibm.com> wrote:
> I still see the following s390 allnoconfig build failure
> with today's next (and previous trees as well ).
>
> arch/s390/include/asm/smp.h:96: error: redefinition of smp_send_stop
> include/linux/smp.h:125: error: previous definition of smp_send_stop was here
In theory it should have been fixed, since I sent a patch and Ingo applied it:
http://lkml.org/lkml/2009/3/20/74
For some reason it doesn't show up in linux-next.
next prev parent reply other threads:[~2009-03-26 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 8:01 linux-next: Tree for March 26 Stephen Rothwell
2009-03-26 9:56 ` Next March 26: s390 allnoconfig build failure still exists Sachin Sant
2009-03-26 10:12 ` Heiko Carstens [this message]
2009-03-26 21:57 ` Stephen Rothwell
2009-03-26 15:46 ` linux-next: Tree for March 26 (benet) Randy Dunlap
2009-03-26 19:30 ` [PATCH] benet: use do_div() for 64 bit divide Stephen Hemminger
2009-03-26 20:10 ` Randy Dunlap
2009-03-27 7:26 ` David Miller
2009-03-26 21:44 ` [PATCH -next] exofs: fix printk format warnings Randy Dunlap
2009-03-30 8:14 ` Boaz Harrosh
2009-03-30 16:15 ` Geert Uytterhoeven
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=20090326111223.3a8ad942@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=sachinp@in$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/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