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, "Dave Young" <dyoung@redhat.com>,
"Yixun Lan" <yixun.lan@gmail.com>,
"Xianting Tian" <xianting.tian@linux.alibaba.com>,
linux-riscv@lists.infradead.org,
"Björn Töpel" <bjorn@rivosinc.com>
Subject: Re: [PATCH 1/4] RISC-V: Add support for riscv kexec/kdump on kexec-tools
Date: Tue, 22 Apr 2025 14:54:05 +0100 [thread overview]
Message-ID: <20250422135405.GA2948814@horms.kernel.org> (raw)
In-Reply-To: <87bjso5ri7.fsf@all.your.base.are.belong.to.us>
On Tue, Apr 22, 2025 at 02:07:28PM +0200, Björn Töpel wrote:
> Simon!
>
> Simon Horman <horms@kernel.org> writes:
>
> > Thanks Björn,
> >
> > Overall I am happy with this patchset. But there are a few minor points
> > I'd like addressed, which relate strictly to build coverage and the CI.
> > I can handle these myself if you prefer.
>
> It's really up to you! What do you prefer? I can spin a v2 if that's
> easier for you (and then I'll try to address all the things you pointed
> out below)!
Hi Björn,
A v2 would be perfect for me.
If you are so inclined and you push the patches to a Github repo
then the workflow should run. It is what picked up the minor problems
I've highlighted.
But in any case, let's stick to the email based workflow
for patch submissions (for now).
_______________________________________________
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-22 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 20:14 [PATCH 0/4] kexec-tools RISC-V port Björn Töpel
2025-04-09 20:14 ` [PATCH 1/4] RISC-V: Add support for riscv kexec/kdump on kexec-tools Björn Töpel
2025-04-22 10:48 ` Simon Horman
2025-04-22 12:07 ` Björn Töpel
2025-04-22 13:54 ` Simon Horman [this message]
2025-04-09 20:14 ` [PATCH 2/4] RISC-V: Enable kexec_file_load syscall Björn Töpel
2025-04-09 20:14 ` [PATCH 3/4] RISC-V: Separate elf_riscv_find_pbase out Björn Töpel
2025-04-09 20:14 ` [PATCH 4/4] RISC-V: Support loading Image binary file Björn Töpel
2025-04-14 8:40 ` [PATCH 0/4] kexec-tools RISC-V port Simon Horman
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=20250422135405.GA2948814@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox