From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Donnellan <ajd@linux.ibm.com>,
Frederic Barrat <fbarrat@linux.ibm.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Ming Lei <ming.lei@redhat.com>,
Lukas Bulwahn <lukas.bulwahn@redhat.com>,
Alyssa Ross <hi@alyssa.is>,
Beau Belgrave <beaub@linux.microsoft.com>,
Nuno Das Neves <nunodasneves@linux.microsoft.com>,
Eric Biggers <ebiggers@google.com>,
Michael Ellerman <mpe@ellerman.id.au>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2] Documentation: ioctl-number: Update table intro
Date: Mon, 19 May 2025 08:59:29 -0600 [thread overview]
Message-ID: <87y0usir3i.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250508005838.8381-2-bagasdotme@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> Introduction paragraph to the ioctl numbers table states that only
> ioctls in up to ancient Linux kernel version (v2.6.31) for x86 arch are
> listed. This is inaccurate as the table also lists ioctls from non-x86
> archs and the kernel is continously developed (currently in v6.x).
>
> Update the paragraph accordingly.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Changes since v1 [1]:
> - Do not mention kernel version (Lukas)
>
> [1]: https://lore.kernel.org/linux-doc/20250507055145.23345-2-bagasdotme@gmail.com/
>
> Documentation/userspace-api/ioctl/ioctl-number.rst | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2025-05-19 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 0:58 [PATCH v2] Documentation: ioctl-number: Update table intro Bagas Sanjaya
2025-05-19 14:59 ` 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=87y0usir3i.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=ajd@linux.ibm.com \
--cc=bagasdotme@gmail.com \
--cc=beaub@linux.microsoft.com \
--cc=ebiggers@google.com \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hi@alyssa.is \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=ming.lei@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nunodasneves@linux.microsoft.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