From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: Alex Shi <alexs@kernel.org>,
Alex Shi <alex.shi@linux.alibaba.com>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Harry Wei <harryxiyou@gmail.com>,
linux-doc@vger.kernel.org, realpuyuwang@gmail.com,
siyanteng01@gmail.com, Wu XiangCheng <bobwxc@email.cn>,
Yanteng Si <siyanteng@loongson.cn>
Subject: Re: [PATCH v3 00/11] docs/zh_CN: add core api and openrisc translation
Date: Tue, 13 Apr 2021 15:04:49 -0600 [thread overview]
Message-ID: <87lf9lsxou.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210413131237.2253955-1-siyanteng@loongson.cn>
Yanteng Si <siyanteng@loongson.cn> writes:
> This series of patches translates core-api/irq/* and openrisc/* into
> Chinese
>
> v1 -> v2:
>
> Modify some words under Xiangcheng Wu's suggestion. Thanks for his rewiew!
>
> v2 -> v3:
>
> keep the signs number equal to the title char under Alex's suggestion.
> Thanks for his rewiew!
>
>
> Yanteng Si(11):
> docs/zh_CN: add core-api irq concepts.rst translation
> docs/zh_CN: add core-api irq irq-affinity.rst translation
> docs/zh_CN: add core-api irq irq-domain.rst translation
> docs/zh_CN: add core-api irq irqflags-tracing.rst
> docs/zh_CN: add core-api irq index.rst translation
> docs/zh_CN: add core-api index.rst translation
> docs/zh_CN: add translation to zh_CN index
> docs/zh_CN: add openrisc openrisc_port.rst translation
> docs/zh_CN: add openrisc todo.rst translation
> docs/zh_CN: add openrisc index.rst translation
> docs/zh_CN: add translation to zh_CN index
>
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
This looks like it's about ready to go in, but I seem to be missing
patch 11...?
Thanks,
jon
next prev parent reply other threads:[~2021-04-13 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 13:12 [PATCH v3 00/11] docs/zh_CN: add core api and openrisc translation Yanteng Si
2021-04-13 13:12 ` [PATCH v3 01/11] docs/zh_CN: add core-api irq concepts.rst translation Yanteng Si
2021-04-13 13:12 ` [PATCH v3 02/11] docs/zh_CN: add core-api irq irq-affinity.rst translation Yanteng Si
2021-04-13 13:33 ` Wu X.C.
2021-04-13 13:12 ` [PATCH v3 03/11] docs/zh_CN: add core-api irq irq-domain.rst translation Yanteng Si
2021-04-13 13:34 ` Wu X.C.
2021-04-13 13:12 ` [PATCH v3 04/11] docs/zh_CN: add core-api irq irqflags-tracing.rst translation Yanteng Si
2021-04-13 13:12 ` [PATCH v3 05/11] docs/zh_CN: add core-api irq index.rst translation Yanteng Si
2021-04-13 13:12 ` [PATCH v3 06/11] docs/zh_CN: add core-api " Yanteng Si
2021-04-13 13:12 ` [PATCH v3 07/11] docs/zh_CN: add translation to zh_CN index Yanteng Si
2021-04-13 13:12 ` [PATCH v3 08/11] docs/zh_CN: add openrisc openrisc_port.rst translation Yanteng Si
2021-04-13 13:36 ` Wu X.C.
2021-04-13 13:12 ` [PATCH v3 09/11] docs/zh_CN: add openrisc todo.rst translation Yanteng Si
2021-04-13 13:12 ` [PATCH v3 10/11] docs/zh_CN: add openrisc index.rst translation Yanteng Si
2021-04-13 21:04 ` Jonathan Corbet [this message]
2021-04-14 15:59 ` [PATCH v3 00/11] docs/zh_CN: add core api and openrisc translation 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=87lf9lsxou.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alex.shi@linux.alibaba.com \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=harryxiyou@gmail.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).