public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, Mike Rapoport <rppt@kernel.org>,
	linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] docs/mm: Physical Memory: correct spelling in reference to CONFIG_PAGE_EXTENSION
Date: Wed, 15 Feb 2023 11:08:08 +0100	[thread overview]
Message-ID: <20230215100808.9613-1-lukas.bulwahn@gmail.com> (raw)

Commit 5d8c5e430a63 ("docs/mm: Physical Memory: add structure, introduction
and nodes description") slips in a minor spelling mistake for the config
PAGE_EXTENSION.

Correct the config name in the physical-memory documentation.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
 Documentation/mm/physical_memory.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/mm/physical_memory.rst b/Documentation/mm/physical_memory.rst
index 3f3c02aa6e6e..f9d7ea4b9dca 100644
--- a/Documentation/mm/physical_memory.rst
+++ b/Documentation/mm/physical_memory.rst
@@ -210,7 +210,7 @@ General
 ``node_page_ext``
   For UMA systems that use FLATMEM memory model the 0's node
   ``node_page_ext`` is array of extensions of struct pages. Available only
-  in the kernels built with ``CONFIG_PAGE_EXTENTION`` enabled.
+  in the kernels built with ``CONFIG_PAGE_EXTENSION`` enabled.
 
 ``node_start_pfn``
   The page frame number of the starting page frame in this node.
-- 
2.17.1


             reply	other threads:[~2023-02-15 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 10:08 Lukas Bulwahn [this message]
2023-02-15 10:12 ` [PATCH] docs/mm: Physical Memory: correct spelling in reference to CONFIG_PAGE_EXTENSION Mike Rapoport
2023-02-16 23:56 ` 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=20230215100808.9613-1-lukas.bulwahn@gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=corbet@lwn.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@kernel.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