From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, jingyuwang_vip@163.com,
akpm@linux-foundation.org
Subject: [merged mm-stable] mm-gupc-fix-typo-in-comments.patch removed from -mm tree
Date: Tue, 28 Mar 2023 16:21:58 -0700 [thread overview]
Message-ID: <20230328232158.E0403C433EF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/gup.c: fix typo in comments
has been removed from the -mm tree. Its filename was
mm-gupc-fix-typo-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: Jingyu Wang <jingyuwang_vip@163.com>
Subject: mm/gup.c: fix typo in comments
Date: Thu, 9 Mar 2023 18:48:13 +0800
Link: https://lkml.kernel.org/r/20230309104813.170309-1-jingyuwang_vip@163.com
Signed-off-by: Jingyu Wang <jingyuwang_vip@163.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/gup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/gup.c~mm-gupc-fix-typo-in-comments
+++ a/mm/gup.c
@@ -2193,7 +2193,7 @@ static bool is_valid_gup_args(struct pag
* This does not guarantee that the page exists in the user mappings when
* get_user_pages_remote returns, and there may even be a completely different
* page there in some cases (eg. if mmapped pagecache has been invalidated
- * and subsequently re faulted). However it does guarantee that the page
+ * and subsequently re-faulted). However it does guarantee that the page
* won't be freed completely. And mostly callers simply care that the page
* contains data that was valid *at some point in time*. Typically, an IO
* or similar operation cannot guarantee anything stronger anyway because
_
Patches currently in -mm which might be from jingyuwang_vip@163.com are
reply other threads:[~2023-03-28 23:22 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=20230328232158.E0403C433EF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=jingyuwang_vip@163.com \
--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.