From: Alex Shi <seakeel@gmail.com>
To: Dongliang Mu <dzm91@hust.edu.cn>,
si.yanteng@linux.dev, alexs@kernel.org, corbet@lwn.net,
Yanteng Si <siyanteng@loongson.cn>
Cc: hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] docs/zh_CN: update the translation of mm/hmm.rst
Date: Tue, 22 Oct 2024 11:28:55 +0800 [thread overview]
Message-ID: <4cf5f422-d287-4f53-9af2-82bd7fe3b264@gmail.com> (raw)
In-Reply-To: <82259a2656549c90591dc3873f3d2e8a4fb41233.1729327831.git.dzm91@hust.edu.cn>
Reviewed-by: Alex Shi <alexs@kernel.org>
On 10/19/24 16:54, Dongliang Mu wrote:
> Update to commit 406c4c5ee4ea ("docs:mm: fix spelling mistakes in
> heterogeneous memory management page")
>
> scripts/checktransupdate.py reports:
>
> Documentation/translations/zh_CN/mm/hmm.rst
> commit 406c4c5ee4ea ("docs:mm: fix spelling mistakes in heterogeneous
> memory management page")
> commit 090a7f1009b8 ("docs/mm: remove references to hmm_mirror ops and
> clean typos")
> commit d56b699d76d1 ("Documentation: Fix typos")
> 3 commits needs resolving in total
>
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
> Documentation/translations/zh_CN/mm/hmm.rst | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/mm/hmm.rst b/Documentation/translations/zh_CN/mm/hmm.rst
> index babbbe756c0f..0669f947d0bc 100644
> --- a/Documentation/translations/zh_CN/mm/hmm.rst
> +++ b/Documentation/translations/zh_CN/mm/hmm.rst
> @@ -129,13 +129,7 @@ struct page可以与现有的 mm 机制进行最简单、最干净的集成。
> int hmm_range_fault(struct hmm_range *range);
>
> 如果请求写访问,它将在丢失或只读条目上触发缺页异常(见下文)。缺页异常使用通用的 mm 缺
> -页异常代码路径,就像 CPU 缺页异常一样。
> -
> -这两个函数都将 CPU 页表条目复制到它们的 pfns 数组参数中。该数组中的每个条目对应于虚拟
> -范围中的一个地址。HMM 提供了一组标志来帮助驱动程序识别特殊的 CPU 页表项。
> -
> -在 sync_cpu_device_pagetables() 回调中锁定是驱动程序必须尊重的最重要的方面,以保
> -持事物正确同步。使用模式是::
> +页异常代码路径,就像 CPU 缺页异常一样。使用模式是::
>
> int driver_populate_range(...)
> {
next prev parent reply other threads:[~2024-10-22 3:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1729327831.git.dzm91@hust.edu.cn>
2024-10-19 8:54 ` [PATCH 1/6] docs/zh_CN: update the translation of mm/hmm.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-22 2:02 ` Alex Shi
2024-10-22 3:28 ` Alex Shi [this message]
2024-10-19 8:54 ` [PATCH 2/6] docs/zh_CN: update the translation of mm/active_mm.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-19 8:54 ` [PATCH 3/6] docs/zh_CN: update the translation of mm/admon/faq.rst Dongliang Mu
2024-10-22 1:43 ` Alex Shi
2024-10-19 8:54 ` [PATCH 4/6] docs/zh_CN: update the translation of mm/overcommit-accounting.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-19 8:54 ` [PATCH 5/6] docs/zh_CN: update the translation of mm/page_table_check.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-19 8:54 ` [PATCH 6/6] docs/zh_CN: update the translation of mm/page_owner.rst Dongliang Mu
2024-10-22 1:44 ` Alex Shi
2024-10-24 21:45 ` [PATCH 0/6] update the translation of partial files in mm 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=4cf5f422-d287-4f53-9af2-82bd7fe3b264@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=siyanteng@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