From: Doehyun Baek <doehyunbaek@gmail.com>
To: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>
Cc: Dongliang Mu <dzm91@hust.edu.cn>, SJ Park <sj@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Doehyun Baek <doehyunbaek@gmail.com>
Subject: [PATCH v6 0/7] docs/zh_CN: update DAMON translations
Date: Wed, 8 Jul 2026 07:32:39 +0000 [thread overview]
Message-ID: <20260708073246.1652828-1-doehyunbaek@gmail.com> (raw)
Update the Simplified Chinese DAMON documentation translations. The
series is split by file, as requested. It is based on mm-new after the
English DAMON documentation fixes have landed.
The intention of this series is to update
Documentation/translations/zh_CN/admin-guide/mm/damon/. This required
choosing how to handle Documentation/translations/zh_CN/mm/damon/: do not
update it at all, update only design.rst, or update it fully. I chose to
update only design.rst, because the admin-guide updates need its zh_CN
anchors and references. Updating the other files would broaden the scope
beyond the requested admin-guide refresh. I would do otherwise if
requested.
I checked the updated translations paragraph by paragraph and sentence by
sentence. Given the size of the update, some issues may remain. In
particular, usage.rst and design.rst were significantly outdated and needed
near-complete updates.
Doehyun Baek (7):
docs/zh_CN: update DAMON design translation
docs/zh_CN: add DAMON_STAT usage translation
docs/zh_CN: update DAMON index translation
docs/zh_CN: update DAMON start translation
docs/zh_CN: update DAMON usage translation
docs/zh_CN: update DAMON reclaim translation
docs/zh_CN: update DAMON LRU sort translation
.../zh_CN/admin-guide/mm/damon/index.rst | 15 +-
.../zh_CN/admin-guide/mm/damon/lru_sort.rst | 68 +-
.../zh_CN/admin-guide/mm/damon/reclaim.rst | 82 ++-
.../zh_CN/admin-guide/mm/damon/start.rst | 63 +-
.../zh_CN/admin-guide/mm/damon/stat.rst | 94 +++
.../zh_CN/admin-guide/mm/damon/usage.rst | 521 +++++++++++---
.../translations/zh_CN/mm/damon/design.rst | 665 +++++++++++++++++-
7 files changed, 1343 insertions(+), 165 deletions(-)
create mode 100644 Documentation/translations/zh_CN/admin-guide/mm/damon/stat.rst
base-commit: db6ed2a3d31068ca5577466591b2521dee0508ca
--
2.43.0
next reply other threads:[~2026-07-08 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 7:32 Doehyun Baek [this message]
2026-07-08 7:32 ` [PATCH v6 1/7] docs/zh_CN: update DAMON design translation Doehyun Baek
2026-07-08 7:32 ` [PATCH v6 2/7] docs/zh_CN: add DAMON_STAT usage translation Doehyun Baek
2026-07-08 7:32 ` [PATCH v6 3/7] docs/zh_CN: update DAMON index translation Doehyun Baek
2026-07-08 7:32 ` [PATCH v6 4/7] docs/zh_CN: update DAMON start translation Doehyun Baek
2026-07-08 7:32 ` [PATCH v6 5/7] docs/zh_CN: update DAMON usage translation Doehyun Baek
2026-07-08 7:32 ` [PATCH v6 6/7] docs/zh_CN: update DAMON reclaim translation Doehyun Baek
2026-07-08 7:32 ` [PATCH v6 7/7] docs/zh_CN: update DAMON LRU sort translation Doehyun Baek
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=20260708073246.1652828-1-doehyunbaek@gmail.com \
--to=doehyunbaek@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=si.yanteng@linux.dev \
--cc=sj@kernel.org \
--cc=skhan@linuxfoundation.org \
/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