Commit 06c88398 authored by Zhen Lei's avatar Zhen Lei Committed by Linus Torvalds
Browse files

mm: fix spelling mistakes in header files 

Fix some spelling mistakes in comments:
successfull ==> successful
potentialy ==> potentially
alloced ==> allocated
indicies ==> indices
wont ==> won't
resposible ==> responsible
dirtyness ==> dirtiness
droppped ==> dropped
alread ==> already
occured ==> occurred
interupts ==> interrupts
extention ==> extension
slighly ==> slightly
Dont't ==> Don't

Link: https://lkml.kernel.org/r/20210531034849.9549-2-thunder.leizhen@huawei.com


Signed-off-by: default avatarZhen Lei <thunder.leizhen@huawei.com>
Cc: Jerome Glisse <jglisse@redhat.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Dennis Zhou <dennis@kernel.org>
Cc: Tejun Heo <tj@kernel.org>
Cc: Christoph Lameter <cl@linux.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 76fe17ef

include/linux/compaction.h

+2 −2
Original line number Diff line number Diff line
@@ -35,12 +35,12 @@ enum compact_result { 
	COMPACT_CONTINUE,



	/*

	 * The full zone was compacted scanned but wasn't successfull to compact

	 * The full zone was compacted scanned but wasn't successful to compact

	 * suitable pages.

	 */

	COMPACT_COMPLETE,

	/*

	 * direct compaction has scanned part of the zone but wasn't successfull

	 * direct compaction has scanned part of the zone but wasn't successful

	 * to compact suitable pages.

	 */

	COMPACT_PARTIAL_SKIPPED,

include/linux/hmm.h

+1 −1
Original line number Diff line number Diff line
@@ -113,7 +113,7 @@ int hmm_range_fault(struct hmm_range *range); 
 * HMM_RANGE_DEFAULT_TIMEOUT - default timeout (ms) when waiting for a range

 *

 * When waiting for mmu notifiers we need some kind of time out otherwise we

 * could potentialy wait for ever, 1000ms ie 1s sounds like a long time to

 * could potentially wait for ever, 1000ms ie 1s sounds like a long time to

 * wait already.

 */

#define HMM_RANGE_DEFAULT_TIMEOUT 1000

include/linux/hugetlb.h

+3 −3
Original line number Diff line number Diff line
@@ -51,7 +51,7 @@ struct hugepage_subpool { 
	long count;

	long max_hpages;	/* Maximum huge pages or -1 if no maximum. */

	long used_hpages;	/* Used count against maximum, includes */

				/* both alloced and reserved pages. */

				/* both allocated and reserved pages. */

	struct hstate *hstate;

	long min_hpages;	/* Minimum huge pages or -1 if no minimum. */

	long rsv_hpages;	/* Pages reserved against global pool to */
@@ -85,7 +85,7 @@ struct resv_map { 
 * by a resv_map's lock.  The set of regions within the resv_map represent

 * reservations for huge pages, or huge pages that have already been

 * instantiated within the map.  The from and to elements are huge page

 * indicies into the associated mapping.  from indicates the starting index

 * indices into the associated mapping.  from indicates the starting index

 * of the region.  to represents the first index past the end of  the region.

 *

 * For example, a file region structure with from == 0 and to == 4 represents
@@ -797,7 +797,7 @@ static inline bool hugepage_migration_supported(struct hstate *h) 
 * It determines whether or not a huge page should be placed on

 * movable zone or not. Movability of any huge page should be

 * required only if huge page size is supported for migration.

 * There wont be any reason for the huge page to be movable if

 * There won't be any reason for the huge page to be movable if

 * it is not migratable to start with. Also the size of the huge

 * page should be large enough to be placed under a movable zone

 * and still feasible enough to be migratable. Just the presence

include/linux/list_lru.h

+2 −2
Original line number Diff line number Diff line
@@ -146,7 +146,7 @@ typedef enum lru_status (*list_lru_walk_cb)(struct list_head *item, 
 * @lru: the lru pointer.

 * @nid: the node id to scan from.

 * @memcg: the cgroup to scan from.

 * @isolate: callback function that is resposible for deciding what to do with

 * @isolate: callback function that is responsible for deciding what to do with

 *  the item currently being scanned

 * @cb_arg: opaque type that will be passed to @isolate

 * @nr_to_walk: how many items to scan.
@@ -172,7 +172,7 @@ unsigned long list_lru_walk_one(struct list_lru *lru, 
 * @lru: the lru pointer.

 * @nid: the node id to scan from.

 * @memcg: the cgroup to scan from.

 * @isolate: callback function that is resposible for deciding what to do with

 * @isolate: callback function that is responsible for deciding what to do with

 *  the item currently being scanned

 * @cb_arg: opaque type that will be passed to @isolate

 * @nr_to_walk: how many items to scan.

include/linux/mmu_notifier.h

+4 −4
Original line number Diff line number Diff line
@@ -33,7 +33,7 @@ struct mmu_interval_notifier; 
 *

 * @MMU_NOTIFY_SOFT_DIRTY: soft dirty accounting (still same page and same

 * access flags). User should soft dirty the page in the end callback to make

 * sure that anyone relying on soft dirtyness catch pages that might be written

 * sure that anyone relying on soft dirtiness catch pages that might be written

 * through non CPU mappings.

 *

 * @MMU_NOTIFY_RELEASE: used during mmu_interval_notifier invalidate to signal
@@ -167,7 +167,7 @@ struct mmu_notifier_ops { 
	 * decrease the refcount. If the refcount is decreased on

	 * invalidate_range_start() then the VM can free pages as page

	 * table entries are removed.  If the refcount is only

	 * droppped on invalidate_range_end() then the driver itself

	 * dropped on invalidate_range_end() then the driver itself

	 * will drop the last refcount but it must take care to flush

	 * any secondary tlb before doing the final free on the

	 * page. Pages will no longer be referenced by the linux
@@ -196,7 +196,7 @@ struct mmu_notifier_ops { 
	 * If invalidate_range() is used to manage a non-CPU TLB with

	 * shared page-tables, it not necessary to implement the

	 * invalidate_range_start()/end() notifiers, as

	 * invalidate_range() alread catches the points in time when an

	 * invalidate_range() already catches the points in time when an

	 * external TLB range needs to be flushed. For more in depth

	 * discussion on this see Documentation/vm/mmu_notifier.rst

	 *
@@ -369,7 +369,7 @@ mmu_interval_read_retry(struct mmu_interval_notifier *interval_sub, 
 * mmu_interval_read_retry() will return true.

 *

 * False is not reliable and only suggests a collision may not have

 * occured. It can be called many times and does not have to hold the user

 * occurred. It can be called many times and does not have to hold the user

 * provided lock.

 *

 * This call can be used as part of loops and other expensive operations to