From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Naoya Horiguchi" <naoya.horiguchi@nec.com>,
"Miaohe Lin" <linmiaohe@huawei.com>,
linux-mm@kvack.org, "Jonathan Corbet" <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH 18/35] Documentation: mm: correct spelling
Date: Thu, 26 Jan 2023 22:39:48 -0800 [thread overview]
Message-ID: <20230127064005.1558-19-rdunlap@infradead.org> (raw)
In-Reply-To: <20230127064005.1558-1-rdunlap@infradead.org>
Correct spelling problems for Documentation/mm/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jérôme Glisse <jglisse@redhat.com>
Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
Cc: Miaohe Lin <linmiaohe@huawei.com>
Cc: linux-mm@kvack.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/mm/hmm.rst | 4 ++--
Documentation/mm/hwpoison.rst | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff -- a/Documentation/mm/hmm.rst b/Documentation/mm/hmm.rst
--- a/Documentation/mm/hmm.rst
+++ b/Documentation/mm/hmm.rst
@@ -416,10 +416,10 @@ can be used to make a memory range inacc
This replaces all mappings for pages in the given range with special swap
entries. Any attempt to access the swap entry results in a fault which is
-resovled by replacing the entry with the original mapping. A driver gets
+resolved by replacing the entry with the original mapping. A driver gets
notified that the mapping has been changed by MMU notifiers, after which point
it will no longer have exclusive access to the page. Exclusive access is
-guranteed to last until the driver drops the page lock and page reference, at
+guaranteed to last until the driver drops the page lock and page reference, at
which point any CPU faults on the page may proceed as described.
Memory cgroup (memcg) and rss accounting
diff -- a/Documentation/mm/hwpoison.rst b/Documentation/mm/hwpoison.rst
--- a/Documentation/mm/hwpoison.rst
+++ b/Documentation/mm/hwpoison.rst
@@ -50,7 +50,7 @@ of applications. KVM support requires a
For the KVM use there was need for a new signal type so that
KVM can inject the machine check into the guest with the proper
address. This in theory allows other applications to handle
-memory failures too. The expection is that near all applications
+memory failures too. The expectation is that near all applications
won't do that, but some very specialized ones might.
Failure recovery modes
next prev parent reply other threads:[~2023-01-27 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 6:39 [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-01-27 6:39 ` Randy Dunlap [this message]
2023-01-27 6:44 ` [PATCH 18/35] Documentation: mm: correct spelling HORIGUCHI NAOYA(堀口 直也)
2023-01-27 8:27 ` Bagas Sanjaya
2023-01-30 10:07 ` Mike Rapoport
2023-01-28 10:48 ` (subset) [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Mark Brown
2023-01-28 20:30 ` patchwork-bot+netdevbpf
2023-01-31 16:28 ` (subset) " Catalin Marinas
2023-02-14 16:57 ` Martin K. Petersen
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=20230127064005.1558-19-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=jglisse@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
/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).