From: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
To: Xianting Tian <xianting.tian@linux.alibaba.com>,
lijiang <lijiang@redhat.com>,
"crash-utility@redhat.com" <crash-utility@redhat.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"hschauhan@nulltrace.org" <hschauhan@nulltrace.org>,
"lifang_xia@linux.alibaba.com" <lifang_xia@linux.alibaba.com>,
"mick@ics.forth.gr" <mick@ics.forth.gr>,
"heinrich.schuchardt@canonical.com"
<heinrich.schuchardt@canonical.com>,
"guoren@kernel.org" <guoren@kernel.org>,
"yixun.lan@gmail.com" <yixun.lan@gmail.com>
Subject: Re: [Crash-utility][PATCH V4 1/9] Add RISCV64 framework code support
Date: Thu, 22 Dec 2022 04:48:52 +0000 [thread overview]
Message-ID: <712596d6-a7c1-f0fa-4aef-6ecfa1f249a0@nec.com> (raw)
In-Reply-To: <f120e4f0-1db9-fc6a-85dd-f42b58ca4d88@linux.alibaba.com>
On 2022/11/09 18:01, Xianting Tian wrote:
>> On the kernel side, some relevant kernel patches got ack, it seems
>> they won't change anymore.
>>
>> And the V4 looks good to me, so: Ack.
> Thanks, Linux kenrel RISC-V maintainer still don't apply the kernel patch, let's wait.
Now I see 649d6b1019a2 ("RISC-V: Add arch_crash_save_vmcoreinfo")
in the mainline, so applied the crash patchset.
https://github.com/crash-utility/crash/compare/88a4910d95d4...0d5ad129252a
Thanks,
Kazu
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-12-22 4:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:50 [Crash-utility][PATCH V4 0/9] Support RISCV64 arch and common commands Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 1/9] Add RISCV64 framework code support Xianting Tian
2022-10-21 2:17 ` HAGIO KAZUHITO(萩尾 一仁)
2022-10-21 2:42 ` Xianting Tian
2022-10-21 2:57 ` HAGIO KAZUHITO(萩尾 一仁)
2022-11-03 5:32 ` lijiang
2022-11-09 9:01 ` Xianting Tian
2022-12-22 4:48 ` HAGIO KAZUHITO(萩尾 一仁) [this message]
2022-10-20 1:50 ` [Crash-utility][PATCH V4 2/9] RISCV64: Make crash tool enter command line and support some commands Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 3/9] RISCV64: Add 'dis' command support Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 4/9] RISCV64: Add irq " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 5/9] RISCV64: Add 'bt' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 6/9] RISCV64: Add 'help -r' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 7/9] RISCV64: Add 'help -m/M' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 8/9] RISCV64: Add 'mach' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 9/9] RISCV64: Add the implementation of symbol verify Xianting Tian
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=712596d6-a7c1-f0fa-4aef-6ecfa1f249a0@nec.com \
--to=k-hagio-ab@nec.com \
--cc=crash-utility@redhat.com \
--cc=guoren@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=hschauhan@nulltrace.org \
--cc=kexec@lists.infradead.org \
--cc=lifang_xia@linux.alibaba.com \
--cc=lijiang@redhat.com \
--cc=mick@ics.forth.gr \
--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