linux-kernel.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: Yanteng Si <siyanteng@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 warning after merge of the jc_docs tree
Date: Wed, 13 Jan 2021 16:27:30 -0700	[thread overview]
Message-ID: <20210113162730.4f6dc0ac@lwn.net> (raw)
In-Reply-To: <20210113150748.1efc75aa@canb.auug.org.au>

On Wed, 13 Jan 2021 15:07:48 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the jc_docs tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/translations/zh_CN/mips/ingenic-tcu.rst:61: WARNING: Malformed table.
> Text in column margin in table line 6.
> 
> ===========         =====
> 时钟                drivers/clk/ingenic/tcu.c
> 中断                drivers/irqchip/irq-ingenic-tcu.c
> 定时器              drivers/clocksource/ingenic-timer.c
> OST                 drivers/clocksource/ingenic-ost.c
> 脉冲宽度调制器      drivers/pwm/pwm-jz4740.c
> 看门狗              drivers/watchdog/jz4740_wdt.c
> ===========         =====
> 
> Introduced by commit
> 
>   419b1d4ed1cb ("doc/zh_CN: add mips ingenic-tcu.rst translation")

Memo to self: you can't skip doing a new build even for simple
translations that obviously shouldn't add any new problems.  Sorry for the
noise, I've applied fixes from Lukas Bulwahn for all of this whole mess of
errors.

Yantang, *please* do not submit documentation patches without having done
a docs build to make sure things work as expected!

Thanks,

jon

  reply	other threads:[~2021-01-14  1:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  4:07 linux-next: build warning after merge of the jc_docs tree Stephen Rothwell
2021-01-13 23:27 ` Jonathan Corbet [this message]
2021-01-21  2:07   ` 司延腾
2021-01-21 18:30     ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18  7:28 Stephen Rothwell
2023-12-18 14:18 ` Jonathan Corbet
2023-12-19 23:59   ` Randy Dunlap
2023-12-20  0:02     ` Jonathan Corbet
2023-12-20  0:04       ` Randy Dunlap
2021-02-23  5:19 Stephen Rothwell
2021-01-13  4:14 Stephen Rothwell
2021-01-13  4:12 Stephen Rothwell
2021-01-13  4:18 ` Stephen Rothwell
2020-12-07  7:52 Stephen Rothwell
2020-11-16  6:03 Stephen Rothwell
2020-12-14 19:51 ` Stephen Rothwell
2020-12-14 20:17   ` 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=20210113162730.4f6dc0ac@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=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).