From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>,
lijiang <lijiang@redhat.com>
Cc: "Discussion list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>,
Nick Kossifidis <mick@ics.forth.gr>,
"heinrich.schuchardt@canonical.com"
<heinrich.schuchardt@canonical.com>,
"guoren@kernel.org" <guoren@kernel.org>,
Yixun Lan <yixun.lan@gmail.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"hschauhan@nulltrace.org" <hschauhan@nulltrace.org>,
"huanyi.xj@alibaba-inc.com" <huanyi.xj@alibaba-inc.com>,
"lifang_xia@linux.alibaba.com" <lifang_xia@linux.alibaba.com>
Subject: Re: [PATCH V3 0/9] Support RISCV64 arch and common commands
Date: Tue, 13 Sep 2022 13:47:37 +0800 [thread overview]
Message-ID: <c429f8d5-332f-8d69-79e9-5a585cc7b11a@linux.alibaba.com> (raw)
In-Reply-To: <e9efc067-360f-3144-a1c4-728b12a7a148@nec.com>
在 2022/9/13 下午12:27, HAGIO KAZUHITO(萩尾 一仁) 写道:
> On 2022/09/13 11:11, Xianting Tian wrote:
>> 在 2022/9/9 下午5:21, lijiang 写道:
>>> But anyway, these issues can be improved with later patches, so for the v3: ACK.
>> Thanks Li Jiang for the comments and ACK,
>>
>> Now I received two ACKs for you and Kazu, Could I know when this patch set can be merged to the mainline?
> Usually a crash patch is merged when a required or targeted kernel patch
> is merged mainline. If the kernel patch for vmcoreinfo is merged in 6.1
> merge window, the patch set will also be merged that time.
Thanks for the reply.
>
> Thanks,
> Kazu
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2022-09-13 5:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 3:17 [Crash-utility][PATCH V3 0/9] Support RISCV64 arch and common commands Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 1/9] Add RISCV64 framework code support Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 2/9] RISCV64: Make crash tool enter command line and support some commands Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 3/9] RISCV64: Add 'dis' command support Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 4/9] RISCV64: Add 'irq' " Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 5/9] RISCV64: Add 'bt' " Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 6/9] RISCV64: Add 'help -r' " Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 7/9] RISCV64: Add 'help -m/M' " Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 8/9] RISCV64: Add 'mach' " Xianting Tian
2022-08-13 3:17 ` [Crash-utility][PATCH V3 9/9] RISCV64: Add the implementation of symbol verify Xianting Tian
[not found] ` <CANU+ZyckYehZaX0uSLPiyLKq2TMmTkqs3O6i4=NerdjXGGxBDA@mail.gmail.com>
2022-08-22 7:28 ` [PATCH V3 0/9] Support RISCV64 arch and common commands Yixun Lan
2022-08-24 8:57 ` Xianting Tian
[not found] ` <CANU+Zyd+276V6uDsWcyCtB+sfdu2xObvnh9Sxmr4d=UOt27nNQ@mail.gmail.com>
2022-09-13 2:11 ` Xianting Tian
2022-09-13 4:27 ` HAGIO KAZUHITO(萩尾 一仁)
2022-09-13 5:47 ` Xianting Tian [this message]
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=c429f8d5-332f-8d69-79e9-5a585cc7b11a@linux.alibaba.com \
--to=xianting.tian@linux.alibaba.com \
--cc=crash-utility@redhat.com \
--cc=guoren@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=hschauhan@nulltrace.org \
--cc=huanyi.xj@alibaba-inc.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=lifang_xia@linux.alibaba.com \
--cc=lijiang@redhat.com \
--cc=mick@ics.forth.gr \
--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