From: Nick Kossifidis <mick@ics.forth.gr>
To: ebiederm@xmission.com, kexec@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
alex@ghiti.fr, rppt@kernel.org, geert+renesas@glider.be,
Stephano Cetola <scetola@linuxfoundation.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
palmer@dabbelt.com, anup.patel@wdc.com, atish.patra@wdc.com
Subject: RISC-V: patched kexec-tools on github for review/testing
Date: Tue, 05 Oct 2021 15:13:30 +0300 [thread overview]
Message-ID: <00c521b5b872b06c9350145c7d39fe7c@mailhost.ics.forth.gr> (raw)
Hello all,
I've uploaded my kexec-tools patches for riscv on github for
testing/review before sending them upstream.
https://github.com/riscv-collab/kexec-tools/tree/riscv
Both kexec and kdump were tested on latest rv64 qemu, using for-next
branch with this patch applied:
https://patchwork.kernel.org/project/linux-riscv/patch/20211002122026.1451269-1-mick@ics.forth.gr/
Regards,
Nick
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2021-10-05 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 12:13 Nick Kossifidis [this message]
2021-10-05 14:07 ` RISC-V: patched kexec-tools on github for review/testing Alexandre Ghiti
2021-10-06 11:10 ` Alexandre Ghiti
2021-10-09 13:25 ` Nick Kossifidis
2021-10-15 7:07 ` Alexandre Ghiti
2021-11-25 23:43 ` Nick Kossifidis
2022-07-02 11:35 ` Yixun Lan
2022-07-05 12:23 ` Nick Kossifidis
2022-07-05 14:12 ` Yixun Lan
2022-09-06 14:49 ` Vasily Averin
2022-09-07 3:23 ` Yixun Lan
2022-08-20 2:19 ` Yixun Lan
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=00c521b5b872b06c9350145c7d39fe7c@mailhost.ics.forth.gr \
--to=mick@ics.forth.gr \
--cc=alex@ghiti.fr \
--cc=anup.patel@wdc.com \
--cc=atish.patra@wdc.com \
--cc=ebiederm@xmission.com \
--cc=geert+renesas@glider.be \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=rppt@kernel.org \
--cc=scetola@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).