All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,urezki@gmail.com,bhe@redhat.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] mm-vmalloc-fix-lockdep-warning-fix.patch removed from -mm tree
Date: Fri, 05 Apr 2024 11:20:07 -0700	[thread overview]
Message-ID: <20240405182008.6911EC433F1@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: mm-vmalloc-fix-lockdep-warning-fix
has been removed from the -mm tree.  Its filename was
     mm-vmalloc-fix-lockdep-warning-fix.patch

This patch was dropped because it was folded into mm-vmalloc-fix-lockdep-warning.patch

------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-vmalloc-fix-lockdep-warning-fix
Date: Fri Apr  5 11:16:02 AM PDT 2024

fix comment typos, per Baoquan

Cc: Baoquan He <bhe@redhat.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/vmalloc.c |    7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

--- a/mm/vmalloc.c~mm-vmalloc-fix-lockdep-warning-fix
+++ a/mm/vmalloc.c
@@ -1064,10 +1064,9 @@ repeat:
 	}
 
 	/*
-	 * Check if found VA exists, it might it is gone away.
-	 * In this case we repeat the search because a VA has
-	 * been removed concurrently thus we need to proceed
-	 * with next one what is a rare case.
+	 * Check if found VA exists, it might have gone away.  In this case we
+	 * repeat the search because a VA has been removed concurrently and we
+	 * need to proceed to the next one, which is a rare case.
 	 */
 	if (va_start_lowest) {
 		vn = addr_to_node(va_start_lowest);
_

Patches currently in -mm which might be from akpm@linux-foundation.org are

mm-vmalloc-fix-lockdep-warning.patch
mm-sparc-change-pxd_huge-behavior-to-exclude-swap-entries-fix.patch
mm-hold-ptl-from-the-first-pte-while-reclaiming-a-large-folio-fix.patch
sh-remove-use-of-pg_arch_1-on-individual-pages-fix.patch
mm-gup-drop-folio_fast_pin_allowed-in-hugepd-processing-fix.patch
mm-allow-anon-exclusive-check-over-hugetlb-tail-pages-fix.patch
__mod_memcg_lruvec_state-enhance-diagnostics.patch
__mod_memcg_lruvec_state-enhance-diagnostics-fix.patch


                 reply	other threads:[~2024-04-05 18:20 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=20240405182008.6911EC433F1@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=urezki@gmail.com \
    /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.