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 4/6] docs/zh_CN: update the translation of mm/overcommit-accounting.rst
Date: Tue, 22 Oct 2024 09:44:24 +0800	[thread overview]
Message-ID: <638d6ade-1fff-4fe3-8963-41b9ccea23a6@gmail.com> (raw)
In-Reply-To: <d426f3f3d9aac061c20c3b766c17369f4e60f398.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 d17ff438a036 ("docs: mm: fix vm overcommit
> documentation for OVERCOMMIT_GUESS")
> 
> scripts/checktransupdate.py reports:
> 
> Documentation/translations/zh_CN/mm/overcommit-accounting.rst
> commit d17ff438a036 ("docs: mm: fix vm overcommit documentation
> for OVERCOMMIT_GUESS")
> 1 commits needs resolving in total
> 
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
>  Documentation/translations/zh_CN/mm/overcommit-accounting.rst | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/Documentation/translations/zh_CN/mm/overcommit-accounting.rst b/Documentation/translations/zh_CN/mm/overcommit-accounting.rst
> index d8452d8b7fbb..f136a8b81859 100644
> --- a/Documentation/translations/zh_CN/mm/overcommit-accounting.rst
> +++ b/Documentation/translations/zh_CN/mm/overcommit-accounting.rst
> @@ -16,8 +16,7 @@ Linux内核支持下列超量使用处理模式
>  
>  0
>  	启发式超量使用处理。拒绝明显的地址空间超量使用。用于一个典型的系统。
> -	它确保严重的疯狂分配失败,同时允许超量使用以减少swap的使用。在这种模式下,
> -	允许root分配稍多的内存。这是默认的。
> +	它确保严重的疯狂分配失败,同时允许超量使用以减少swap的使用。这是默认的。
>  1
>  	总是超量使用。适用于一些科学应用。经典的例子是使用稀疏数组的代码,只是依赖
>  	几乎完全由零页组成的虚拟内存

  reply	other threads:[~2024-10-22  1:44 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
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 [this message]
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=638d6ade-1fff-4fe3-8963-41b9ccea23a6@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