[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <26810115-1325-faf2-0f6e-0d7ff164982d@gmail.com>
Date: Thu, 20 Oct 2022 08:56:32 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Xianting Tian <xianting.tian@...ux.alibaba.com>,
paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, anup@...infault.org, heiko@...ech.de,
guoren@...nel.org, mick@....forth.gr,
alexandre.ghiti@...onical.com, bhe@...hat.com, vgoyal@...hat.com,
dyoung@...hat.com, corbet@....net, Conor.Dooley@...rochip.com,
k-hagio-ab@....com, lijiang@...hat.com
Cc: kexec@...ts.infradead.org, linux-doc@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
crash-utility@...hat.com, heinrich.schuchardt@...onical.com,
hschauhan@...ltrace.org, yixun.lan@...il.com
Subject: Re: [PATCH V4 2/2] Documentation: kdump: describe VMCOREINFO export
for RISCV64
On 10/19/22 17:36, Xianting Tian wrote:
> The following interrelated definitions and ranges are needed by the kdump
> crash tool, which are exported by "arch/riscv/kernel/crash_core.c":
> VA_BITS,
> PAGE_OFFSET,
> phys_ram_base,
> KERNEL_LINK_ADDR,
> MODULES_VADDR ~ MODULES_END,
> VMALLOC_START ~ VMALLOC_END,
> VMEMMAP_START ~ VMEMMAP_END,
>
> Document these RISCV64 exports above.
>
> Signed-off-by: Xianting Tian <xianting.tian@...ux.alibaba.com>
Hi Xianting,
Seems like you forgot to keep carrying my Reviewed-by from v3 [1].
Anyway, here it goes...
Reviewed-by: Bagas Sanjaya <bagasdotme@...il.com>
Thanks.
[1]: https://lore.kernel.org/linux-doc/20221018081755.6214-3-xianting.tian@linux.alibaba.com/
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists