From: Jonathan Corbet <corbet@lwn.net>
To: Pengyu Zhang <zpenya1314@gmail.com>,
alexs@kernel.org, siyanteng@loongson.cn, seakeel@gmail.com,
si.yanteng@linux.dev
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
zpenya1314@gmail.com, yaxin_wang_uestc@163.com,
zenghui.yu@linux.dev
Subject: Re: [PATCH v4] Docs/zh_CN: Translate page_tables.rst to Simplified Chinese
Date: Wed, 09 Oct 2024 10:13:41 -0600 [thread overview]
Message-ID: <87plo9b6fe.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241008153824.4691-1-zpenya1314@gmail.com>
Pengyu Zhang <zpenya1314@gmail.com> writes:
> This patch provides a Simplified Chinese translation of the
> "page_tables.rst" document, aimed at improving accessibility
> for Chinese-speaking developers and users.
>
> The translation prioritizes technical accuracy and readability,
> ensuring that the content remains clear and informative for
> its intended audience.
>
> Signed-off-by: Pengyu Zhang <zpenya1314@gmail.com>
> ---
> Documentation/translations/zh_CN/mm/index.rst | 1 +
> .../translations/zh_CN/mm/page_tables.rst | 221 ++++++++++++++++++
> 2 files changed, 222 insertions(+)
> create mode 100644 Documentation/translations/zh_CN/mm/page_tables.rst
When posting revised versions of patches, please always include (below
the "---" line) a summary of what has changed.
It looks like Alex reviewed the previous version; is there a reason you
didn't include the Reviewed-by tag? Unless something comes up, my plan
is to add that back and apply this in the near future.
Thanks,
jon
next prev parent reply other threads:[~2024-10-09 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 15:38 [PATCH v4] Docs/zh_CN: Translate page_tables.rst to Simplified Chinese Pengyu Zhang
2024-10-09 16:13 ` Jonathan Corbet [this message]
[not found] ` <023c4378-7625-41fc-a671-5db60311b3b8@linux.dev>
2024-10-11 2:01 ` Yanteng Si
-- strict thread matches above, loose matches on Subject: below --
2024-10-11 15:49 Pengyu Zhang
2024-10-12 9:19 ` 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=87plo9b6fe.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=si.yanteng@linux.dev \
--cc=siyanteng@loongson.cn \
--cc=yaxin_wang_uestc@163.com \
--cc=zenghui.yu@linux.dev \
--cc=zpenya1314@gmail.com \
/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).