From: patchwork-bot+linux-riscv@kernel.org
To: Song Shuai <songshuaishuai@tinylab.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
conor.dooley@microchip.com, lihuafei1@huawei.com,
petr.tesarik.ext@huawei.com, duwe@suse.de, ribalda@chromium.org,
akpm@linux-foundation.org, keescook@chromium.org, hi@alyssa.is,
heiko@sntech.de, lizhengyu3@huawei.com, alexghiti@rivosinc.com,
schwab@suse.de, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org
Subject: Re: [PATCH V1 0/3] riscv: kexec: cleanup and fixups
Date: Wed, 13 Sep 2023 00:37:00 +0000 [thread overview]
Message-ID: <169456542018.30716.13506539771908013747.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230907103304.590739-1-songshuaishuai@tinylab.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 7 Sep 2023 18:33:01 +0800 you wrote:
> Hi,
>
> I had posted 2 patches [1][2] for riscv/kexec, but there was no "effective"
> response to them until now, so I merged them in this series with the 3rd fixup.
>
> Anyway, this series contains a cleanup for riscv_kexec_relocate() and two fixups
> for KEXEC_FILE and had passed the basic kexec test in my 64bit Qemu-virt.
>
> [...]
Here is the summary with links:
- [V1,1/3] riscv: kexec: Cleanup riscv_kexec_relocate
(no matching commit)
- [V1,2/3] riscv: kexec: Align the kexeced kernel entry
https://git.kernel.org/riscv/c/1bfb2b618d52
- [V1,3/3] riscv: kexec: Remove -fPIE for PURGATORY_CFLAGS
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
parent reply other threads:[~2023-09-13 0:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230907103304.590739-1-songshuaishuai@tinylab.org>]
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=169456542018.30716.13506539771908013747.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--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=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=petr.tesarik.ext@huawei.com \
--cc=ribalda@chromium.org \
--cc=schwab@suse.de \
--cc=songshuaishuai@tinylab.org \
/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