From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wang Qing <wangqing@vivo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the jc_docs tree
Date: Mon, 14 Dec 2020 13:17:42 -0700 [thread overview]
Message-ID: <20201214131742.20d2252f@lwn.net> (raw)
In-Reply-To: <20201215065143.65ccf365@canb.auug.org.au>
On Tue, 15 Dec 2020 06:51:43 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Mon, 16 Nov 2020 17:03:03 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the jc_docs tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/translations/zh_CN/filesystems/tmpfs.rst:5: WARNING: undefined label: tmpfs_index (if the link has no caption the label must precede a section header)
> >
> > Introduced by commit
> >
> > 09028e60fcea ("doc: zh_CN: add translatation for tmpfs")
>
> I am still getting this warning.
OK, enough of that; I've just tacked on the following patch to address
this problem, thanks for the report.
Thanks,
jon
From 47e44ed01434e51e2e42b188482d837c01e5d16e Mon Sep 17 00:00:00 2001
From: Jonathan Corbet <corbet@lwn.net>
Date: Mon, 14 Dec 2020 13:14:22 -0700
Subject: [PATCH] docs: fix broken cross reference in translations/zh_CN
Commit 09028e60fcea ("doc: zh_CN: add translatation for tmpfs") introduced
a cross reference without adding the appropriate target tag, leading to
this docs-build warning:
Documentation/translations/zh_CN/filesystems/tmpfs.rst:5: WARNING: undefined label: tmpfs_index (if the link has no caption the label must precede a section header)
With automarkup, we don't actually need an explicit reference here at all,
so just take it out.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Fixes: 09028e60fcea ("doc: zh_CN: add translatation for tmpfs")
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---
Documentation/translations/zh_CN/filesystems/tmpfs.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/zh_CN/filesystems/tmpfs.rst b/Documentation/translations/zh_CN/filesystems/tmpfs.rst
index cf3ccab20e50..6fd9d83b2db5 100644
--- a/Documentation/translations/zh_CN/filesystems/tmpfs.rst
+++ b/Documentation/translations/zh_CN/filesystems/tmpfs.rst
@@ -2,7 +2,7 @@
.. include:: ../disclaimer-zh_CN.rst
-:Original: :ref:`Documentation/filesystems/tmpfs.rst <tmpfs_index>`
+:Original: Documentation/filesystems/tmpfs.rst
translated by Wang Qing<wangqing@vivo.com>
--
2.28.0
next prev parent reply other threads:[~2020-12-14 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 6:03 linux-next: build warning after merge of the jc_docs tree Stephen Rothwell
2020-12-14 19:51 ` Stephen Rothwell
2020-12-14 20:17 ` Jonathan Corbet [this message]
2020-12-07 7:52 Stephen Rothwell
2021-01-13 4:07 Stephen Rothwell
2021-01-13 23:27 ` Jonathan Corbet
2021-01-21 2:07 ` 司延腾
2021-01-21 18:30 ` Jonathan Corbet
2021-01-13 4:12 Stephen Rothwell
2021-01-13 4:18 ` Stephen Rothwell
2021-01-13 4:14 Stephen Rothwell
2021-02-23 5:19 Stephen Rothwell
2023-12-18 7:28 Stephen Rothwell
2023-12-18 14:18 ` Jonathan Corbet
2023-12-19 23:59 ` Randy Dunlap
2023-12-20 0:02 ` Jonathan Corbet
2023-12-20 0:04 ` 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=20201214131742.20d2252f@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wangqing@vivo.com \
/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).