Commit 1067b261 authored by Randy Dunlap's avatar Randy Dunlap Committed by Linus Torvalds
Browse files

mm: drop duplicated words in <linux/pgtable.h> 



Drop the doubled words "used" and "by".

Drop the repeated acronym "TLB" and make several other fixes around it.
(capital letters, spellos)

Signed-off-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Reviewed-by: default avatarSeongJae Park <sjpark@amazon.de>
Link: http://lkml.kernel.org/r/2bb6e13e-44df-4920-52d9-4d3539945f73@infradead.org


Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent de1193f0

include/linux/pgtable.h

+6 −6
Original line number Diff line number Diff line
@@ -804,7 +804,7 @@ static inline void ptep_modify_prot_commit(struct vm_area_struct *vma, 


/*

 * No-op macros that just return the current protection value. Defined here

 * because these macros can be used used even if CONFIG_MMU is not defined.

 * because these macros can be used even if CONFIG_MMU is not defined.

 */



#ifndef pgprot_nx
@@ -1234,7 +1234,7 @@ static inline int pmd_trans_unstable(pmd_t *pmd) 
 * Technically a PTE can be PROTNONE even when not doing NUMA balancing but

 * the only case the kernel cares is for NUMA balancing and is only ever set

 * when the VMA is accessible. For PROT_NONE VMAs, the PTEs are not marked

 * _PAGE_PROTNONE so by by default, implement the helper as "always no". It

 * _PAGE_PROTNONE so by default, implement the helper as "always no". It

 * is the responsibility of the caller to distinguish between PROT_NONE

 * protections and NUMA hinting fault protections.

 */
@@ -1318,10 +1318,10 @@ static inline int pmd_free_pte_page(pmd_t *pmd, unsigned long addr) 
/*

 * ARCHes with special requirements for evicting THP backing TLB entries can

 * implement this. Otherwise also, it can help optimize normal TLB flush in

 * THP regime. stock flush_tlb_range() typically has optimization to nuke the

 * entire TLB TLB if flush span is greater than a threshold, which will

 * likely be true for a single huge page. Thus a single thp flush will

 * invalidate the entire TLB which is not desitable.

 * THP regime. Stock flush_tlb_range() typically has optimization to nuke the

 * entire TLB if flush span is greater than a threshold, which will

 * likely be true for a single huge page. Thus a single THP flush will

 * invalidate the entire TLB which is not desirable.

 * e.g. see arch/arc: flush_pmd_tlb_range

 */

#define flush_pmd_tlb_range(vma, addr, end)	flush_tlb_range(vma, addr, end)