From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: 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 12:27:25 -0700 [thread overview]
Message-ID: <87wm1hmk82.fsf@trenco.lwn.net> (raw)
In-Reply-To: <c7d47b56-2d37-4893-b8ec-1fb23f75a55e@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Seems I was confused with fs/namei.c, where I see similar warnings.
> I don't see those warnings in fs/open.c.
>
> I'm using today's linux-next tree, where the latest change to
> fs/open.c is:
> ommit 750d2f1f7b5c
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Sun Dec 14 03:13:59 2025 -0500
> chroot(2): switch to CLASS(filename)
>
> Do you have something later (newer) than that?
>
> Also, at fs/open.c lines 1147-1157, I don't see anything that would
> cause docs warnings.
No, docs-next is older - based on -rc2. It seems that linux-next has
significantly thrashed thing there, and the offending function
(dentry_create()) moved to namei.c...
jon
next prev parent reply other threads:[~2026-01-16 19:27 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
2026-01-16 18:46 ` Randy Dunlap
2026-01-16 19:23 ` Randy Dunlap
2026-01-16 19:27 ` Jonathan Corbet [this message]
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=87wm1hmk82.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