From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, guoren@kernel.org, chris@zankel.net,
anshuman.khandual@arm.com, jcmvbkbc@gmail.com,
akpm@linux-foundation.org
Subject: + xtensa-mm-enable-arch_has_vm_get_page_prot-fix.patch added to mm-unstable branch
Date: Tue, 05 Jul 2022 15:26:15 -0700 [thread overview]
Message-ID: <20220705222616.28644C341C7@smtp.kernel.org> (raw)
The patch titled
Subject: xtensa: noMMU: fix vm_get_page_prot definition
has been added to the -mm mm-unstable branch. Its filename is
xtensa-mm-enable-arch_has_vm_get_page_prot-fix.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/xtensa-mm-enable-arch_has_vm_get_page_prot-fix.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: Max Filippov <jcmvbkbc@gmail.com>
Subject: xtensa: noMMU: fix vm_get_page_prot definition
Date: Tue, 5 Jul 2022 15:14:11 -0700
Don't define protection_map and don't use DECLARE_VM_GET_PAGE_PROT in
noMMU configs, because in that case the definition for vm_get_page_prot is
provided by the include/linux/mm.h
Link: https://lkml.kernel.org/r/20220705221411.3381797-1-jcmvbkbc@gmail.com
Fixes: 61ab8053710f ("xtensa/mm: enable ARCH_HAS_VM_GET_PAGE_PROT")
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Chris Zankel <chris@zankel.net>
Cc: Guo Ren <guoren@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/xtensa/mm/init.c | 2 ++
1 file changed, 2 insertions(+)
--- a/arch/xtensa/mm/init.c~xtensa-mm-enable-arch_has_vm_get_page_prot-fix
+++ a/arch/xtensa/mm/init.c
@@ -217,6 +217,7 @@ static int __init parse_memmap_opt(char
}
early_param("memmap", parse_memmap_opt);
+#ifdef CONFIG_MMU
static const pgprot_t protection_map[16] = {
[VM_NONE] = PAGE_NONE,
[VM_READ] = PAGE_READONLY,
@@ -236,3 +237,4 @@ static const pgprot_t protection_map[16]
[VM_SHARED | VM_EXEC | VM_WRITE | VM_READ] = PAGE_SHARED_EXEC
};
DECLARE_VM_GET_PAGE_PROT
+#endif
_
Patches currently in -mm which might be from jcmvbkbc@gmail.com are
xtensa-mm-enable-arch_has_vm_get_page_prot-fix.patch
reply other threads:[~2022-07-05 22:26 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=20220705222616.28644C341C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=chris@zankel.net \
--cc=guoren@kernel.org \
--cc=jcmvbkbc@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.