All of lore.kernel.org
 help / color / mirror / Atom feed
* + mm-fixed-multiple-typos-in-multiple-files.patch added to mm-unstable branch
@ 2023-10-23 18:00 Andrew Morton
  0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2023-10-23 18:00 UTC (permalink / raw)
  To: mm-commits, willy, rdunlap, James.Bottomley, m.muzzammilashraf,
	akpm


The patch titled
     Subject: mm: fix multiple typos in multiple files
has been added to the -mm mm-unstable branch.  Its filename is
     mm-fixed-multiple-typos-in-multiple-files.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-fixed-multiple-typos-in-multiple-files.patch

This patch will later appear in the mm-unstable branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days

------------------------------------------------------
From: Muhammad Muzammil <m.muzzammilashraf@gmail.com>
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@gmail.com
Signed-off-by: Muhammad Muzammil <m.muzzammilashraf@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Muhammad Muzammil <m.muzzammilashraf@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 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
@@ -601,7 +601,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
@@ -843,7 +843,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.
@@ -8080,7 +8080,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@gmail.com are

mm-fixed-multiple-typos-in-multiple-files.patch


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-10-23 18:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-23 18:00 + mm-fixed-multiple-typos-in-multiple-files.patch added to mm-unstable branch Andrew Morton

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.