From: Jonathan Corbet <corbet@lwn.net>
To: "Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>,
"Bartosz Golaszewski" <brgl@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, "Mickaël Salaün" <mic@digikod.net>,
"Jason Wang" <jasowangio@gmail.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
Subject: Re: [PATCH 0/7] docs/abi: align userspace documentation with implementation
Date: Tue, 15 Sep 2026 13:47:13 -0600 [thread overview]
Message-ID: <87mrti70vy.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260831143125.151360-1-ivanrwcm25@gmail.com>
Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com> writes:
> Documentation and ABI alignment fixes found on v7.3-rc1 by comparing
> userspace-api docs, kernel-doc blocks, and uapi headers against the
> current implementation.
>
> Patches 1-6 are documentation only. Patch 7 makes GPIO v2 return
> -EOPNOTSUPP when EVENT_CLOCK_HTE is requested but no HTE provider is
> available, matching the documented behaviour.
>
> No functional ABI changes are intended beyond the GPIO errno correction.
>
> Iván Ezequiel Rodriguez (7):
> docs: futex2: fix documented errno names for futex_waitv
> docs: landlock: fix ENOMSG condition in create_ruleset kernel-doc
> docs: gpio: note lineinfo padding must be zero filled
> docs: dma-buf-heaps: fix CMA heap name typo
> docs: vduse: align documentation with current uapi and driver
> docs: ioctl: fix stale NVMe registry entry and note N conflict
I have applied the series...
> gpio: cdev: return EOPNOTSUPP when HTE is unavailable
...minus this patch.
> Documentation/userspace-api/dma-buf-heaps.rst | 2 +-
> Documentation/userspace-api/futex2.rst | 4 +--
> .../userspace-api/ioctl/ioctl-number.rst | 5 +--
> Documentation/userspace-api/vduse.rst | 33 ++++++++++++-------
> drivers/gpio/gpiolib-cdev.c | 2 ++
> include/uapi/linux/gpio.h | 2 +-
> security/landlock/syscalls.c | 2 +-
> 7 files changed, 31 insertions(+), 19 deletions(-)
I do have a comment on patch 5 that I'll send separately, though.
Did you write these yourself, or was there an LLM involved? In the
latter case, these patches really needed Assisted-by tags as well.
Thanks,
jon
prev parent reply other threads:[~2026-09-15 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:31 Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 1/7] docs: futex2: fix documented errno names for futex_waitv Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 2/7] docs: landlock: fix ENOMSG condition in create_ruleset kernel-doc Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 3/7] docs: gpio: note lineinfo padding must be zero filled Iván Ezequiel Rodriguez
2026-09-01 8:24 ` Bartosz Golaszewski
2026-08-31 14:31 ` [PATCH 4/7] docs: dma-buf-heaps: fix CMA heap name typo Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 5/7] docs: vduse: align documentation with current uapi and driver Iván Ezequiel Rodriguez
2026-09-15 19:48 ` Jonathan Corbet
2026-08-31 14:31 ` [PATCH 6/7] docs: ioctl: fix stale NVMe registry entry and note N conflict Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 7/7] gpio: cdev: return EOPNOTSUPP when HTE is unavailable Iván Ezequiel Rodriguez
2026-09-01 8:25 ` [PATCH 0/7] docs/abi: align userspace documentation with implementation Bartosz Golaszewski
2026-09-15 19:47 ` 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=87mrti70vy.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=brgl@kernel.org \
--cc=ivanrwcm25@gmail.com \
--cc=jasowangio@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=sumit.semwal@linaro.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®