From: Alex Shi <seakeel@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>
Subject: [GIT PULL] Chinese-docs changes for v7.3
Date: Fri, 17 Jul 2026 20:43:46 +0800 [thread overview]
Message-ID: <84cd6621-50b1-4b96-8e70-9685ba8c7af6@gmail.com> (raw)
The following changes since commit be828e6819ed139b699bf7feb00a546cb7806266:
docs: pt_BR: Translate deprecated interfaces guide to Portuguese
(2026-07-16 16:48:43 -0600)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/alexs/linux.git
tags/Chinese-docs-7.3
for you to fetch changes up to 8492d4e6bb7b9b1e78f2d17c4dda5272f25ec118:
docs/zh_CN: Update rust/testing.rst translation (2026-07-17 20:24:09
+0800)
----------------------------------------------------------------
Chinese translation docs for 7.3
This is the Chinese translation subtree for 7.3. It includes
the following changes:
- Add the some rust, module-signing docs translation
- Fix/update couples Chinese translation
Above patches are tested by 'make htmldocs'
Signed-off-by: Alex Shi <alexs@kernel.org>
----------------------------------------------------------------
Ben Guo (5):
docs/zh_CN: add --no-merges to git log example in how-to.rst
docs/zh_CN: Update rust/quick-start.rst translation
docs/zh_CN: Update rust/general-information.rst translation
docs/zh_CN: Update rust/arch-support.rst translation
docs/zh_CN: Update rust/testing.rst translation
Dongliang Mu (2):
docs/zh_CN: polish how-to.rst
docs/zh_CN: restructure how-to.rst patch submission workflow
Ethan Nelson-Moore (2):
docs/zh_CN: fix CONFIG_CGROUP typo for CONFIG_CGROUPS
docs/zh_CN: fix CONFIG_CONPAT typo for CONFIG_COMPAT
Yan Zhu (2):
docs/zh_CN: add module-signing Chinese translation
docs/zh_CN: update admin-guide/index.rst translation
chengyaqiang (1):
docs/zh_CN: fix KASAN SW_TAGS mode description
panzhipop (1):
docs/zh_TW: replace 接口 with 介面 in stable-api-nonsense.rst
Documentation/translations/zh_CN/accounting/psi.rst | 2 +-
Documentation/translations/zh_CN/admin-guide/index.rst | 202
++++++++++++++++++++-------
Documentation/translations/zh_CN/admin-guide/module-signing.rst | 250
++++++++++++++++++++++++++++++++++
Documentation/translations/zh_CN/dev-tools/kasan.rst | 2 +-
Documentation/translations/zh_CN/how-to.rst | 149
+++++++++++++-------
Documentation/translations/zh_CN/rust/arch-support.rst | 1 +
Documentation/translations/zh_CN/rust/general-information.rst | 82
++++++++++-
Documentation/translations/zh_CN/rust/quick-start.rst | 48
+++----
Documentation/translations/zh_CN/rust/testing.rst | 4 +
Documentation/translations/zh_CN/security/self-protection.rst | 2 +-
Documentation/translations/zh_TW/process/stable-api-nonsense.rst | 62
++++-----
11 files changed, 639 insertions(+), 165 deletions(-)
create mode 100644
Documentation/translations/zh_CN/admin-guide/module-signing.rst
next reply other threads:[~2026-07-17 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 12:43 Alex Shi [this message]
2026-07-22 15:46 ` 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=84cd6621-50b1-4b96-8e70-9685ba8c7af6@gmail.com \
--to=seakeel@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
/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
all inboxes | Powered by JetHome®