From: patchwork-bot+linux-riscv@kernel.org
To: Petr Tesarik <petrtesarik@huaweicloud.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
conor.dooley@microchip.com, lihuafei1@huawei.com,
liaochang1@huawei.com, masahiroy@kernel.org,
keescook@chromium.org, akpm@linux-foundation.org,
heiko@sntech.de, ribalda@chromium.org, hi@alyssa.is,
lizhengyu3@huawei.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, duwe@suse.de,
roberto.sassu@huaweicloud.com, petr@tesarici.cz
Subject: Re: [PATCH v2 0/3] RISC-V: Fix a few kexec_file_load(2) failures
Date: Thu, 03 Aug 2023 15:10:22 +0000 [thread overview]
Message-ID: <169107542294.19238.10753003765050685366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1690365011.git.petr.tesarik.ext@huawei.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 26 Jul 2023 11:53:58 +0200 you wrote:
> From: Petr Tesarik <petr.tesarik.ext@huawei.com>
>
> The kexec_file_load(2) syscall does not work at least in some kernel
> builds. For details see the relevant section in this blog post:
>
> https://sigillatum.tesarici.cz/2023-07-21-state-of-riscv64-kdump.html
>
> [...]
Here is the summary with links:
- [v2,1/3] riscv/kexec: handle R_RISCV_CALL_PLT relocation type
https://git.kernel.org/riscv/c/1be0b05b3a80
- [v2,2/3] riscv/purgatory: do not link with string.o and its dependencies
(no matching commit)
- [v2,3/3] riscv/kexec: load initrd high in available memory
https://git.kernel.org/riscv/c/0ccd2e803745
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
next prev parent reply other threads:[~2023-08-03 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 9:53 [PATCH v2 0/3] RISC-V: Fix a few kexec_file_load(2) failures Petr Tesarik
2023-07-26 9:53 ` [PATCH v2 1/3] riscv/kexec: handle R_RISCV_CALL_PLT relocation type Petr Tesarik
2023-07-26 16:30 ` Conor Dooley
2023-07-26 9:54 ` [PATCH v2 2/3] riscv/purgatory: do not link with string.o and its dependencies Petr Tesarik
2023-07-26 16:33 ` Conor Dooley
2023-08-03 15:13 ` Palmer Dabbelt
2023-08-03 15:17 ` Conor Dooley
2023-08-03 15:33 ` Petr Tesarik
2023-07-26 9:54 ` [PATCH v2 3/3] riscv/kexec: load initrd high in available memory Petr Tesarik
2023-07-26 16:38 ` Conor Dooley
2023-07-26 18:27 ` Petr Tesarik
2023-08-01 9:27 ` [PATCH v2 0/3] RISC-V: Fix a few kexec_file_load(2) failures Petr Tesarik
2023-08-03 15:10 ` patchwork-bot+linux-riscv [this message]
2023-08-09 14:35 ` (subset) " Palmer Dabbelt
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=169107542294.19238.10753003765050685366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=duwe@suse.de \
--cc=heiko@sntech.de \
--cc=hi@alyssa.is \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=liaochang1@huawei.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=masahiroy@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=petr@tesarici.cz \
--cc=petrtesarik@huaweicloud.com \
--cc=ribalda@chromium.org \
--cc=roberto.sassu@huaweicloud.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