From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: Yanteng Si <siyanteng@loongson.cn>,
alexs@kernel.org, chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
linux-doc@vger.kernel.org, realpuyuwang@gmail.com,
bobwxc@email.cn, siyanteng01@gmail.com,
huangjianghui@uniontech.com
Subject: Re: [PATCH v5 0/3] docs/zh_CN add three core api docs
Date: Thu, 13 May 2021 10:20:55 -0600 [thread overview]
Message-ID: <87k0o261w8.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1620286208.git.siyanteng@loongson.cn>
Yanteng Si <siyanteng@loongson.cn> writes:
> * As Matthew and Xiangcheng suggested:
>
> call kernel-doc to generate related docs (0001 and 0002).Thanks!
>
> I tested it on other computers (at least three) with no problem,
> But on my computers it prints 1000+ warnings, I tried to find the
> cause in the past few days but no clue.
> So, the two patches may print as follows:(maybe your computer won't print anything)
>
> linux-next/Documentation/translations/zh_CN/core-api/kernel-api.rst:235: WARNING: Duplicate C declaration, also defined at core-api/kernel-api:235.
> Declaration is '.. c:None:: struct list_head *prev'.
This is the same problem I just talked about in my other message. I
really think we need to just leave the kernel-doc directives out of
translations; we certainly don't want to add all those warnings.
Thanks,
jon
next prev parent reply other threads:[~2021-05-13 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 7:58 [PATCH v5 0/3] docs/zh_CN add three core api docs Yanteng Si
2021-05-06 7:58 ` [PATCH v5 1/3] docs/zh_CN: add core-api kernel-api.rst translation Yanteng Si
2021-05-06 7:58 ` [PATCH v5 2/3] docs/zh_CN: add core-api printk-basics.rst translation Yanteng Si
2021-05-06 7:58 ` [PATCH v5 3/3] docs/zh_CN: add core-api printk-formats.rst translation Yanteng Si
2021-05-10 2:46 ` [PATCH v5 0/3] docs/zh_CN add three core api docs teng sterling
2021-05-13 16:20 ` Jonathan Corbet [this message]
2021-05-14 9:24 ` yanteng si
2021-05-15 6:53 ` yanteng si
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=87k0o261w8.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=huangjianghui@uniontech.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=realpuyuwang@gmail.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
/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).