From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, Huang Shijie <shijie@os.amperecomputing.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
patches@amperecomputing.com, cl@linux.com,
Shubhang@os.amperecomputing.com, corbet@lwn.net,
paulmck@kernel.org, akpm@linux-foundation.org,
rostedt@goodmis.org, Neeraj.Upadhyay@amd.com, bp@alien8.de,
ardb@kernel.org, anshuman.khandual@arm.com,
suzuki.poulose@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rdunlap@infradead.org
Subject: Re: [PATCH v7 0/2] arm64: refactor the rodata=xxx
Date: Tue, 16 Sep 2025 22:13:50 +0100 [thread overview]
Message-ID: <175805239499.269424.4665701509938991056.b4-ty@kernel.org> (raw)
In-Reply-To: <20250909033236.4099-1-shijie@os.amperecomputing.com>
On Tue, 09 Sep 2025 11:32:34 +0800, Huang Shijie wrote:
> >From Documentation/admin-guide/kernel-parameters.txt, we know that:
> rodata= [KNL,EARLY]
> on Mark read-only kernel memory as read-only (default).
> off Leave read-only kernel memory writable for debugging.
> full Mark read-only kernel memory and aliases as read-only
> [arm64]
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/2] arm64: refactor the rodata=xxx
(no commit info)
[2/2] arm64/Kconfig: Remove CONFIG_RODATA_FULL_DEFAULT_ENABLED
https://git.kernel.org/arm64/c/bfbbb0d3215f
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-09-16 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 3:32 [PATCH v7 0/2] arm64: refactor the rodata=xxx Huang Shijie
2025-09-09 3:32 ` [PATCH v7 1/2] " Huang Shijie
2025-09-09 4:29 ` Anshuman Khandual
2025-09-09 5:26 ` Shijie Huang
2025-09-09 6:03 ` Anshuman Khandual
2025-09-09 3:32 ` [PATCH v7 2/2] arm64/Kconfig: Remove CONFIG_RODATA_FULL_DEFAULT_ENABLED Huang Shijie
2025-09-16 21:13 ` Will Deacon [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=175805239499.269424.4665701509938991056.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Neeraj.Upadhyay@amd.com \
--cc=Shubhang@os.amperecomputing.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shijie@os.amperecomputing.com \
--cc=suzuki.poulose@arm.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