linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <siyanteng@loongson.cn>
To: alexs@kernel.org, bobwxc@email.cn, seakeel@gmail.com
Cc: Yanteng Si <siyanteng@loongson.cn>,
	corbet@lwn.net, 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: [PATCH 0/8] Docs/zh_CN: Update some translation to 5.19-rc8
Date: Mon, 25 Jul 2022 17:20:45 +0800	[thread overview]
Message-ID: <cover.1658740151.git.siyanteng@loongson.cn> (raw)

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(-)

-- 
2.31.1


             reply	other threads:[~2022-07-25  9:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  9:20 Yanteng Si [this message]
2022-07-25  9:20 ` [PATCH 1/8] Docs/zh_CN: Update the translation of iio_configfs to 5.19-rc8 Yanteng Si
2022-07-26  5:51   ` Alex Shi
2022-07-25  9:20 ` [PATCH 2/8] Docs/zh_CN: Update the translation of kasan " Yanteng Si
2022-07-27  2:15   ` Alex Shi
2022-07-28  1:17     ` YanTeng Si
2022-07-25  9:20 ` [PATCH 3/8] Docs/zh_CN: Update the translation of sparse " Yanteng Si
2022-07-27  2:16   ` Alex Shi
2022-07-25  9:23 ` [PATCH 4/8] Docs/zh_CN: Update the translation of testing-overview " Yanteng Si
2022-07-27  2:18   ` Alex Shi
2022-07-25  9:24 ` [PATCH 5/8] Docs/zh_CN: Update the translation of usage " Yanteng Si
2022-07-27  2:18   ` Alex Shi
2022-07-25  9:24 ` [PATCH 6/8] Docs/zh_CN: Update the translation of pci-iov-howto " Yanteng Si
2022-07-27  2:19   ` Alex Shi
2022-07-25  9:24 ` [PATCH 7/8] Docs/zh_CN: Update the translation of pci " Yanteng Si
2022-07-26 16:19   ` Wu XiangCheng
2022-07-27  2:20   ` Alex Shi
2022-07-25  9:24 ` [PATCH 8/8] Docs/zh_CN: Update the translation of sched-stats " Yanteng Si
2022-07-26 15:06   ` Wu XiangCheng
2022-07-27  2:20   ` Alex Shi

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=cover.1658740151.git.siyanteng@loongson.cn \
    --to=siyanteng@loongson.cn \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=chenhuacai@kernel.org \
    --cc=corbet@lwn.net \
    --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=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 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).