From: patchwork-bot+linux-riscv@kernel.org
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: linux-riscv@lists.infradead.org, punit.agrawal@bytedance.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
chenjiahao16@huawei.com, guoren@kernel.org,
vishal.moola@gmail.com, stuart.menefy@codasip.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: add a warning when physical memory address overflows
Date: Thu, 30 Jan 2025 14:10:40 +0000 [thread overview]
Message-ID: <173824624099.971083.29484788191658517.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240814062625.19794-1-cuiyunhui@bytedance.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 14 Aug 2024 14:26:25 +0800 you wrote:
> The part of physical memory that exceeds the size of the linear mapping
> will be discarded. When the system starts up normally, a warning message
> will be printed to prevent confusion caused by the mismatch between the
> system memory and the actual physical memory.
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
>
> [...]
Here is the summary with links:
- riscv: add a warning when physical memory address overflows
https://git.kernel.org/riscv/c/101971298be2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-30 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 6:26 [PATCH] riscv: add a warning when physical memory address overflows Yunhui Cui
2024-08-15 11:01 ` Alexandre Ghiti
2024-09-18 3:49 ` [External] " yunhui cui
2024-10-23 14:25 ` Punit Agrawal
2025-02-03 15:59 ` Palmer Dabbelt
2025-01-30 14:10 ` patchwork-bot+linux-riscv [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=173824624099.971083.29484788191658517.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=chenjiahao16@huawei.com \
--cc=cuiyunhui@bytedance.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=punit.agrawal@bytedance.com \
--cc=stuart.menefy@codasip.com \
--cc=vishal.moola@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