From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [s390] build failure
Date: Tue, 04 Dec 2007 13:26:26 +0100 [thread overview]
Message-ID: <1196771186.9441.4.camel@localhost> (raw)
In-Reply-To: <E1IzWVI-0002zO-Ff@faramir.fjphome.nl>
On Tue, 2007-12-04 at 13:03 +0100, Frans Pop wrote:
> Martin Schwidefsky wrote:
> > On Wed, 2007-11-28 at 11:27 +0100, Frans Pop wrote:
> >> arch/s390/kernel/built-in.o: In function `cleanup_io_leave_insn':
> >> diag.c:(.text+0xc29a): undefined reference to `preempt_schedule_irq'
> >> make[2]: *** [.tmp_vmlinux1] Error 1
> >
> > This is fixes by a patch from Christian:
> > [S390] Fix compile error on 31bit without preemption
> >
> > You can get the latest s390 patches by pulling from
> > git://git390.osdl.marist.edu/pub/scm/linux-2.6.git fixes
>
> Any reason this has not been pushed into mainline yet? The fix missed -rc4
> because of that...
The a final s390 please pull for 2.6.24 will be sent in the next few
days. The preempt fix for 31 bit has been added to the repository by
Christian shortly after I sent the last please pull. I want to avoid to
sent too many of them.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2007-12-04 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 10:27 [s390] build failure Frans Pop
2007-11-28 10:51 ` Christian Borntraeger
2007-11-28 11:05 ` Frans Pop
2007-11-28 12:24 ` [s390] networking related oops during boot on Hercules (was: build failure) Frans Pop
2007-11-28 16:18 ` Christian Borntraeger
2007-11-28 17:05 ` Frans Pop
2007-11-28 17:26 ` Eric W. Biederman
2007-11-28 18:42 ` Stephen Hemminger
2007-11-28 17:30 ` Ursula Braun
2007-11-28 11:03 ` [s390] build failure Martin Schwidefsky
2007-12-04 12:03 ` Frans Pop
2007-12-04 12:26 ` Martin Schwidefsky [this message]
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=1196771186.9441.4.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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