Fixed spelling error.
Signed-off-by: Alok Mistry <[email protected]>
---
arch/powerpc/mm/hash64_64k.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/mm/hash64_64k.c b/arch/powerpc/mm/hash64_64k.c
index b2d659c..fe89a6d 100644
--- a/arch/powerpc/mm/hash64_64k.c
+++ b/arch/powerpc/mm/hash64_64k.c
@@ -91,7 +91,7 @@ int __hash_page_4K(unsigned long ea, unsigned long access, unsigned long vsid,
!cpu_has_feature(CPU_FTR_COHERENT_ICACHE)) {
/*
- * No CPU has hugepages but lacks no execute, so we
+ * No CPU has huge pages but lacks no execute, so we
* don't need to worry about that case
*/
rflags = hash_page_do_lazy_icache(rflags, __pte(old_pte), trap);
--
1.9.1
Hi Alok
Thanks for wanting to contribute to the Linux kernel!
On 22/03/16 20:43, mistryalok wrote:
> Fixed spelling error.
> Signed-off-by: Alok Mistry <[email protected]>
> ---
> /*
> - * No CPU has hugepages but lacks no execute, so we
> + * No CPU has huge pages but lacks no execute, so we
> * don't need to worry about that case
> */
Within the kernel, we have a lot of internal terminology. If you grep
through the kernel source code, you'll find that in both the
documentation and the code, we do use the term "hugepage". We also use
"huge page", but "hugepage" is more common. Therefore I wouldn't call it
a spelling error, just an internal term :)
Andrew
--
Andrew Donnellan OzLabs, ADL Canberra
[email protected] IBM Australia Limited