From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 01/12] docs: ioctl-number: update MM entries
Date: Wed, 18 Nov 2026 21:04:26 -0800 [thread overview]
Message-ID: <20261119050444.249752-2-rdunlap@infradead.org> (raw)
In-Reply-To: <20261119050444.249752-1-rdunlap@infradead.org>
Add ioctl number entries for test_hmm_uapi and gup_test.
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: David Hildenbrand <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>
Cc: linux-mm@kvack.org
Documentation/userspace-api/ioctl/ioctl-number.rst | 4 ++++
1 file changed, 4 insertions(+)
--- linux-next-20261111.orig/Documentation/userspace-api/ioctl/ioctl-number.rst
+++ linux-next-20261111/Documentation/userspace-api/ioctl/ioctl-number.rst
@@ -147,6 +147,8 @@ Code Seq# Include File
'G' 00-0F xen/gntalloc.h, xen/gntdev.h conflict!
'H' 00-7F linux/hiddev.h conflict!
'H' 00-0F linux/hidraw.h conflict!
+'H' 00-0F lib/test_hmm_uapi.h conflict!
+ <mailto:linux-mm@kvack.org>
'H' 01 linux/mei.h conflict!
'H' 02 linux/mei.h conflict!
'H' 03 linux/mei.h conflict!
@@ -252,6 +254,8 @@ Code Seq# Include File
'f' 81-8F linux/fsverity.h
'g' 00-0F linux/usb/gadgetfs.h
'g' 20-2F linux/usb/g_printer.h
+'g' 01-0F mm/gup_test.h conflict!
+ <mailto:linux-mm@kvack.org>
'h' 00-7F conflict! Charon filesystem
<mailto:zapman@interlan.net>
'h' 00-1F linux/hpet.h conflict!
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 ` Randy Dunlap [this message]
2026-11-19 5:04 ` [PATCH v2 02/12] docs: ioctl-number: update sound entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 03/12] docs: ioctl-number: update block entries Randy Dunlap
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 01/12] docs: ioctl-number: update MM 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-2-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®