From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Kees Cook <kees@kernel.org>,
Jinbum Park <jinb.park7@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Fix DEBUG_RODATA_TEST indentation in Kconfig
Date: Tue, 25 Nov 2025 16:20:26 +0530 [thread overview]
Message-ID: <44c43197-e881-458e-837e-2aec673aaf97@arm.com> (raw)
In-Reply-To: <74f39b1bffc6ed802088cb3e7d17b4c82330e8b3.1764058676.git.geert@linux-m68k.org>
On 25/11/25 1:49 PM, Geert Uytterhoeven wrote:
> Most of the DEBUG_RODATA_TEST section is indented by four spaces instead
> of the customary single TAB.
>
> Fixes: 2959a5f726f6510d ("mm: add arch-independent testcases for RODATA")
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> mm/Kconfig.debug | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/Kconfig.debug b/mm/Kconfig.debug
> index 32b65073d0cccaf5..7638d75b27db8cf1 100644
> --- a/mm/Kconfig.debug
> +++ b/mm/Kconfig.debug
> @@ -175,10 +175,10 @@ config DEBUG_PAGE_REF
> nil until the tracepoints are actually enabled.
>
> config DEBUG_RODATA_TEST
> - bool "Testcase for the marking rodata read-only"
> - depends on STRICT_KERNEL_RWX
> + bool "Testcase for the marking rodata read-only"
> + depends on STRICT_KERNEL_RWX
> help
> - This option enables a testcase for the setting rodata read-only.
> + This option enables a testcase for the setting rodata read-only.
>
> config ARCH_HAS_DEBUG_WX
> bool
prev parent reply other threads:[~2025-11-25 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 8:19 Geert Uytterhoeven
2025-11-25 10:14 ` Mike Rapoport
2025-11-25 10:50 ` Anshuman Khandual [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=44c43197-e881-458e-837e-2aec673aaf97@arm.com \
--to=anshuman.khandual@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jinb.park7@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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