From: Simon Horman <horms@kernel.org>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: "Nick Kossifidis" <mick@ics.forth.gr>,
"Song Shuai" <songshuaishuai@tinylab.org>,
"Li Zhengyu" <lizhengyu3@huawei.com>,
kexec@lists.infradead.org, "Björn Töpel" <bjorn@rivosinc.com>,
"Dave Young" <dyoung@redhat.com>,
"Yixun Lan" <yixun.lan@gmail.com>,
"Xianting Tian" <xianting.tian@linux.alibaba.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/4] kexec-tools RISC-V port
Date: Wed, 23 Apr 2025 17:13:03 +0100 [thread overview]
Message-ID: <20250423161303.GZ2843373@horms.kernel.org> (raw)
In-Reply-To: <20250422162304.169431-1-bjorn@kernel.org>
On Tue, Apr 22, 2025 at 06:22:56PM +0200, Björn Töpel wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> Hi!
>
> *Patch history*
>
> v1: https://lore.kernel.org/kexec/20250409201428.648717-1-bjorn@kernel.org/
> v2: Added Github Actions support for riscv64 (Simon)
> Sorted filenames in Makefile (Simon)
> Added missing dist files (Simon)
> Fixed mips build (Simon)
>
> Here's a passed CI run with this series on master:
> https://github.com/bjoto/kexec-tools/actions/runs/14597988952/job/40948715214
Thanks Björn, and everyone who got us here.
I have applied this patch-set for inclusion in v2.0.32.
- x86_64: Use the x86-64 level for purgatory
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=14f48ea80e51
madeliefje ~/projects/kexec-tools/kexec-tools git kexec-tools-applied-log -4
- RISC-V: Support loading Image binary file
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=b257f311f5f0
- RISC-V: Separate elf_riscv_find_pbase out
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=363087cd156f
- RISC-V: Enable kexec_file_load syscall
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=027e6e237427
- RISC-V: Add support for riscv kexec/kdump on kexec-tools
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=b3fd54b022fe
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: "Nick Kossifidis" <mick@ics.forth.gr>,
"Song Shuai" <songshuaishuai@tinylab.org>,
"Li Zhengyu" <lizhengyu3@huawei.com>,
kexec@lists.infradead.org, "Björn Töpel" <bjorn@rivosinc.com>,
"Dave Young" <dyoung@redhat.com>,
"Yixun Lan" <yixun.lan@gmail.com>,
"Xianting Tian" <xianting.tian@linux.alibaba.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/4] kexec-tools RISC-V port
Date: Wed, 23 Apr 2025 17:13:03 +0100 [thread overview]
Message-ID: <20250423161303.GZ2843373@horms.kernel.org> (raw)
In-Reply-To: <20250422162304.169431-1-bjorn@kernel.org>
On Tue, Apr 22, 2025 at 06:22:56PM +0200, Björn Töpel wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> Hi!
>
> *Patch history*
>
> v1: https://lore.kernel.org/kexec/20250409201428.648717-1-bjorn@kernel.org/
> v2: Added Github Actions support for riscv64 (Simon)
> Sorted filenames in Makefile (Simon)
> Added missing dist files (Simon)
> Fixed mips build (Simon)
>
> Here's a passed CI run with this series on master:
> https://github.com/bjoto/kexec-tools/actions/runs/14597988952/job/40948715214
Thanks Björn, and everyone who got us here.
I have applied this patch-set for inclusion in v2.0.32.
- x86_64: Use the x86-64 level for purgatory
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=14f48ea80e51
madeliefje ~/projects/kexec-tools/kexec-tools git kexec-tools-applied-log -4
- RISC-V: Support loading Image binary file
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=b257f311f5f0
- RISC-V: Separate elf_riscv_find_pbase out
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=363087cd156f
- RISC-V: Enable kexec_file_load syscall
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=027e6e237427
- RISC-V: Add support for riscv kexec/kdump on kexec-tools
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=b3fd54b022fe
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-04-23 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 16:22 [PATCH v2 0/4] kexec-tools RISC-V port Björn Töpel
2025-04-22 16:22 ` Björn Töpel
2025-04-22 16:22 ` [PATCH v2 1/4] RISC-V: Add support for riscv kexec/kdump on kexec-tools Björn Töpel
2025-04-22 16:22 ` Björn Töpel
2025-04-22 16:22 ` [PATCH v2 2/4] RISC-V: Enable kexec_file_load syscall Björn Töpel
2025-04-22 16:22 ` Björn Töpel
2025-04-22 16:22 ` [PATCH v2 3/4] RISC-V: Separate elf_riscv_find_pbase out Björn Töpel
2025-04-22 16:22 ` Björn Töpel
2025-04-22 16:23 ` [PATCH v2 4/4] RISC-V: Support loading Image binary file Björn Töpel
2025-04-22 16:23 ` Björn Töpel
2025-04-23 16:13 ` Simon Horman [this message]
2025-04-23 16:13 ` [PATCH v2 0/4] kexec-tools RISC-V port Simon Horman
2025-05-05 11:02 ` Nick Kossifidis
2025-05-05 11:02 ` Nick Kossifidis
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=20250423161303.GZ2843373@horms.kernel.org \
--to=horms@kernel.org \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=mick@ics.forth.gr \
--cc=songshuaishuai@tinylab.org \
--cc=xianting.tian@linux.alibaba.com \
--cc=yixun.lan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.