mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dongliang Mu <dzm91@hust.edu.cn>
To: jiang.peng9@zte.com.cn, si.yanteng@linux.dev
Cc: alexs@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/zh_CN: fix spelling mistake
Date: Mon, 17 Mar 2025 10:16:04 +0800	[thread overview]
Message-ID: <f11afa64-1629-4005-8cb4-723d9b6ce6cb@hust.edu.cn> (raw)
In-Reply-To: <20250317100811126QvOaWRPxSgm2ttU5faitl@zte.com.cn>


On 2025/3/17 10:08, jiang.peng9@zte.com.cn wrote:
> From: Peng Jiang <jiang.peng9@zte.com.cn>
>
> The word watermark was misspelled as "watemark".
>
> Signed-off-by: Peng Jiang <jiang.peng9@zte.com.cn>

One suggestion: the original English(Documentation/mm/balance.rst) 
version also has this typo. Submit a v2 patch to fix both?

Reviewed-by: Dongliang Mu <dzm91@hust.edu.cn>

> ---
>   Documentation/translations/zh_CN/mm/balance.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/mm/balance.rst b/Documentation/translations/zh_CN/mm/balance.rst
> index 6fd79209c307..f877c0cfa39a 100644
> --- a/Documentation/translations/zh_CN/mm/balance.rst
> +++ b/Documentation/translations/zh_CN/mm/balance.rst
> @@ -64,7 +64,7 @@ kswapd并不真正需要平衡高内存区,因为中断上下文并不请求
>   如果从进程内存和shm中偷取页面可以减轻该页面节点中任何区的内存压力,而该区的内存压力
>   已经低于其水位,则会进行偷取。
>
> -watemark[WMARK_MIN/WMARK_LOW/WMARK_HIGH]/low_on_memory/zone_wake_kswapd:
> +watermark[WMARK_MIN/WMARK_LOW/WMARK_HIGH]/low_on_memory/zone_wake_kswapd:
>   这些是每个区的字段,用于确定一个区何时需要平衡。当页面数低于水位[WMARK_MIN]时,
>   hysteric 的字段low_on_memory被设置。这个字段会一直被设置,直到空闲页数变成水位
>   [WMARK_HIGH]。当low_on_memory被设置时,页面分配请求将尝试释放该区域的一些页面(如果


  reply	other threads:[~2025-03-17  2:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  2:08 jiang.peng9
2025-03-17  2:16 ` Dongliang Mu [this message]
2025-03-17  2:31   ` jiang.peng9
2025-03-17  2:53     ` Dongliang Mu
2025-03-17 12:59       ` Alex Shi
2025-03-17  2:19 ` alexs

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=f11afa64-1629-4005-8cb4-723d9b6ce6cb@hust.edu.cn \
    --to=dzm91@hust.edu.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jiang.peng9@zte.com.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    /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

all inboxes | Powered by JetHome®