From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, jongwooo.han@gmail.com,
akpm@linux-foundation.org
Subject: + mm-fix-typo-in-comments.patch added to mm-unstable branch
Date: Wed, 25 Jan 2023 16:45:55 -0800 [thread overview]
Message-ID: <20230126004556.1FAC0C433EF@smtp.kernel.org> (raw)
The patch titled
Subject: mm/gup.c: fix typo in comments
has been added to the -mm mm-unstable branch. Its filename is
mm-fix-typo-in-comments.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-fix-typo-in-comments.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: Jongwoo Han <jongwooo.han@gmail.com>
Subject: mm/gup.c: fix typo in comments
Date: Thu, 26 Jan 2023 03:08:47 +0900
Link: https://lkml.kernel.org/r/20230125180847.4542-1-jongwooo.han@gmail.com
Signed-off-by: Jongwoo Han <jongwooo.han@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/mm/gup.c~mm-fix-typo-in-comments
+++ a/mm/gup.c
@@ -1055,7 +1055,7 @@ static int check_vma_flags(struct vm_are
* This does not guarantee that the page exists in the user mappings when
* __get_user_pages 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 jongwooo.han@gmail.com are
mm-fix-typo-in-comments.patch
reply other threads:[~2023-01-26 0:45 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=20230126004556.1FAC0C433EF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=jongwooo.han@gmail.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.