From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 03/12] docs: ioctl-number: update block entries
Date: Wed, 18 Nov 2026 21:04:28 -0800 [thread overview]
Message-ID: <20261119050444.249752-4-rdunlap@infradead.org> (raw)
In-Reply-To: <20261119050444.249752-1-rdunlap@infradead.org>
Update the list of files where block ioctls are defined.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
v2: no change
[Since having multiple maintainers trying to merge these would
cause some conflicts, it would be more manageable for Jon to
take all of these through the docs-next tree.]
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Documentation/userspace-api/ioctl/ioctl-number.rst | 4 ++++
1 file changed, 4 insertions(+)
--- linux-next-20261116.orig/Documentation/userspace-api/ioctl/ioctl-number.rst
+++ linux-next-20261116/Documentation/userspace-api/ioctl/ioctl-number.rst
@@ -78,6 +78,7 @@ Code Seq# Include File
0x00 00-1F linux/fb.h conflict!
0x00 00-1F linux/wavefront.h conflict!
0x02 all linux/fd.h
+ drivers/block/floppy.c
0x03 all linux/hdreg.h
0x04 D2-DC linux/umsdos_fs.h Dead since 2.6.11, but don't reuse these.
0x06 all linux/lp.h
@@ -90,6 +91,9 @@ Code Seq# Include File
linux/blkpg.h
linux/blkzoned.h
linux/blk-crypto.h
+ linux/blkdev.h
+ linux/blktrace_api.h
+ block/ioctl.c
0x15 all linux/fs.h FS_IOC_* ioctls
0x1b all InfiniBand Subsystem
<http://infiniband.sourceforge.net/>
next prev parent reply other threads:[~2026-11-19 5:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 5:04 [PATCH v2 00/12] docs: ioctl-number: update entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 01/12] docs: ioctl-number: update MM entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 02/12] docs: ioctl-number: update sound entries Randy Dunlap
2026-11-19 5:04 ` Randy Dunlap [this message]
2026-11-19 5:04 ` [PATCH v2 04/12] docs: ioctl-number: update networking entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 05/12] docs: ioctl-number: update video/fbdev entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 06/12] docs: ioctl-number: update SCSI entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 07/12] docs: ioctl-number: update MTD entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 08/12] docs: ioctl-number: update USB entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 09/12] docs: ioctl-number: update virtualization entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 10/12] docs: ioctl-number: update FS entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 11/12] docs: ioctl-number: update platform entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 12/12] docs: ioctl-number: update DRM entries Randy Dunlap
2026-11-19 5:35 [PATCH v2 00/12 RESEND] docs: ioctl-number: update entries Randy Dunlap
2026-11-19 5:35 ` [PATCH v2 03/12] docs: ioctl-number: update block entries Randy Dunlap
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=20261119050444.249752-4-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®