From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, eb@emlix.com, akpm@linux-foundation.org
Subject: [merged mm-stable] mm-fix-typo-in-struct-vm_operations_struct-comments.patch removed from -mm tree
Date: Tue, 08 Nov 2022 17:38:21 -0800 [thread overview]
Message-ID: <20221109013822.1285CC433B5@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: fix typo in struct vm_operations_struct comments
has been removed from the -mm tree. Its filename was
mm-fix-typo-in-struct-vm_operations_struct-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: Rolf Eike Beer <eb@emlix.com>
Subject: mm: fix typo in struct vm_operations_struct comments
Date: Fri, 07 Oct 2022 13:37:41 +0200
There is no eprotect(), so I assume this is about mprotect().
Link: https://lkml.kernel.org/r/2385684.8vm7BOzihM@mobilepool36.emlix.com
Signed-off-by: Rolf Eike Beer <eb@emlix.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/include/linux/mm.h~mm-fix-typo-in-struct-vm_operations_struct-comments
+++ a/include/linux/mm.h
@@ -549,7 +549,7 @@ struct vm_operations_struct {
/*
* Called by mprotect() to make driver-specific permission
* checks before mprotect() is finalised. The VMA must not
- * be modified. Returns 0 if eprotect() can proceed.
+ * be modified. Returns 0 if mprotect() can proceed.
*/
int (*mprotect)(struct vm_area_struct *vma, unsigned long start,
unsigned long end, unsigned long newflags);
_
Patches currently in -mm which might be from eb@emlix.com are
reply other threads:[~2022-11-09 1:38 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=20221109013822.1285CC433B5@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=eb@emlix.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.