From: Rob Herring <robh@kernel.org>
To: "Jan Sebastian Götte" <linux@jaseg.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, keyrings@vger.kernel.org,
linux-mm@kvack.org, linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH 1/4] of/kexec: fix typo in comment (usable-memory-range)
Date: Tue, 11 Aug 2026 08:43:52 -0500 [thread overview]
Message-ID: <20260811134352.GA2054339-robh@kernel.org> (raw)
In-Reply-To: <20260731162739.158320-2-linux@jaseg.de>
On Fri, Jul 31, 2026 at 06:27:36PM +0200, Jan Sebastian Götte wrote:
> Signed-off-by: Jan Sebastian Götte <linux@jaseg.de>
> ---
> drivers/of/kexec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/of/kexec.c b/drivers/of/kexec.c
> index 029903b986cb..36635f6cb900 100644
> --- a/drivers/of/kexec.c
> +++ b/drivers/of/kexec.c
> @@ -24,7 +24,7 @@
>
> /*
> * Additional space needed for the FDT buffer so that we can add initrd,
> - * bootargs, kaslr-seed, rng-seed, useable-memory-range and elfcorehdr.
> + * bootargs, kaslr-seed, rng-seed, usable-memory-range and elfcorehdr.
If we're going to fix it, really it is "linux,usable-memory-range" and
"linux,elfcorehdr".
Rob
next prev parent reply other threads:[~2026-08-11 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 16:27 [PATCH 0/4] CRASH_ZEROIZE: Wipe secrets before kdump Jan Sebastian Götte
2026-07-31 16:27 ` [PATCH 1/4] of/kexec: fix typo in comment (usable-memory-range) Jan Sebastian Götte
2026-08-11 13:43 ` Rob Herring [this message]
2026-07-31 16:27 ` [PATCH 2/4] kexec: add CRASH_ZEROIZE to wipe secrets before kdump Jan Sebastian Götte
2026-07-31 16:35 ` sashiko-bot
2026-07-31 16:27 ` [PATCH 3/4] mm/secretmem: zeroize secret pages " Jan Sebastian Götte
2026-07-31 16:40 ` sashiko-bot
2026-08-11 14:53 ` David Hildenbrand (Arm)
2026-08-11 15:05 ` Jan Sebastian Götte
2026-08-11 15:14 ` David Hildenbrand (Arm)
2026-08-11 15:18 ` Jan Sebastian Götte
2026-07-31 16:27 ` [PATCH 4/4] security/keys: zeroize key payloads " Jan Sebastian Götte
2026-07-31 16:45 ` sashiko-bot
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=20260811134352.GA2054339-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kexec@lists.infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@jaseg.de \
/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