From: Hans Holmberg <Hans.Holmberg@wdc.com>
To: Carlos Maiolino <cem@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
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 xfs tree
Date: Tue, 22 Apr 2025 11:38:58 +0000 [thread overview]
Message-ID: <0e636a46-623c-495c-a897-23b6c6aa9336@wdc.com> (raw)
In-Reply-To: <huc7jw3retrx5i2szvngci23vwh6z5ve5a4oiyjvjewg4d5ien@2h2j3qpgkk3c>
On 22/04/2025 12:46, Carlos Maiolino wrote:
> On Tue, Apr 22, 2025 at 08:25:17PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the xfs tree, today's linux-next build (htmldocs) produced
>> this warning:
>>
>> Documentation/admin-guide/xfs.rst:576: WARNING: duplicate label admin-guide/xfs:zoned filesystems, other instance in Documentation/admin-guide/xfs.rst [autosectionlabel.admin-guide/xfs]
>>
>> Introduced by commit
>>
>> c7b67ddc3c99 ("xfs: document zoned rt specifics in admin-guide")
>>
>
> Thanks, I'll take a look into it
Looks like the Zoned Filesystems section was duplicated when applying
the two documentation patches. I can send a cleanup patch.
next prev parent reply other threads:[~2025-04-22 11:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <95VzqAdwXL6uADPxQWGQV9LD2OtK9bUX7if_opYIYTcdIroqe7176LhnAst-sIYFTfU2tgwJknumIwzvYvxyTQ==@protonmail.internalid>
2025-04-22 10:25 ` linux-next: build warning after merge of the xfs tree Stephen Rothwell
2025-04-22 10:46 ` Carlos Maiolino
2025-04-22 11:38 ` Hans Holmberg [this message]
[not found] <D20pUU7kdgWfIpAYmLR776cP2sU4_NhTrc4Fasx5DbMewO7J6UW6QX_81athF3DSSPP2tZiEZNid_Rlin4p6lw==@protonmail.internalid>
2025-09-08 8:04 ` Stephen Rothwell
2025-09-16 10:22 ` Carlos Maiolino
2024-02-23 4:36 Stephen Rothwell
2024-02-23 6:35 ` Christoph Hellwig
2024-02-23 8:55 ` Mauro Carvalho Chehab
2024-02-23 14:06 ` Christoph Hellwig
2024-02-24 9:07 ` Akira Yokosawa
2024-02-26 10:57 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 0:48 Stephen Rothwell
2021-06-07 1:15 ` Dave Chinner
2021-02-08 12:44 Stephen Rothwell
2021-01-24 22:55 Stephen Rothwell
2021-01-25 13:26 ` Brian Foster
2021-01-27 3:14 ` Darrick J. Wong
2020-05-08 1:15 Stephen Rothwell
2020-01-16 0:37 Stephen Rothwell
2020-01-15 22:12 Stephen Rothwell
2020-01-24 2:47 ` Stephen Rothwell
2020-01-24 4:17 ` Darrick J. Wong
2017-10-31 22:42 Stephen Rothwell
2017-08-31 0:07 Stephen Rothwell
2017-08-31 10:30 ` Brian Foster
2017-08-31 14:57 ` Darrick J. Wong
2017-08-31 15:22 ` Brian Foster
2017-08-31 15:41 ` Darrick J. Wong
2017-08-31 21:32 ` Dave Chinner
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=0e636a46-623c-495c-a897-23b6c6aa9336@wdc.com \
--to=hans.holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).