linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suchit K <suchitkarunakaran@gmail.com>
To: akpm@linux-foundation.org, skhan@linuxfoundation.org
Cc: Suchit K <suchitkarunakaran@gmail.com>,
	linux-kernel-mentees@lists.linux.dev,
	 linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-mm@kvack.org
Subject: [PATCH] Documentation/mm: Fix spelling mistake
Date: Sat, 15 Feb 2025 22:30:42 +0530	[thread overview]
Message-ID: <CAO9wTFhe4sf1eVVgijt2cdLPPsUHBj7B=HN-380_JSpve5KbvQ@mail.gmail.com> (raw)

The word watermark was misspelled as "watemark" in the balance.rst
file. This commit corrects the spelling error.
Signed-off-by: Suchit <suchitkarunakaran@gmail.com>
---
 Documentation/mm/balance.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/mm/balance.rst b/Documentation/mm/balance.rst
index abaa78561..c4962c89a 100644
--- a/Documentation/mm/balance.rst
+++ b/Documentation/mm/balance.rst
@@ -81,7 +81,7 @@ Page stealing from process memory and shm is done if
stealing the page would
 alleviate memory pressure on any zone in the page's node that has fallen below
 its watermark.

-watemark[WMARK_MIN/WMARK_LOW/WMARK_HIGH]/low_on_memory/zone_wake_kswapd: These
+watermark[WMARK_MIN/WMARK_LOW/WMARK_HIGH]/low_on_memory/zone_wake_kswapd: These
 are per-zone fields, used to determine when a zone needs to be balanced. When
 the number of pages falls below watermark[WMARK_MIN], the hysteric field
 low_on_memory gets set. This stays set till the number of free pages becomes
-- 
2.48.1


             reply	other threads:[~2025-02-15 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15 17:00 Suchit K [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-15 16:55 Suchit K
2025-02-15 16:52 Suchit K
2025-02-15 17:24 ` Jonathan Corbet
2025-02-15 17:30   ` Suchit K
2025-02-15 17:48     ` Jonathan Corbet
2025-02-15 18:07       ` Suchit K
2025-02-15 16:45 Suchit K

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='CAO9wTFhe4sf1eVVgijt2cdLPPsUHBj7B=HN-380_JSpve5KbvQ@mail.gmail.com' \
    --to=suchitkarunakaran@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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