From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Huang Pei <huangpei@loongson.cn>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
ambrosehua@gmail.com, Bibo Mao <maobibo@loongson.cn>,
linux-mips@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, Jiaxun Yang <jiaxun.yang@flygoat.com>,
Paul Burton <paulburton@kernel.org>,
Li Xuefeng <lixuefeng@loongson.cn>,
Yang Tiezhu <yangtiezhu@loongson.cn>,
Gao Juxin <gaojuxin@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>,
Jinyang He <hejinyang@loongson.cn>,
Steven Rostedt <rostedt@goodmis.org>,
Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] MIPS: fix local_t operation on MIPS64
Date: Mon, 6 Sep 2021 18:29:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2109061827590.38640@angie.orcam.me.uk> (raw)
In-Reply-To: <20210906140307.cnj7iv567aibvhzr@ThinkPad-W520>
On Mon, 6 Sep 2021, Huang Pei wrote:
> || {standard input}: Assembler messages:
> {standard input}|11389| Error: unrecognized opcode `long_addu $6,$3,$2'
> {standard input}|11392| Error: unrecognized opcode `long_addu $6,$3,$2'
> {standard input}|11404| Error: unrecognized opcode `long_addu $5,$7,$2'
> {standard input}|11407| Error: unrecognized opcode `long_addu $5,$7,$2'
> {standard input}|12354| Error: unrecognized opcode `long_addu $20,$3,$2'
> {standard input}|12357| Error: unrecognized opcode `long_addu $20,$3,$2'
Sheesh, you need to unquote the references to get them expanded.
Maciej
next prev parent reply other threads:[~2021-09-06 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210904151218.10167-1-huangpei@loongson.cn>
2021-09-04 17:57 ` [PATCH] MIPS: fix local_t operation on MIPS64 Maciej W. Rozycki
[not found] ` <20210905004810.5783639.10620.10055@loongson.cn>
2021-09-06 11:08 ` Maciej W. Rozycki
[not found] ` <20210906140307.cnj7iv567aibvhzr@ThinkPad-W520>
2021-09-06 16:29 ` Maciej W. Rozycki [this message]
[not found] ` <6113C299-3E26-4445-97FD-32690FD91C95@loongson.cn>
2021-09-07 10:00 ` Maciej W. Rozycki
2021-09-08 8:15 ` 黄沛
2021-09-04 18:50 ` kernel test robot
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=alpine.DEB.2.21.2109061827590.38640@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=Jisheng.Zhang@synaptics.com \
--cc=ambrosehua@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=gaojuxin@loongson.cn \
--cc=hejinyang@loongson.cn \
--cc=huangpei@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixuefeng@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=mhiramat@kernel.org \
--cc=paulburton@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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).