From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Frederic Barrat <fbarrat@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Andrew Donnellan <ajd@linux.ibm.com>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
Eric Biggers <ebiggers@google.com>,
Nuno Das Neves <nunodasneves@linux.microsoft.com>,
Beau Belgrave <beaub@linux.microsoft.com>,
Jan Kara <jack@suse.cz>, Lukas Bulwahn <lukas.bulwahn@redhat.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH] Documentation: ioctl-number: Update table intro
Date: Thu, 8 May 2025 06:39:04 +0700 [thread overview]
Message-ID: <aBvvGHb3KCpRGU_d@archie.me> (raw)
In-Reply-To: <CAOc5a3OKA-zQQU1pF3T4HT7awEg3JMgD-BYOXbviqMDyZr-__Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
On Wed, May 07, 2025 at 08:34:59AM +0200, Lukas Bulwahn wrote:
> On Wed, May 7, 2025 at 7:52 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> > -This table lists ioctls visible from user land for Linux/x86. It contains
> > -most drivers up to 2.6.31, but I know I am missing some. There has been
> > -no attempt to list non-X86 architectures or ioctls from drivers/staging/.
> > +This table lists ioctls visible from userland for Linux version 6.x+,
> > +excluding ones from drivers/staging/.
>
> It is probably best to avoid mentioning any version information at all.
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-05-07 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 5:51 [PATCH] Documentation: ioctl-number: Update table intro Bagas Sanjaya
2025-05-07 6:34 ` Lukas Bulwahn
2025-05-07 23:39 ` Bagas Sanjaya [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=aBvvGHb3KCpRGU_d@archie.me \
--to=bagasdotme@gmail.com \
--cc=ajd@linux.ibm.com \
--cc=beaub@linux.microsoft.com \
--cc=corbet@lwn.net \
--cc=ebiggers@google.com \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=lbulwahn@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=mchehab+huawei@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nunodasneves@linux.microsoft.com \
--cc=rostedt@goodmis.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