linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the jc_docs tree
Date: Mon, 31 Oct 2022 08:27:06 -0600	[thread overview]
Message-ID: <87a65c3w79.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221031170537.722220c4@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> After merging the jc_docs tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/core-api/timekeeping.rst:16: WARNING: Duplicate C declaration, also defined at translations/zh_CN/core-api/timekeeping:26.
> Declaration is '.. c:function:: ktime_t ktime_get(void)'.

[...]

> Presumably introduced by commit
>
>   d24c911bd031 ("docs/zh_CN: core-api: Add timekeeping Chinese translation")
>
> but I have no idea why :-(

"Why" is the ".. c:function::" definitions in core-api/timekeeping.rst.
The translation duplicated those, leading to the warnings you mention.
I should have caught that, but the old (fast!) version of sphinx I used
to check things doesn't put out that warning.  I'm just going to have to
be more patient, I guess.

I've reverted the commit in question.  I'm not sure what the best
practice should be for translating documents with those declarations in
them.  Perhaps the function prototype should just go into a literal
block without the c:function declaration?

Thanks,

jon

  parent reply	other threads:[~2022-10-31 14:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  6:05 linux-next: build warnings after merge of the jc_docs tree Stephen Rothwell
2022-10-31  9:02 ` Bagas Sanjaya
2022-10-31 14:27 ` Jonathan Corbet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-27  3:15 Stephen Rothwell
2022-01-27  3:36 ` Stephen Rothwell
2022-01-27 18:22 ` Jonathan Corbet
2021-03-26  7:54 Stephen Rothwell
2021-03-26 19:20 ` Jonathan Corbet
2021-03-10  3:20 Stephen Rothwell
2021-01-19  6:13 Stephen Rothwell
2021-01-19  6:45 ` Stephen Rothwell
2021-01-19  7:16 ` Stephen Rothwell
2021-01-19  9:07 ` Mauro Carvalho Chehab

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=87a65c3w79.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zhoubinbin@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).