From: Al Viro <viro@zeniv.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the vfs tree
Date: Thu, 15 Jan 2026 03:10:53 +0000 [thread overview]
Message-ID: <20260115031053.GY3634291@ZenIV> (raw)
In-Reply-To: <20260115140132.6e0c05a0@canb.auug.org.au>
On Thu, Jan 15, 2026 at 02:01:32PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the vfs tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/filesystems/porting.rst:1348: ERROR: Unknown target name: "filename". [docutils]
>
> Introduced by commit
>
> 7335480a8461 ("non-consuming variant of do_linkat()")
Egads... That's from "filename_{link,renameat2}()" in there (there's also
"do_{link,renameat2}()" earlier in the same line, but that didn't produce
a warning.
Any suggestions re better way to spell it for .rst?
next prev parent reply other threads:[~2026-01-15 3:09 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 3:01 linux-next: build warning after merge of the vfs tree Stephen Rothwell
2026-01-15 3:10 ` Al Viro [this message]
2026-01-15 4:04 ` Stephen Rothwell
2026-01-15 8:28 ` Mauro Carvalho Chehab
2026-01-15 14:57 ` Al Viro
2026-01-16 17:56 ` Al Viro
-- strict thread matches above, loose matches on Subject: below --
2025-09-11 5:23 Stephen Rothwell
2021-04-12 11:47 Stephen Rothwell
2021-04-12 13:07 ` Miklos Szeredi
2021-04-15 21:19 ` Al Viro
2021-01-06 23:15 Stephen Rothwell
2021-01-07 0:37 ` Gao Xiang
2021-01-07 0:40 ` Al Viro
2020-09-24 1:40 Stephen Rothwell
2020-09-24 2:00 ` Al Viro
2020-06-16 0:21 Stephen Rothwell
2020-03-09 22:59 Stephen Rothwell
2020-03-09 23:17 ` Pali Rohár
2020-03-09 23:36 ` Namjae Jeon
2020-03-10 10:32 ` 'Greg Kroah-Hartman'
2019-02-03 22:33 Stephen Rothwell
2019-03-18 0:00 ` Stephen Rothwell
2019-03-25 23:05 ` Stephen Rothwell
2018-09-06 0:02 Stephen Rothwell
2018-09-07 8:57 ` David Howells
2018-06-19 1:53 Stephen Rothwell
2018-06-19 1:29 Stephen Rothwell
2018-05-17 0:39 Stephen Rothwell
2018-05-17 6:41 ` Christoph Hellwig
2018-05-14 0:56 Stephen Rothwell
2017-09-07 23:25 Stephen Rothwell
2017-09-08 5:53 ` Dmitry V. Levin
2017-09-14 1:51 ` Stephen Rothwell
2017-07-03 0:53 Stephen Rothwell
2017-07-09 23:34 ` Stephen Rothwell
2015-04-13 4:00 Stephen Rothwell
2012-10-12 5:06 Stephen Rothwell
2012-09-25 1:52 Stephen Rothwell
2012-01-05 6:35 Stephen Rothwell
2012-01-05 8:06 ` Al Viro
2012-01-05 8:14 ` Al Viro
2012-01-05 11:34 ` Jan Kara
2012-01-05 8:14 ` Stephen Rothwell
2012-01-05 8:19 ` Al Viro
2011-07-18 5:04 Stephen Rothwell
2011-07-18 5:17 ` Al Viro
2011-07-18 5:20 ` Al Viro
2010-07-05 0:01 Stephen Rothwell
2010-07-05 8:10 ` Al Viro
2010-07-05 10:44 ` Stephen Rothwell
2010-07-05 12:15 ` Jeff Layton
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=20260115031053.GY3634291@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.