From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, ahuang12@lenovo.com,
akpm@linux-foundation.org
Subject: [merged mm-stable] mm-rmap-fix-typos-in-comments.patch removed from -mm tree
Date: Mon, 09 May 2022 21:15:44 -0700 [thread overview]
Message-ID: <20220510041545.167E2C385C5@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/rmap: Fix typos in comments
has been removed from the -mm tree. Its filename was
mm-rmap-fix-typos-in-comments.patch
This patch was dropped because it was merged into mm-stable
------------------------------------------------------
From: Adrian Huang <ahuang12@lenovo.com>
Subject: mm/rmap: Fix typos in comments
Fix spelling/grammar mistakes in comments.
Link: https://lkml.kernel.org/r/20220428061522.666-1-adrianhuang0701@gmail.com
Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/rmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/rmap.c~mm-rmap-fix-typos-in-comments
+++ a/mm/rmap.c
@@ -298,7 +298,7 @@ int anon_vma_clone(struct vm_area_struct
* Reuse existing anon_vma if its degree lower than two,
* that means it has no vma and only one anon_vma child.
*
- * Do not chose parent anon_vma, otherwise first child
+ * Do not choose parent anon_vma, otherwise first child
* will always reuse it. Root anon_vma is never reused:
* it has self-parent reference and at least one child.
*/
@@ -2249,7 +2249,7 @@ static bool folio_make_device_exclusive(
/**
* make_device_exclusive_range() - Mark a range for exclusive use by a device
- * @mm: mm_struct of assoicated target process
+ * @mm: mm_struct of associated target process
* @start: start of the region to mark for exclusive device access
* @end: end address of region
* @pages: returns the pages which were successfully marked for exclusive access
_
Patches currently in -mm which might be from ahuang12@lenovo.com are
reply other threads:[~2022-05-10 4:18 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=20220510041545.167E2C385C5@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=ahuang12@lenovo.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.