public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 2/6] docs/zh_CN: update the translation of mm/active_mm.rst
Date: Tue, 22 Oct 2024 09:43:36 +0800	[thread overview]
Message-ID: <2e08db0e-74b2-4b50-ab0a-1318e541ec7e@gmail.com> (raw)
In-Reply-To: <985f62236dad7c9446272d94bffc20eb8f45ae4b.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 88e3009b5283 ("lazy tlb: allow lazy tlb
> mm refcounting to be configurable")
> 
> scripts/checktransupdate.py reports:
> 
> Documentation/translations/zh_CN/mm/active_mm.rst
> commit 88e3009b5283 ("lazy tlb: allow lazy tlb mm refcounting
> to be configurable")
> commit ee86588960e2 ("docs/mm: remove useless markup")
> 2 commits needs resolving in total
> 
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
>  Documentation/translations/zh_CN/mm/active_mm.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/translations/zh_CN/mm/active_mm.rst b/Documentation/translations/zh_CN/mm/active_mm.rst
> index c2816f523bd7..b3352668c4c8 100644
> --- a/Documentation/translations/zh_CN/mm/active_mm.rst
> +++ b/Documentation/translations/zh_CN/mm/active_mm.rst
> @@ -13,6 +13,11 @@
>  Active MM
>  =========
>  
> +注意,在配置了 CONFIG_MMU_LAZY_TLB_REFCOUNT=n 的内核中,mm_count 引用计数
> +可能不再包括“懒惰”用户(运行任务中 ->active_mm == mm && ->mm == NULL)。
> +获取和释放这些懒惰引用必须使用 mmgrab_lazy_tlb() 和 mmdrop_lazy_tlb() 这
> +两个辅助函数,它们抽象了这个配置选项。
> +
>  这是一封linux之父回复开发者的一封邮件,所以翻译时我尽量保持邮件格式的完整。
>  
>  ::

  reply	other threads:[~2024-10-22  1:43 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
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 [this message]
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=2e08db0e-74b2-4b50-ab0a-1318e541ec7e@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