From: Simon Horman <horms@kernel.org>
To: Chen Jiahao <chenjiahao16@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
conor.dooley@microchip.com, guoren@kernel.org, heiko@sntech.de,
bjorn@rivosinc.com, alex@ghiti.fr, akpm@linux-foundation.org,
atishp@rivosinc.com, bhe@redhat.com, thunder.leizhen@huawei.com
Subject: Re: [PATCH -next v3 2/2] docs: kdump: Update the crashkernel description for riscv
Date: Fri, 7 Apr 2023 14:04:15 +0200 [thread overview]
Message-ID: <ZDAGv7dMyirW9aqd@kernel.org> (raw)
In-Reply-To: <20230406220206.3067006-3-chenjiahao16@huawei.com>
On Fri, Apr 07, 2023 at 06:02:06AM +0800, Chen Jiahao wrote:
> Now "crashkernel=" parameter on riscv has been updated to support
> crashkernel=X,[high,low]. Through which we can reserve memory region
> above/within 32bit addressible DMA zone.
>
> Here update the parameter description accordingly.
>
> Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-04-07 12:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 22:02 [PATCH -next v3 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-04-06 22:02 ` [PATCH -next v3 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-04-07 9:06 ` Guo Ren
2023-04-07 12:03 ` Simon Horman
2023-04-11 1:38 ` Guo Ren
2023-04-07 12:03 ` Simon Horman
2023-04-07 12:58 ` Leizhen (ThunderTown)
2023-04-08 2:00 ` Leizhen (ThunderTown)
2023-04-10 9:52 ` chenjiahao (C)
2023-04-10 9:20 ` chenjiahao (C)
2023-04-06 22:02 ` [PATCH -next v3 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-04-07 8:34 ` Guo Ren
2023-04-07 12:04 ` Simon Horman [this message]
2023-04-08 2:01 ` Leizhen (ThunderTown)
2023-04-07 12:05 ` [PATCH -next v3 0/2] support allocating crashkernel above 4G explicitly on riscv Simon Horman
2023-04-10 10:02 ` chenjiahao (C)
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=ZDAGv7dMyirW9aqd@kernel.org \
--to=horms@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=atishp@rivosinc.com \
--cc=bhe@redhat.com \
--cc=bjorn@rivosinc.com \
--cc=chenjiahao16@huawei.com \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=thunder.leizhen@huawei.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).