From: Alex Shi <alex.shi@linux.alibaba.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: Harry Wei <harryxiyou@gmail.com>,
Wang Wenhu <wenhu.wang@vivo.com>,
Chucheng Luo <luochucheng@vivo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: zh_CN: use doc reference to resolve undefined label warning
Date: Wed, 3 Jun 2020 15:36:11 +0800 [thread overview]
Message-ID: <67729261-8deb-c1f4-979c-762786ab1954@linux.alibaba.com> (raw)
In-Reply-To: <20200531183556.5751-1-lukas.bulwahn@gmail.com>
在 2020/6/1 上午2:35, Lukas Bulwahn 写道:
> Documentation generation warns:
>
> Documentation/translations/zh_CN/filesystems/debugfs.rst:5:
> WARNING: undefined label: debugfs_index
It's due to debugfs.txt changed to debugfs.rst.
>
> Use doc reference for files rather than introducing a label to refer to.
> This resolves the warning above.
Anyway this fix is also fine for me.
Reviewed-by: Alex Shi <alex.shi@linux.alibaba.com>
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Jonathan, please pick this quick warning fix.
>
> applies on your doc-next and next-20200529
>
> Documentation/translations/zh_CN/filesystems/debugfs.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/filesystems/debugfs.rst b/Documentation/translations/zh_CN/filesystems/debugfs.rst
> index f8a28793c277..822c4d42fdf9 100644
> --- a/Documentation/translations/zh_CN/filesystems/debugfs.rst
> +++ b/Documentation/translations/zh_CN/filesystems/debugfs.rst
> @@ -2,7 +2,7 @@
>
> .. include:: ../disclaimer-zh_CN.rst
>
> -:Original: :ref:`Documentation/filesystems/debugfs.txt <debugfs_index>`
> +:Original: :doc:`../../../filesystems/debugfs`
>
> =======
> Debugfs
>
next prev parent reply other threads:[~2020-06-03 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 18:35 Lukas Bulwahn
2020-06-03 7:36 ` Alex Shi [this message]
2020-06-08 15:25 ` Jonathan Corbet
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=67729261-8deb-c1f4-979c-762786ab1954@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=luochucheng@vivo.com \
--cc=wenhu.wang@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
all inboxes | Powered by JetHome®