From: patchwork-bot+linux-riscv@kernel.org
To: None <sunying@isrc.iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, ebiederm@xmission.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, zhuhengbo@iscas.ac.cn,
petr@tesarici.cz
Subject: Re: [PATCH v1] riscv/kexec_file: Fix relocation type R_RISCV_ADD16 and R_RISCV_SUB16 unknown
Date: Wed, 14 Aug 2024 14:10:33 +0000 [thread overview]
Message-ID: <172364463350.2278280.14691701821976528565.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711083236.2859632-1-sunying@isrc.iscas.ac.cn>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 11 Jul 2024 08:32:36 +0000 you wrote:
> From: Ying Sun <sunying@isrc.iscas.ac.cn>
>
> Runs on the kernel with CONFIG_RISCV_ALTERNATIVE enabled:
> kexec -sl vmlinux
>
> Error:
> kexec_image: Unknown rela relocation: 34
> kexec_image: Error loading purgatory ret=-8
> and
> kexec_image: Unknown rela relocation: 38
> kexec_image: Error loading purgatory ret=-8
>
> [...]
Here is the summary with links:
- [v1] riscv/kexec_file: Fix relocation type R_RISCV_ADD16 and R_RISCV_SUB16 unknown
https://git.kernel.org/riscv/c/2d1f51d8a4b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-08-14 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 8:32 [PATCH v1] riscv/kexec_file: Fix relocation type R_RISCV_ADD16 and R_RISCV_SUB16 unknown sunying
2024-07-11 12:53 ` Petr Tesařík
2024-07-17 13:14 ` Andrew Jones
2024-08-14 14: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=172364463350.2278280.14691701821976528565.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=petr@tesarici.cz \
--cc=sunying@isrc.iscas.ac.cn \
--cc=zhuhengbo@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