public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, alex@ghiti.fr, mick@ics.forth.gr,
	bjorn@rivosinc.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH fixes] riscv: Properly export reserved regions in /proc/iomem
Date: Wed, 16 Apr 2025 18:42:30 +0000	[thread overview]
Message-ID: <174482895074.3460781.13932594280682555131.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250409182129.634415-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Wed,  9 Apr 2025 20:21:27 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> The /proc/iomem represents the kernel's memory map. Regions marked
> with "Reserved" tells the user that the range should not be tampered
> with. Kexec-tools, when using the older kexec_load syscall relies on
> the "Reserved" regions to build the memory segments, that will be the
> target of the new kexec'd kernel.
> 
> [...]

Here is the summary with links:
  - [fixes] riscv: Properly export reserved regions in /proc/iomem
    https://git.kernel.org/riscv/c/e94eb7ea6f20

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2025-04-16 18:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 18:21 [PATCH fixes] riscv: Properly export reserved regions in /proc/iomem Björn Töpel
2025-04-11 10:28 ` Alexandre Ghiti
2025-04-16 18:42 ` patchwork-bot+linux-riscv [this message]
2025-06-30 11:21 ` [PATCH 0/1] Fix for riscv vmcore issue Pnina Feder
2025-06-30 13:33   ` Björn Töpel
2025-07-03 12:06     ` Pnina Feder
2025-07-04 12:25       ` Alexandre Ghiti
2025-07-06 13:57         ` Pnina Feder
2025-07-14 12:00           ` Pnina Feder
2025-07-16  6:58             ` Alexandre Ghiti
2025-07-16 11:05               ` Pnina Feder
2025-07-16 11:47                 ` Alexandre Ghiti
2025-07-16 18:16                   ` Nick Kossifidis
2025-06-30 11:21 ` [PATCH 1/1] riscv: Change memblock reserved name to be recognized on kexec Pnina Feder

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=174482895074.3460781.13932594280682555131.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=alex@ghiti.fr \
    --cc=bjorn@rivosinc.com \
    --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 \
    /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