* [PATCH] mm: Fix two typos in comments for to_vmem_altmap()
@ 2016-01-25 10:35 Andreas Ziegler
0 siblings, 0 replies; only message in thread
From: Andreas Ziegler @ 2016-01-25 10:35 UTC (permalink / raw
To: Dan Williams; +Cc: Andrew Morton, linux-kernel, Linus Torvalds, Andreas Ziegler
Commit 4b94ffdc4163 ("x86, mm: introduce vmem_altmap to augment
vmemmap_populate()"), introduced the to_vmem_altmap() function.
The comments in this function contain two typos (one misspelling
of the Kconfig option CONFIG_SPARSEMEM_VMEMMAP, and one missing
letter 'n'), let's fix them up.
Signed-off-by: Andreas Ziegler <andreas.ziegler@fau.de>
---
kernel/memremap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/memremap.c b/kernel/memremap.c
index e517a16..2e84aa8 100644
--- a/kernel/memremap.c
+++ b/kernel/memremap.c
@@ -377,7 +377,7 @@ struct vmem_altmap *to_vmem_altmap(unsigned long memmap_start)
/*
* 'memmap_start' is the virtual address for the first "struct
* page" in this range of the vmemmap array. In the case of
- * CONFIG_SPARSE_VMEMMAP a page_to_pfn conversion is simple
+ * CONFIG_SPARSEMEM_VMEMMAP a page_to_pfn conversion is simple
* pointer arithmetic, so we can perform this to_vmem_altmap()
* conversion without concern for the initialization state of
* the struct page fields.
@@ -386,7 +386,7 @@ struct vmem_altmap *to_vmem_altmap(unsigned long memmap_start)
struct dev_pagemap *pgmap;
/*
- * Uncoditionally retrieve a dev_pagemap associated with the
+ * Unconditionally retrieve a dev_pagemap associated with the
* given physical address, this is only for use in the
* arch_{add|remove}_memory() for setting up and tearing down
* the memmap.
--
1.9.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2016-01-25 10:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-25 10:35 [PATCH] mm: Fix two typos in comments for to_vmem_altmap() Andreas Ziegler
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 read-only IMAP folder(s) and NNTP newsgroup(s).