From: Leon Hwang <leon.hwang@linux.dev>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-mm@kvack.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Nathan Chancellor <nathan@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Miguel Ojeda <ojeda@kernel.org>, Nicolas Schier <nsc@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Douglas Anderson <dianders@chromium.org>,
Gary Guo <gary@garyguo.net>, Anand Moon <linux.amoon@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] mm/mseal: fix mseal documentation for 32-bit kernels
Date: Tue, 7 Jul 2026 21:50:31 +0800 [thread overview]
Message-ID: <dd21ee9a-a7a9-46a2-b151-0f5c486772bd@linux.dev> (raw)
In-Reply-To: <20260707122827-2d6c18d3-8e02-4d9a-bb29-2ec46e759645@linutronix.de>
On 2026/7/7 18:34, Thomas Weißschuh wrote:
> On Fri, Jul 03, 2026 at 11:09:55PM +0800, Leon Hwang wrote:
>> On 2026/7/3 17:44, Thomas Weißschuh wrote:
>>> On Fri, Jul 03, 2026 at 10:25:07AM +0800, Leon Hwang wrote:
>>> (...)
>>>
>>>> The following architectures currently support this feature: x86-64, arm64,
>>>> - loongarch and s390.
>>>> + loongarch, riscv, and s390.
>>>
>>> For per-architecture feature documentation we also have
>>> Documentation/features/. Maybe move it there.
>>
>> Better to replace with a reference to the feature doc?
>>
>> + Refer to :doc:`features/core/mseal_sys_mappings/arch-support` for the
>> + support status of each architecture.
>
> It should automatically show up here:
> https://www.kernel.org/doc/html/latest/admin-guide/features.html
>
> See also Documentation/sphinx/kernel_feat.py
>
> So I don't think an explicit link is necessary.
> But the maintainers might disagree.
> In my opinion the link should then go to the rendered table entry.
>
Let us drop the sentence following Pedro's suggestion.
Thanks,
Leon
next prev parent reply other threads:[~2026-07-07 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 2:25 [PATCH] mm/mseal: fix mseal documentation for 32-bit kernels Leon Hwang
2026-07-03 9:30 ` Lance Yang
2026-07-03 9:44 ` Thomas Weißschuh
2026-07-03 15:09 ` Leon Hwang
2026-07-07 10:34 ` Thomas Weißschuh
2026-07-07 13:50 ` Leon Hwang [this message]
2026-07-03 9:44 ` Pedro Falcato
2026-07-03 14:50 ` Leon Hwang
2026-07-07 10:01 ` Pedro Falcato
2026-07-07 13:48 ` Leon Hwang
2026-07-04 0:39 ` Matthew Wilcox
2026-07-06 1:42 ` Leon Hwang
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=dd21ee9a-a7a9-46a2-b151-0f5c486772bd@linux.dev \
--to=leon.hwang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=gary@garyguo.net \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--cc=ljs@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pfalcato@suse.de \
--cc=pjw@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=vbabka@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