From: patchwork-bot+linux-riscv@kernel.org
To: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, conor@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, nathan@kernel.org,
ndesaulniers@google.com, trix@redhat.com, bmeng@tinylab.org,
guoren@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, stable@vger.kernel.org,
conor.dooley@microchip.com
Subject: Re: [PATCH] riscv: Fix build errors using binutils2.37 toolchains
Date: Thu, 24 Aug 2023 20:10:22 +0000 [thread overview]
Message-ID: <169290782216.11381.9335896608253523695.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230824190852.45470-1-xingmingzheng@iscas.ac.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 25 Aug 2023 03:08:52 +0800 you wrote:
> When building the kernel with binutils 2.37 and GCC-11.1.0/GCC-11.2.0,
> the following error occurs:
>
> Assembler messages:
> Error: cannot find default versions of the ISA extension `zicsr'
> Error: cannot find default versions of the ISA extension `zifencei'
>
> [...]
Here is the summary with links:
- riscv: Fix build errors using binutils2.37 toolchains
https://git.kernel.org/riscv/c/ef21fa7c198e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-24 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:08 [PATCH] riscv: Fix build errors using binutils2.37 toolchains Mingzheng Xing
2023-08-24 19:25 ` Conor Dooley
2023-08-24 19:36 ` Palmer Dabbelt
2023-08-24 20:08 ` Palmer Dabbelt
2023-08-24 20:10 ` patchwork-bot+linux-riscv [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=169290782216.11381.9335896608253523695.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bmeng@tinylab.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=stable@vger.kernel.org \
--cc=trix@redhat.com \
--cc=xingmingzheng@iscas.ac.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