mm/cma.c: fix typos in comments
Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com> Acked-by: Michal Nazarewicz <mina86@mina86.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
f0d6647e85
commit
0f96ae2928
4
mm/cma.c
4
mm/cma.c
|
@ -182,7 +182,7 @@ int __init cma_init_reserved_mem(phys_addr_t base, phys_addr_t size,
|
|||
if (!size || !memblock_is_region_reserved(base, size))
|
||||
return -EINVAL;
|
||||
|
||||
/* ensure minimal alignment requied by mm core */
|
||||
/* ensure minimal alignment required by mm core */
|
||||
alignment = PAGE_SIZE << max(MAX_ORDER - 1, pageblock_order);
|
||||
|
||||
/* alignment should be aligned with order_per_bit */
|
||||
|
@ -238,7 +238,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
|
|||
/*
|
||||
* high_memory isn't direct mapped memory so retrieving its physical
|
||||
* address isn't appropriate. But it would be useful to check the
|
||||
* physical address of the highmem boundary so it's justfiable to get
|
||||
* physical address of the highmem boundary so it's justifiable to get
|
||||
* the physical address from it. On x86 there is a validation check for
|
||||
* this case, so the following workaround is needed to avoid it.
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue