From: Simon Horman <horms@kernel.org>
To: Chen Jiahao <chenjiahao16@huawei.com>
Cc: 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,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH -next 2/2] docs: kdump: Update the crashkernel description for riscv
Date: Mon, 20 Mar 2023 15:37:14 +0100 [thread overview]
Message-ID: <ZBhvmqlyyvLOUot1@kernel.org> (raw)
In-Reply-To: <20230320204244.1637821-3-chenjiahao16@huawei.com>
On Tue, Mar 21, 2023 at 04:42:44AM +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>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Chen Jiahao <chenjiahao16@huawei.com>
Cc: 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,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH -next 2/2] docs: kdump: Update the crashkernel description for riscv
Date: Mon, 20 Mar 2023 15:37:14 +0100 [thread overview]
Message-ID: <ZBhvmqlyyvLOUot1@kernel.org> (raw)
In-Reply-To: <20230320204244.1637821-3-chenjiahao16@huawei.com>
On Tue, Mar 21, 2023 at 04:42:44AM +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>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Chen Jiahao <chenjiahao16@huawei.com>
Cc: 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,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kexec@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH -next 2/2] docs: kdump: Update the crashkernel description for riscv
Date: Mon, 20 Mar 2023 15:37:14 +0100 [thread overview]
Message-ID: <ZBhvmqlyyvLOUot1@kernel.org> (raw)
In-Reply-To: <20230320204244.1637821-3-chenjiahao16@huawei.com>
On Tue, Mar 21, 2023 at 04:42:44AM +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>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-03-20 14:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 20:42 [PATCH -next 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-03-20 20:42 ` Chen Jiahao
2023-03-20 20:42 ` Chen Jiahao
2023-03-20 20:42 ` [PATCH -next 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-03-20 20:42 ` Chen Jiahao
2023-03-20 20:42 ` Chen Jiahao
2023-03-20 14:36 ` Simon Horman
2023-03-20 14:36 ` Simon Horman
2023-03-20 14:36 ` Simon Horman
2023-03-27 12:50 ` chenjiahao (C)
2023-03-27 12:50 ` chenjiahao (C)
2023-03-27 12:50 ` chenjiahao (C)
2023-03-21 1:42 ` Leizhen (ThunderTown)
2023-03-21 1:42 ` Leizhen (ThunderTown)
2023-03-21 1:42 ` Leizhen (ThunderTown)
2023-03-27 12:54 ` chenjiahao (C)
2023-03-27 12:54 ` chenjiahao (C)
2023-03-27 12:54 ` chenjiahao (C)
2023-03-20 20:42 ` [PATCH -next 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-03-20 20:42 ` Chen Jiahao
2023-03-20 20:42 ` Chen Jiahao
2023-03-20 14:37 ` Simon Horman [this message]
2023-03-20 14:37 ` Simon Horman
2023-03-20 14:37 ` Simon Horman
2023-03-21 1:45 ` Leizhen (ThunderTown)
2023-03-21 1:45 ` Leizhen (ThunderTown)
2023-03-21 1:45 ` Leizhen (ThunderTown)
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=ZBhvmqlyyvLOUot1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.