From: Greg Kroah-Hartman <gregkh@linux-foundation.org>
To: David Woodhouse <dwmw@amazon.co.uk>,
Razvan Ghitulete <rga@amazon.de>,
Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org
Subject: Re: Build errors in v4.4-stable-queue (i386)
Date: Thu, 18 Jan 2018 19:10:42 +0100 [thread overview]
Message-ID: <20180118181042.GA31694@kroah.com> (raw)
In-Reply-To: <20180118164158.GA21046@roeck-us.net>
On Thu, Jan 18, 2018 at 08:41:58AM -0800, Guenter Roeck wrote:
> Building i386:defconfig ... failed
> --------------
> Error log:
> arch/x86/entry/entry_32.S: Assembler messages:
> arch/x86/entry/entry_32.S:230: Error: too many memory references for `mov'
Ick, no good, 0-day has pointed this out as well.
Razvan and David, any ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-18 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 16:41 Build errors in v4.4-stable-queue (i386) Guenter Roeck
2018-01-18 18:10 ` Greg Kroah-Hartman [this message]
2018-01-19 9:34 ` David Woodhouse
2018-01-19 10:21 ` David Woodhouse
2018-01-19 12:26 ` Greg Kroah-Hartman
2018-01-19 13:08 ` David Woodhouse
2018-01-19 13:16 ` Greg Kroah-Hartman
2018-01-19 18:28 ` Guenter Roeck
2018-01-20 7:30 ` Greg Kroah-Hartman
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=20180118181042.GA31694@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=dwmw@amazon.co.uk \
--cc=linux@roeck-us.net \
--cc=rga@amazon.de \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).