From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] docs: filesystems: add fs/open.c to api-summary
Date: Fri, 16 Jan 2026 11:40:45 -0700 [thread overview]
Message-ID: <871pjpo0ya.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260104204530.518206-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Include fs/open.c in filesystems/api-summary.rst to provide its
> exported APIs.
>
> Suggested-by: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: linux-fsdevel@vger.kernel.org
>
> Documentation/filesystems/api-summary.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> --- linux-next-20251219.orig/Documentation/filesystems/api-summary.rst
> +++ linux-next-20251219/Documentation/filesystems/api-summary.rst
> @@ -56,6 +56,9 @@ Other Functions
> .. kernel-doc:: fs/namei.c
> :export:
>
> +.. kernel-doc:: fs/open.c
> + :export:
> +
So I've applied this, but it does add a couple of new warnings:
Documentation/filesystems/api-summary:59: ./fs/open.c:1157: WARNING: Inline emphasis start-string without end-string. [docutils]
Documentation/filesystems/api-summary:59: ./fs/open.c:1147: ERROR: Unknown target name: "o". [docutils]
It would be nice to get those fixed up.
Thanks,
jon
next prev parent reply other threads:[~2026-01-16 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 20:45 [PATCH] docs: filesystems: add fs/open.c to api-summary Randy Dunlap
2026-01-06 21:50 ` Christian Brauner
2026-01-16 18:40 ` Jonathan Corbet [this message]
2026-01-16 18:46 ` Randy Dunlap
2026-01-16 19:23 ` Randy Dunlap
2026-01-16 19:27 ` Jonathan Corbet
2026-01-16 22:24 ` Randy Dunlap
2026-01-21 23:26 ` 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=871pjpo0ya.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=brauner@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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