From: Baoquan He <bhe@redhat.com>
To: Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, anup@brainfault.org, heiko@sntech.de,
guoren@kernel.org, mick@ics.forth.gr,
alexandre.ghiti@canonical.com, vgoyal@redhat.com,
dyoung@redhat.com, corbet@lwn.net, Conor.Dooley@microchip.com,
bagasdotme@gmail.com, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, crash-utility@redhat.com,
heinrich.schuchardt@canonical.com, k-hagio-ab@nec.com,
hschauhan@nulltrace.org, yixun.lan@gmail.com
Subject: Re: [PATCH V5 0/2] Support VMCOREINFO export for RISCV64
Date: Mon, 31 Oct 2022 17:17:58 +0800 [thread overview]
Message-ID: <Y1+SxuC8qFWQStSe@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20221026144208.373504-1-xianting.tian@linux.alibaba.com>
On 10/26/22 at 10:42pm, Xianting Tian wrote:
> As disscussed in below patch set, the patch of 'describe VMCOREINFO export in Documentation'
> need to update according to Bagas's comments.
> https://lore.kernel.org/linux-riscv/22AAF52E-8CC8-4D11-99CB-88DE4D113444@kernel.org/
>
> As others patches in above patch set already applied, so this patch set only contains below two
> patches.
>
> ------
> Changes:
> Fix commit message in patch 2: use "Document these RISCV64 exports above" instead of
> "This patch just add the description of VMCOREINFO export for RISCV64."
> V1 -> V2:
> Remove unnecessary overline above header text in patch 2.
> V2 -> V3:
> Fix commit message in patch 1,2;
> Use 'space' instead of 'region' for vmemmap description in patch 2.
> V3 -> V4:
> Remove unnecessary kernel space export:
> KASAN_SHADOW_START ~ KASAN_SHADOW_END,
> ADDRESS_SPACE_END
> V4 -> V5:
> Remove IS_ENABLED() judgement for KERNEL_LINK_ADDR in patch 1.
This series looks good to me, thanks.
Acked-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2022-10-31 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 14:42 [PATCH V5 0/2] Support VMCOREINFO export for RISCV64 Xianting Tian
2022-10-26 14:42 ` [PATCH V5 1/2] RISC-V: Add arch_crash_save_vmcoreinfo support Xianting Tian
2022-11-17 4:15 ` Deepak Gupta
2022-11-17 15:43 ` Guo Ren
2022-10-26 14:42 ` [PATCH V5 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64 Xianting Tian
2022-10-31 9:17 ` Baoquan He [this message]
2022-11-18 0:11 ` [PATCH V5 0/2] Support " Baoquan He
2022-12-03 0:49 ` Palmer Dabbelt
2022-12-03 7:53 ` Guo Ren
2022-12-06 23:05 ` Conor Dooley
2022-12-07 3:34 ` Guo Ren
2022-12-07 8:08 ` Conor Dooley
2022-12-07 9:15 ` Guo Ren
2022-12-03 1:00 ` patchwork-bot+linux-riscv
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=Y1+SxuC8qFWQStSe@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=Conor.Dooley@microchip.com \
--cc=alexandre.ghiti@canonical.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=crash-utility@redhat.com \
--cc=dyoung@redhat.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=hschauhan@nulltrace.org \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vgoyal@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).