From: zhaimingbing <zhaimingbing@cmss.chinamobile.com>
To: willy@infradead.org, James.Bottomley@hansenpartnership.com,
rdunlap@infradead.org
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
zhaimingbing <zhaimingbing@cmss.chinamobile.com>
Subject: [PATCH] mm: fix multiple typos in multiple files
Date: Fri, 27 Oct 2023 14:43:45 +0800 [thread overview]
Message-ID: <20231027064345.2434-1-zhaimingbing@cmss.chinamobile.com> (raw)
nommu.c: Fix typo 'privatize'
io-mapping.c: Fix typo 'pre-validation'
Signed-off-by: zhaimingbing <zhaimingbing@cmss.chinamobile.com>
---
mm/io-mapping.c | 2 +-
mm/nommu.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/io-mapping.c b/mm/io-mapping.c
index 01b362799..486598ba4 100644
--- a/mm/io-mapping.c
+++ b/mm/io-mapping.c
@@ -21,7 +21,7 @@ int io_mapping_map_user(struct io_mapping *iomap, struct vm_area_struct *vma,
if (WARN_ON_ONCE((vma->vm_flags & expected_flags) != expected_flags))
return -EINVAL;
- /* We rely on prevalidation of the io-mapping to skip track_pfn(). */
+ /* We rely on pre-validation of the io-mapping to skip track_pfn(). */
return remap_pfn_range_notrack(vma, addr, pfn, size,
__pgprot((pgprot_val(iomap->prot) & _PAGE_CACHE_MASK) |
(pgprot_val(vma->vm_page_prot) & ~_PAGE_CACHE_MASK)));
diff --git a/mm/nommu.c b/mm/nommu.c
index 7f9e9e5a0..40842b080 100644
--- a/mm/nommu.c
+++ b/mm/nommu.c
@@ -776,7 +776,7 @@ static int validate_mmap_request(struct file *file,
if (!(capabilities & NOMMU_MAP_DIRECT))
return -ENODEV;
- /* we mustn't privatise shared mappings */
+ /* we mustn't privatize shared mappings */
capabilities &= ~NOMMU_MAP_COPY;
} else {
/* we're going to read the file into private memory we
--
2.33.0
next reply other threads:[~2023-10-27 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 6:43 zhaimingbing [this message]
2023-10-27 7:19 ` Randy Dunlap
2023-10-27 8:04 ` David Hildenbrand
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=20231027064345.2434-1-zhaimingbing@cmss.chinamobile.com \
--to=zhaimingbing@cmss.chinamobile.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.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