The quilt patch titled Subject: mm: fix multiple typos in multiple files has been removed from the -mm tree. Its filename was mm-fixed-multiple-typos-in-multiple-files.patch This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: Muhammad Muzammil <m.muzzammilashraf@xxxxxxxxx> Subject: mm: fix multiple typos in multiple files Date: Mon, 23 Oct 2023 17:44:05 +0500 Link: https://lkml.kernel.org/r/20231023124405.36981-1-m.muzzammilashraf@xxxxxxxxx Signed-off-by: Muhammad Muzammil <m.muzzammilashraf@xxxxxxxxx> Reviewed-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> Cc: "James E.J. Bottomley" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> Cc: Matthew Wilcox (Oracle) <willy@xxxxxxxxxxxxx> Cc: Muhammad Muzammil <m.muzzammilashraf@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/debug_vm_pgtable.c | 4 ++-- mm/internal.h | 2 +- mm/memcontrol.c | 4 ++-- mm/mmap.c | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) --- a/mm/debug_vm_pgtable.c~mm-fixed-multiple-typos-in-multiple-files +++ a/mm/debug_vm_pgtable.c @@ -1322,8 +1322,8 @@ static int __init debug_vm_pgtable(void) * true irrespective of the starting protection value for a * given page table entry. * - * Protection based vm_flags combinatins are always linear - * and increasing i.e starting from VM_NONE and going upto + * Protection based vm_flags combinations are always linear + * and increasing i.e starting from VM_NONE and going up to * (VM_SHARED | READ | WRITE | EXEC). */ #define VM_FLAGS_START (VM_NONE) --- a/mm/internal.h~mm-fixed-multiple-typos-in-multiple-files +++ a/mm/internal.h @@ -592,7 +592,7 @@ extern bool mlock_future_ok(struct mm_st * range. * "fully mapped" means all the pages of folio is associated with the page * table of range while this function just check whether the folio range is - * within the range [start, end). Funcation caller nees to do page table + * within the range [start, end). Function caller needs to do page table * check if it cares about the page table association. * * Typical usage (like mlock or madvise) is: --- a/mm/memcontrol.c~mm-fixed-multiple-typos-in-multiple-files +++ a/mm/memcontrol.c @@ -819,7 +819,7 @@ void __mod_memcg_lruvec_state(struct lru memcg = pn->memcg; /* - * The caller from rmap relay on disabled preemption becase they never + * The caller from rmap relies on disabled preemption because they never * update their counter from in-interrupt context. For these two * counters we check that the update is never performed from an * interrupt context while other caller need to have disabled interrupt. @@ -8044,7 +8044,7 @@ static struct cftype memsw_files[] = { * * This doesn't check for specific headroom, and it is not atomic * either. But with zswap, the size of the allocation is only known - * once compression has occured, and this optimistic pre-check avoids + * once compression has occurred, and this optimistic pre-check avoids * spending cycles on compression when there is already no room left * or zswap is disabled altogether somewhere in the hierarchy. */ --- a/mm/mmap.c~mm-fixed-multiple-typos-in-multiple-files +++ a/mm/mmap.c @@ -1223,7 +1223,7 @@ unsigned long do_mmap(struct file *file, * Does the application expect PROT_READ to imply PROT_EXEC? * * (the exception is when the underlying filesystem is noexec - * mounted, in which case we dont add PROT_EXEC.) + * mounted, in which case we don't add PROT_EXEC.) */ if ((prot & PROT_READ) && (current->personality & READ_IMPLIES_EXEC)) if (!(file && path_noexec(&file->f_path))) _ Patches currently in -mm which might be from m.muzzammilashraf@xxxxxxxxx are