From: Fengguang Wu <fengguang.wu@intel.com>
To: Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Slaby <jslaby@suse.cz>,
kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kbuild-all] [jirislaby-stable:stable-3.12-queue 2253/5333] arch/mips/kernel/r4k_switch.S:67: Error: opcode not supported on this processor: loongson2e (mips3) `sdc1 $f1, 904($4)'
Date: Fri, 22 Jul 2016 20:26:32 +0800 [thread overview]
Message-ID: <20160722122632.GB32690@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <201607221956.UfStWvqZ%fengguang.wu@intel.com>
>config: mips-fuloong2e_defconfig (attached as .config)
>compiler: mips64el-linux-gnuabi64-gcc (Debian 5.4.0-6) 5.4.0 20160609
>All errors (new ones prefixed by >>):
>
> arch/mips/kernel/r4k_switch.S: Assembler messages:
>>> arch/mips/kernel/r4k_switch.S:67: Error: opcode not supported on this processor: loongson2e (mips3) `sdc1 $f1,904($4)'
> arch/mips/kernel/r4k_switch.S:67: Error: opcode not supported on this processor: loongson2e (mips3) `sdc1 $f3,920($4)'
> arch/mips/kernel/r4k_switch.S:67: Error: opcode not supported on this processor: loongson2e (mips3) `sdc1 $f5,936($4)'
> arch/mips/kernel/r4k_switch.S:67: Error: opcode not supported on this processor: loongson2e (mips3) `sdc1 $f7,952($4)'
Sorry I'll shut them up -- they obviously should have unique error id
and hence the duplicates be ignored.
Thanks,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-07-22 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 11:04 [jirislaby-stable:stable-3.12-queue 2253/5333] arch/mips/kernel/r4k_switch.S:67: Error: opcode not supported on this processor: loongson2e (mips3) `sdc1 $f1,904($4)' kbuild test robot
2016-07-22 12:26 ` Fengguang Wu [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=20160722122632.GB32690@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
/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