From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390: Fix build failure in __cpu_up()
Date: Mon, 09 Jun 2008 12:05:12 +0000 [thread overview]
Message-ID: <1213013112.19343.31.camel@localhost> (raw)
In-Reply-To: <1213013059.19343.29.camel@localhost>
On Mon, 2008-06-09 at 13:31 +0200, Segher Boessenkool wrote:
> >> I'll add this patch to the queue for 2.6.26 and have to think
> about
> >> some
> >> more fixes.
> >
> > The patch below should fix the problem with unsigned long arguments
> > instead of arrays of unsigned long. Could you test if your gcc still
> > crashes with the patch (but without yours)?
>
> Sure. Nope, no more crash. Good :-)
Thanks for the verification. I will send both patches soonish.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
parent reply other threads:[~2008-06-09 12:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1213013059.19343.29.camel@localhost>]
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=1213013112.19343.31.camel@localhost \
--to=schwidefsky@de.ibm.com \
--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