From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation
Date: Fri, 21 Aug 2026 15:22:20 +0800 [thread overview]
Message-ID: <aof8rCuuwzHUNtka@wyuan.org> (raw)
In-Reply-To: <5b107aad-2826-4bf6-97aa-14592131b6a8@hust.edu.cn>
On Fri, Aug 21, 2026 at 02:54:59PM +0800, Dongliang Mu wrote:
>
> On 8/21/26 1:13 AM, Weijie Yuan wrote:
> > The script says:
> >
> > $ tools/docs/checktransupdate.py Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
> > [1787244823.341547] Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
> > [1787244823.630509] commit 54857c52452a ("docs: maintainer-pgp-guide.rst: add a reference for kernel.org sign")
> > [1787244823.680849] commit 6c5c07bc8589 ("docs: process: maintainer-pgp-guide: update kernel.org docs link")
> > [1787244823.730027] commit 273aa250f138 ("Documentation: Improve wording on requirements for a free Nitrokey")
> > [1787244823.779408] commit f44a29784f68 ("Documentation: update maintainer-pgp-guide for latest best practices")
> > [1787244823.779522] 4 commits needs resolving in total
> >
> > So I updated this document in chronological order, created four patches
> > based on these four outdated commits to make it easier for you to
> > review. Hence, you can freely squash them when applying them.
> >
> > Tested with make htmldocs, no warning or error made by these patches.
>
> Hi Weijie,
>
> Please make sure you execute " make cleandocs & make htmldocs". Some
> warnings may be ignored by further compilation.
Hi!
Thanks for emphasizing this. While I do remember I used "make cleandocs
&& make htmldocs", and checked among those long lines of red warning
output to find anything caused by my commit, I indeed didn't notice this
warning appearing at the early stage of the compilation.
It seems that I need to have my eyes checked soon. ;-)
Apologize for my recklessness.
Even so, do we have any way to distinguish these long-standing warnings
from the new warnings that appear during compilation? In fact, every
time I was worried that I might not have noticed the newly appeared
warning. Unfortunately, this time it really happened. (For example,
setting a new color? for new warnings?) Do you have a better idea or
tips for this?
Btw I've been trying to know more about Sphinx and kernel-docs, hope my
mistake won't happen again.
Thanks.
> > WARNING: duplicate label kernel_org_trust_repository
> >
> > The same label is already defined in the English document. Please use a translation-specific label, for example:
> >
> > .. _zh_kernel_org_trust_repository:
> > checkpatch.pl reports:
> >
> > WARNING: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
> >
> > Please replace Assisted-by: LLM with the actual agent, model version, and tools used.
And this one has been updated from Jon's PR last night, so I ignored
this output, left just a simple LLM.
prev parent reply other threads:[~2026-08-21 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 17:13 [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation Weijie Yuan
2026-08-20 17:13 ` [PATCH 1/4] docs/zh_CN: update maintainer-pgp-guide translation Weijie Yuan
2026-08-20 17:13 ` [PATCH 2/4] docs/zh_CN: clarify free Nitrokey requirements Weijie Yuan
2026-08-20 17:13 ` [PATCH 3/4] docs/zh_CN: update maintainer-pgp-guide kernel.org link Weijie Yuan
2026-08-20 17:13 ` [PATCH 4/4] docs/zh_CN: add kernel.org trust repository reference Weijie Yuan
2026-08-20 17:38 ` Weijie Yuan
2026-08-21 4:14 ` Dongliang Mu
2026-08-21 5:14 ` Weijie Yuan
2026-08-21 6:54 ` [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation Dongliang Mu
2026-08-21 7:22 ` Weijie Yuan [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=aof8rCuuwzHUNtka@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.