From: 司延腾 <siyanteng@loongson.cn>
To: "Jonathan Corbet" <corbet@lwn.net>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: Re: linux-next: build warning after merge of the jc_docs tree
Date: Thu, 21 Jan 2021 10:07:48 +0800 (GMT+08:00) [thread overview]
Message-ID: <4b5a642b.4d7e.17722b2a4af.Coremail.siyanteng@loongson.cn> (raw)
In-Reply-To: <20210113162730.4f6dc0ac@lwn.net>
Sorry, I apologize for the inconvenience caused to you, I do not quibble, but I have been studying for nearly a week, please pay attention to my future patches.
Thanks
Yanteng
> -----原始邮件-----
> 发件人: "Jonathan Corbet" <corbet@lwn.net>
> 发送时间: 2021-01-14 07:27:30 (星期四)
> 收件人: "Stephen Rothwell" <sfr@canb.auug.org.au>
> 抄送: "Yanteng Si" <siyanteng@loongson.cn>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, "Linux Next Mailing List" <linux-next@vger.kernel.org>
> 主题: Re: linux-next: build warning after merge of the jc_docs tree
>
> 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
</sfr@canb.auug.org.au></linux-next@vger.kernel.org></linux-kernel@vger.kernel.org></siyanteng@loongson.cn></sfr@canb.auug.org.au></corbet@lwn.net>
next prev parent reply other threads:[~2021-01-21 2:35 UTC|newest]
Thread overview: 4+ 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
2021-01-21 2:07 ` 司延腾 [this message]
2021-01-21 18:30 ` 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=4b5a642b.4d7e.17722b2a4af.Coremail.siyanteng@loongson.cn \
--to=siyanteng@loongson.cn \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).