From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lbulwahn@redhat.com>, linux-doc@vger.kernel.org
Cc: linux-snps-arc@lists.infradead.org, linux-parisc@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-um@lists.infradead.org,
linux-openrisc@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] Documentation/features: Update feature lists for 6.17-rc7
Date: Thu, 25 Sep 2025 11:18:31 -0600 [thread overview]
Message-ID: <87qzvu30yg.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250925073634.112142-1-lukas.bulwahn@redhat.com>
Lukas Bulwahn <lbulwahn@redhat.com> writes:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> It seems that ./Documentation/features/scripts/features-refresh.sh was most
> recently used in December 2022, with the latest kernel release v6.1-rc7 at
> that time (see commit 7f2e60ff51ca ("Documentation/features: Update feature
> lists for 6.1") to update the feature lists in this subdirectory. All
> further changes to Documentation/features/ since then have probably been
> done manually, without checking for changes in other architectures and
> features, that missed to update this part of the documentation.
>
> Running ./Documentation/features/scripts/features-refresh.sh now showed
> seven changes of supported features in various architectures (one in arc,
> two in parisc, one in riscv, one in openrisc, and two in um), which were
> not reflected yet in the current documentation.
>
> To confirm the sanity of this script's suggested changes, I checked if the
> commit messages confirm that the features have in fact been added in the
> following commits:
>
> - commit f122668ddcce ("ARC: Add eBPF JIT support")
> - commit 4800a6215e33 ("parisc: Wire up eBPF JIT compiler")
> - commit a869b8c29f86 ("riscv: enable mseal sysmap for RV64")
> - commit 2f681ba4b352 ("um: move thread info into task")
> - commit 3f17fed21491 ("um: switch to regset API and depend on XSTATE")
> - commit 7ce8716e2769 ("openrisc: Add HAVE_REGS_AND_STACK_ACCESS_API support")
> - commit b5ff52be8913 ("parisc: Convert to generic clockevents")
>
> So, update all documents to the current state with features-refresh.sh.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> ---
> Documentation/features/core/eBPF-JIT/arch-support.txt | 4 ++--
> .../features/core/mseal_sys_mappings/arch-support.txt | 2 +-
> .../features/core/thread-info-in-task/arch-support.txt | 2 +-
> Documentation/features/core/tracehook/arch-support.txt | 2 +-
> Documentation/features/perf/kprobes-event/arch-support.txt | 2 +-
> Documentation/features/time/clockevents/arch-support.txt | 2 +-
> 6 files changed, 7 insertions(+), 7 deletions(-)
OK, I went ahead and applied this one, thanks.
jon
prev parent reply other threads:[~2025-09-25 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 7:36 [PATCH] Documentation/features: Update feature lists for 6.17-rc7 Lukas Bulwahn
2025-09-25 17:18 ` Jonathan Corbet [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=87qzvu30yg.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=lukas.bulwahn@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).