From: Guenter Roeck <linux@roeck-us.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build errors in v3.2-stable-queue
Date: Fri, 5 Aug 2016 18:00:28 -0700 [thread overview]
Message-ID: <20160806010028.GA2450@roeck-us.net> (raw)
In-Reply-To: <1470439600.4189.7.camel@decadent.org.uk>
On Sat, Aug 06, 2016 at 12:26:40AM +0100, Ben Hutchings wrote:
> On Sun, 2016-07-31 at 10:34 -0700, Guenter Roeck wrote:
> >�
> > Now I get a crash with the nosmp qemu test, and
>
> Did you work out what introduced that?
>
I didn't try. I can bisect later tonight after the current build completes
if the problem is still seen. I'll let you know.
Guenter
> >
> > {standard input}: Assembler messages:
> > {standard input}:343: Error: Unrecognized opcode `ll$4, 0($3)'
> > {standard input}:346: Error: Unrecognized opcode `sc$4, 0($3)'
> > scripts/Makefile.build:305: recipe for target
> > 'arch/mips/mm/ioremap.o' failed
> > make[2]: *** [arch/mips/mm/ioremap.o] Error 1
> > make[2]: *** Waiting for unfinished jobs....
> >
> > when building mips:malta_defconfig. Bisect points to
> > 'MIPS: Adjust set_pte() SMP fix to handle R10000_LLSC_WAR'.
> >
> > for the build error.
>
> Oh, I see the problem. �I'll push another version in a moment.
>
> Ben.
>
> --
> Ben Hutchings
> Beware of bugs in the above code;
> I have only proved it correct, not tried it. - Donald Knuth
next prev parent reply other threads:[~2016-08-06 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 3:58 Build errors in v3.2-stable-queue Guenter Roeck
2016-07-30 19:18 ` Ben Hutchings
2016-07-31 17:34 ` Guenter Roeck
2016-08-05 23:26 ` Ben Hutchings
2016-08-06 1:00 ` Guenter Roeck [this message]
2016-08-06 2:40 ` Guenter Roeck
2016-08-06 10:48 ` Ben Hutchings
2016-08-06 14:36 ` Guenter Roeck
2016-08-06 15:20 ` Ben Hutchings
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=20160806010028.GA2450@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ben@decadent.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.