All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, chenxuebing@jari.cn,
	akpm@linux-foundation.org
Subject: [merged mm-stable] mm-sparsemem-drop-unexpected-word-a-in-comments.patch removed from -mm tree
Date: Sun, 03 Jul 2022 18:10:55 -0700	[thread overview]
Message-ID: <20220704011055.990F2C341C6@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: mm: sparsemem: drop unexpected word 'a' in comments
has been removed from the -mm tree.  Its filename was
     mm-sparsemem-drop-unexpected-word-a-in-comments.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: "XueBing Chen" <chenxuebing@jari.cn>
Subject: mm: sparsemem: drop unexpected word 'a' in comments
Date: Sat, 25 Jun 2022 16:51:35 +0800 (GMT+08:00)

there is an unexpected word 'a' in the comments that need to be dropped

Link: https://lkml.kernel.org/r/24fbdae3.c86.1819a0f31b9.Coremail.chenxuebing@jari.cn
Signed-off-by: XueBing Chen <chenxuebing@jari.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/sparse-vmemmap.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/mm/sparse-vmemmap.c~mm-sparsemem-drop-unexpected-word-a-in-comments
+++ a/mm/sparse-vmemmap.c
@@ -548,7 +548,7 @@ pte_t * __meminit vmemmap_pte_populate(p
 		} else {
 			/*
 			 * When a PTE/PMD entry is freed from the init_mm
-			 * there's a a free_pages() call to this page allocated
+			 * there's a free_pages() call to this page allocated
 			 * above. Thus this get_page() is paired with the
 			 * put_page_testzero() on the freeing path.
 			 * This can only called by certain ZONE_DEVICE path,
_

Patches currently in -mm which might be from chenxuebing@jari.cn are



                 reply	other threads:[~2022-07-04  1:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220704011055.990F2C341C6@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=chenxuebing@jari.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.