From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Build errors in -next due to ' s390/kernel: lazy restore fpu registers'
Date: Mon, 3 Aug 2015 13:59:58 +0200 [thread overview]
Message-ID: <20150803135958.0c34d9a9@mschwide> (raw)
In-Reply-To: <20150731183510.GA9117@roeck-us.net>
On Fri, 31 Jul 2015 11:35:10 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
> Hi,
>
> s390:defconfig and s390:allmodconfig fail to build in -next as follows.
>
> arch/s390/kernel/entry.S:806: Error:
> operand out of range (0x00000000000023e8 is not between 0x0000000000000000 and 0x0000000000000fff)
> arch/s390/kernel/entry.S:1254: Error:
> operand out of range (0x00000000000023e8 is not between 0x0000000000000000 and 0x0000000000000fff)
>
> bisect points to commit 9977e886cbb (" s390/kernel: lazy restore fpu
> registers").
>
> The build has been broken since at least July 20. I thought this was reported
> before, but maybe not; there may have been other failures masking this one.
>
> Guenter
Should be solved not with an additional patch on the features branch:
git commit d0164ee20d98847d3c777a0ae90e678e7ac1e416
s390/kernel: remove save_fpu_regs() parameter and use __LC_CURRENT instead
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2015-08-03 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 18:35 Build errors in -next due to ' s390/kernel: lazy restore fpu registers' Guenter Roeck
2015-08-03 11:59 ` 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=20150803135958.0c34d9a9@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linux@roeck-us.net \
/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