From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng@loongson.cn>,
alexs@kernel.org, bobwxc@email.cn, seakeel@gmail.com
Cc: Yanteng Si <siyanteng@loongson.cn>,
chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
linux-doc@vger.kernel.org, siyanteng01@gmail.com,
zhoubinbin@loongson.cn, yizhou.tang@shopee.com,
wanjiabing@vivo.com, leoyang.li@nxp.com, src.res@email.cn
Subject: Re: [PATCH v2 0/8] Docs/zh_CN: Update some translation to 5.19-rc8
Date: Thu, 28 Jul 2022 09:40:07 -0600 [thread overview]
Message-ID: <87pmhpb608.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1658983157.git.siyanteng@loongson.cn>
Yanteng Si <siyanteng@loongson.cn> writes:
> v2:
> *Take Alex's advice and modify "狗粮测试" to "自我测试" .
>
> v1:
> * Update the following Chinese documents to 5.19-rc8:
>
> iio
> dev-tools
> mm/damon
> PCI
> scheduler
>
> Yanteng Si (8):
> Docs/zh_CN: Update the translation of iio_configfs to 5.19-rc8
> Docs/zh_CN: Update the translation of kasan to 5.19-rc8
> Docs/zh_CN: Update the translation of sparse to 5.19-rc8
> Docs/zh_CN: Update the translation of testing-overview to 5.19-rc8
> Docs/zh_CN: Update the translation of usage to 5.19-rc8
> Docs/zh_CN: Update the translation of pci-iov-howto to 5.19-rc8
> Docs/zh_CN: Update the translation of pci to 5.19-rc8
> Docs/zh_CN: Update the translation of sched-stats to 5.19-rc8
>
> .../translations/zh_CN/PCI/pci-iov-howto.rst | 7 +-
> Documentation/translations/zh_CN/PCI/pci.rst | 6 +-
> .../zh_CN/admin-guide/mm/damon/usage.rst | 2 +
> .../translations/zh_CN/dev-tools/kasan.rst | 117 ++++++++++++------
> .../translations/zh_CN/dev-tools/sparse.rst | 2 +
> .../zh_CN/dev-tools/testing-overview.rst | 25 ++++
> .../translations/zh_CN/iio/iio_configfs.rst | 12 +-
> .../zh_CN/scheduler/sched-stats.rst | 8 +-
> 8 files changed, 123 insertions(+), 56 deletions(-)
So these patches create a number of checkpatch warnings:
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit c1d82dbcb0a6 ("docs: iio: fix example formatting")'
I've gone ahead and applied them anyway, but that might be a good thing
to watch out for in the future.
Thanks,
jon
next prev parent reply other threads:[~2022-07-28 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 5:05 [PATCH v2 0/8] Docs/zh_CN: Update some translation to 5.19-rc8 Yanteng Si
2022-07-28 5:05 ` [PATCH v2 1/8] Docs/zh_CN: Update the translation of iio_configfs " Yanteng Si
2022-07-28 5:05 ` [PATCH v2 2/8] Docs/zh_CN: Update the translation of kasan " Yanteng Si
2022-07-28 5:05 ` [PATCH v2 3/8] Docs/zh_CN: Update the translation of sparse " Yanteng Si
2022-07-28 5:07 ` [PATCH v2 4/8] Docs/zh_CN: Update the translation of testing-overview " Yanteng Si
2022-07-28 5:07 ` [PATCH v2 5/8] Docs/zh_CN: Update the translation of usage " Yanteng Si
2022-07-28 5:08 ` [PATCH v2 6/8] Docs/zh_CN: Update the translation of pci-iov-howto " Yanteng Si
2022-07-28 5:08 ` [PATCH v2 7/8] Docs/zh_CN: Update the translation of pci " Yanteng Si
2022-07-28 5:08 ` [PATCH v2 8/8] Docs/zh_CN: Update the translation of sched-stats " Yanteng Si
2022-07-28 15:40 ` Jonathan Corbet [this message]
2022-07-29 6:43 ` [PATCH v2 0/8] Docs/zh_CN: Update some 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=87pmhpb608.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=leoyang.li@nxp.com \
--cc=linux-doc@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
--cc=src.res@email.cn \
--cc=wanjiabing@vivo.com \
--cc=yizhou.tang@shopee.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.