From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,lorenzo.stoakes@oracle.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] mm-correctly-handle-uffd-pte-markers-fix.patch removed from -mm tree
Date: Mon, 24 Nov 2025 14:51:10 -0800 [thread overview]
Message-ID: <20251124225111.46147C4CEF1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-correctly-handle-uffd-pte-markers-fix
has been removed from the -mm tree. Its filename was
mm-correctly-handle-uffd-pte-markers-fix.patch
This patch was dropped because it was folded into mm-correctly-handle-uffd-pte-markers.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-correctly-handle-uffd-pte-markers-fix
Date: Thu Nov 20 01:21:44 PM PST 2025
fix comment typo, per Mike
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Mike Rapoport (Microsoft) <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/userfaultfd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/userfaultfd.c~mm-correctly-handle-uffd-pte-markers-fix
+++ a/fs/userfaultfd.c
@@ -312,7 +312,7 @@ again:
return true;
/*
- * A race could arise which would result in a softleaf entry such a
+ * A race could arise which would result in a softleaf entry such as
* migration entry unexpectedly being present in the PMD, so explicitly
* check for this and bail out if so.
*/
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-correctly-handle-uffd-pte-markers.patch
mm-huge_memoryc-introduce-folio_split_unmapped-v2-fix-fix.patch
memblock-unpreserve-memory-in-case-of-error-fix.patch
reply other threads:[~2025-11-24 22:51 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=20251124225111.46147C4CEF1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@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.