public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Dongliang Mu <dzm91@hust.edu.cn>
To: Ben Guo <ben.guo@openatom.club>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <si.yanteng@linux.dev>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 0/4] docs/zh_CN: update rust/ subsystem translations
Date: Wed, 8 Apr 2026 19:44:55 +0800	[thread overview]
Message-ID: <8dd6239f-eac6-4e81-a1b5-a4e6c45d07fd@hust.edu.cn> (raw)
In-Reply-To: <cover.1775619061.git.ben.guo@openatom.club>


On 4/8/26 1:05 PM, Ben Guo wrote:
> Update Chinese translations for the Rust subsystem documentation,
> syncing with the latest upstream changes.
>
> - arch-support.rst: add ARM (ARMv7) support, update RISC-V and UM notes
> - coding-guidelines.rst: add imports formatting, private item docs,
>    C FFI types, and Lints sections
> - quick-start.rst: add distro-specific install instructions, update
>    rustc/bindgen sections, remove cargo section
> - index.rst: remove experimental notice and genindex

Hi Guo,

I found an issue in this patchset: please do not directly include my 
review tag from the internal mailing list [1].

After you submit it to the linux‑doc mailing list, I will add my review 
tag at that time. Including it now would look inappropriate.

Our internal review is only intended to maintain patch quality for our 
open‑source club.

[1] https://groups.google.com/g/hust-os-kernel-patches/c/QGN_5xneJc4
>
> Ben Guo (4):
>    docs/zh_CN: update rust/arch-support.rst translation
>    docs/zh_CN: update rust/coding-guidelines.rst translation
>    docs/zh_CN: update rust/quick-start.rst translation
>    docs/zh_CN: update rust/index.rst translation
>
>   .../translations/zh_CN/rust/arch-support.rst  |   9 +-
>   .../zh_CN/rust/coding-guidelines.rst          | 262 +++++++++++++++++-
>   .../translations/zh_CN/rust/index.rst         |  17 --
>   .../translations/zh_CN/rust/quick-start.rst   | 190 ++++++++++---
>   4 files changed, 401 insertions(+), 77 deletions(-)
>


  parent reply	other threads:[~2026-04-08 11:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  5:05 [PATCH 0/4] docs/zh_CN: update rust/ subsystem translations Ben Guo
2026-04-08  5:05 ` [PATCH 1/4] docs/zh_CN: update rust/arch-support.rst translation Ben Guo
2026-04-08 11:31   ` Gary Guo
2026-04-08  5:05 ` [PATCH 2/4] docs/zh_CN: update rust/coding-guidelines.rst translation Ben Guo
2026-04-08 11:32   ` Gary Guo
2026-04-08  5:05 ` [PATCH 3/4] docs/zh_CN: update rust/quick-start.rst translation Ben Guo
2026-04-08 11:33   ` Gary Guo
2026-04-08 16:51     ` Ben Guo
2026-04-08 17:43       ` Gary Guo
2026-04-08  5:05 ` [PATCH 4/4] docs/zh_CN: update rust/index.rst translation Ben Guo
2026-04-08 11:33   ` Gary Guo
2026-04-08 11:44 ` Dongliang Mu [this message]
2026-04-08 16:54   ` [PATCH 0/4] docs/zh_CN: update rust/ subsystem translations Ben Guo

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=8dd6239f-eac6-4e81-a1b5-a4e6c45d07fd@hust.edu.cn \
    --to=dzm91@hust.edu.cn \
    --cc=alexs@kernel.org \
    --cc=ben.guo@openatom.club \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rust-for-linux@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