public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Law <hlcj1234567@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Josh Law <objecting@objecting.org>
Subject: [PATCH 3/4] arm64: kernel: Move const after static in get_kaslr_seed
Date: Sun,  1 Mar 2026 00:34:06 +0000	[thread overview]
Message-ID: <20260301003407.2493781-3-objecting@objecting.org> (raw)
In-Reply-To: <20260301003407.2493781-1-objecting@objecting.org>

Signed-off-by: Josh Law <objecting@objecting.org>
---
 arch/arm64/kernel/pi/kaslr_early.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm64/kernel/pi/kaslr_early.c b/arch/arm64/kernel/pi/kaslr_early.c
index e0e018046a46..b1fb950f1564 100644
--- a/arch/arm64/kernel/pi/kaslr_early.c
+++ b/arch/arm64/kernel/pi/kaslr_early.c
@@ -20,7 +20,7 @@
 
 static u64 __init get_kaslr_seed(void *fdt, int node)
 {
-	static char const seed_str[] __initconst = "kaslr-seed";
+	static const char seed_str[] __initconst = "kaslr-seed";
 	fdt64_t *prop;
 	u64 ret;
 	int len;
-- 
2.43.0


  parent reply	other threads:[~2026-03-01  0:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  0:34 [PATCH 1/4] arm64: errata: Fix missing space after comma Josh Law
2026-03-01  0:34 ` [PATCH 2/4] arm64: fpsimd: make stack ctl_table const Josh Law
2026-03-01  0:34 ` Josh Law [this message]
2026-03-01  0:34 ` [PATCH 4/4] arm64: kernel: Fix style in io.c macro Josh Law
2026-03-02 14:51   ` Mark Rutland
2026-03-02 15:45     ` Josh Law
2026-03-02 18:08       ` Mark Rutland
2026-03-02 18:21         ` Josh Law
2026-03-03 11:50 ` [PATCH 1/4] arm64: errata: Fix missing space after comma Will Deacon

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=20260301003407.2493781-3-objecting@objecting.org \
    --to=hlcj1234567@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=objecting@objecting.org \
    --cc=will@kernel.org \
    /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