From: Bruce Song <xiongwei.song@linux.dev>
To: Dongliang Mu <dzm91@hust.edu.cn>, alexs@kernel.org, si.yanteng@linux.dev
Cc: corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
paulmck@kernel.org, linux-doc@vger.kernel.org,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] docs/zh_CN: Add RCU/whatisRCU.rst Chinese translation
Date: Tue, 17 Nov 2026 17:48:03 +0800 [thread overview]
Message-ID: <415e7ae2-e7f9-4199-8de4-49819cd2c9e3@linux.dev> (raw)
In-Reply-To: <a96526ff-660b-4c02-85cd-c00b12c483c9@hust.edu.cn>
On 11/16/2026 11:05 PM, Dongliang Mu wrote:
>
> On 11/13/26 9:30 AM, xiongwei.song@linux.dev wrote:
>> From: Xiongwei Song <xiongwei.song@linux.dev>
>>
>> Translate .../RCU/whatisRCU.rst into Chinese.
>>
>> Update the translation through commit b3eb16109ae1
>> ("doc: Update stallwarn.rst based on RCU Tasks Trace as SRCU")
>>
>> Signed-off-by: Xiongwei Song <xiongwei.song@linux.dev>
>
> My sphinx complains about the follows errors and warnings, please double
> check and revise the translation to make sphinx happy :)
>
> Dongliang Mu
>
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:253:
> ERROR: Unknown target name: "1".
>
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:268:
> ERROR: Unknown target name: "2".
>
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:15:
> WARNING: duplicate label whatisrcu_doc
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:77:
> WARNING: duplicate label 1_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:124:
> WARNING: duplicate label 2_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:351:
> WARNING: duplicate label 3_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:435:
> WARNING: duplicate label 4_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:528:
> WARNING: duplicate label 5_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:603:
> WARNING: duplicate label quiz_1
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:650:
> WARNING: duplicate label quiz_2
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:657:
> WARNING: duplicate label quiz_3
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:666:
> WARNING: duplicate label 6_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:788:
> WARNING: duplicate label 7_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:854:
> WARNING: duplicate label 8_whatisrcu
> Documentation/translations/zh_CN/RCU/whatisRCU.rst:1135:
> WARNING: duplicate label 9_whatisrcu
Thank you, Dongliang.
Again, I didn't notice these errors and warnings when building them
myself. I will fix them and resend the patch.
Thanks,
Xiongwei
prev parent reply other threads:[~2026-11-17 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 1:30 [PATCH 0/2] Add RCU docs Chinese translation xiongwei.song
2026-11-13 1:30 ` [PATCH 1/2] docs/zh_CN: Add RCU/index.rst translation xiongwei.song
2026-11-16 14:49 ` Dongliang Mu
2026-11-17 9:44 ` Bruce Song
2026-11-13 1:30 ` [PATCH 2/2] docs/zh_CN: Add RCU/whatisRCU.rst Chinese translation xiongwei.song
2026-11-16 15:05 ` Dongliang Mu
2026-11-17 9:48 ` Bruce Song [this message]
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=415e7ae2-e7f9-4199-8de4-49819cd2c9e3@linux.dev \
--to=xiongwei.song@linux.dev \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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