linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Xiao <abigwc@gmail.com>
To: corbet@lwn.net
Cc: akpm@linux-foundation.org, yejiajian2018@email.szu.edu.cn,
	caoyixuan2019@email.szu.edu.cn, zhangyinan2019@email.szu.edu.cn,
	akiyks@gmail.com, rppt@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Chen Xiao <abigwc@gmail.com>
Subject: [PATCH] docs: mm/page_owner: fix spelling mistakes
Date: Thu,  8 Dec 2022 14:04:03 +0800	[thread overview]
Message-ID: <1670479443-8484-1-git-send-email-abigwc@gmail.com> (raw)

Fix several spelling mistakes in page_owner documentation.

Signed-off-by: Chen Xiao <abigwc@gmail.com>
---
 Documentation/mm/page_owner.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/mm/page_owner.rst b/Documentation/mm/page_owner.rst
index 1275149..0f4cb59 100644
--- a/Documentation/mm/page_owner.rst
+++ b/Documentation/mm/page_owner.rst
@@ -52,7 +52,7 @@ pages are investigated and marked as allocated in initialization phase.
 Although it doesn't mean that they have the right owner information,
 at least, we can tell whether the page is allocated or not,
 more accurately. On 2GB memory x86-64 VM box, 13343 early allocated pages
-are catched and marked, although they are mostly allocated from struct
+are caught and marked, although they are mostly allocated from struct
 page extension feature. Anyway, after that, no page is left in
 un-tracking state.
 
@@ -178,7 +178,7 @@ STANDARD FORMAT SPECIFIERS
 	at		alloc_ts	timestamp of the page when it was allocated
 	ator		allocator	memory allocator for pages
 
-  For --curl option:
+  For --cull option:
 
 	KEY		LONG		DESCRIPTION
 	p		pid		process ID
-- 
1.8.3.1


             reply	other threads:[~2022-12-08  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  6:04 Chen Xiao [this message]
2022-12-08  6:09 ` [PATCH] docs: mm/page_owner: fix spelling mistakes Randy Dunlap
2023-01-02 23:26 ` 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=1670479443-8484-1-git-send-email-abigwc@gmail.com \
    --to=abigwc@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=caoyixuan2019@email.szu.edu.cn \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=yejiajian2018@email.szu.edu.cn \
    --cc=zhangyinan2019@email.szu.edu.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;
as well as URLs for NNTP newsgroup(s).