From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: arnd@arndb.de
Cc: gregkh@linuxfoundation.org, willy@infradead.org,
geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: [PATCH v3 0/2] mm: PAGE_KERNEL_* fallbacks
Date: Thu, 10 May 2018 11:55:05 -0700 [thread overview]
Message-ID: <20180510185507.2439-1-mcgrof@kernel.org> (raw)
This is the 3rd iteration for moving PAGE_KERNEL_* fallback
definitions into asm-generic headers. Greg asked for a Changelog
for patch iteration changes, its below.
All these patches have been tested by 0-day.
Questions, and specially flames are greatly appreciated.
v3:
Removed documentation effort to keep tabs on which architectures
currently don't defint the respective PAGE_* flags. Keeping tabs
on this is just not worth it.
Ran a spell checker on all patches :)
v2:
I added a patch for PAGE_KERNEL_EXEC as suggested by Matthew Wilcox.
v1:
I sent out a patch just for dealing witht he fallback mechanism for
PAGE_KERNEL_RO.
Luis R. Rodriguez (2):
mm: provide a fallback for PAGE_KERNEL_RO for architectures
mm: provide a fallback for PAGE_KERNEL_EXEC for architectures
drivers/base/firmware_loader/fallback.c | 5 -----
include/asm-generic/pgtable.h | 18 ++++++++++++++++++
mm/nommu.c | 4 ----
mm/vmalloc.c | 4 ----
4 files changed, 18 insertions(+), 13 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-10 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 18:55 Luis R. Rodriguez [this message]
2018-05-10 18:55 ` [PATCH v3 1/2] mm: provide a fallback for PAGE_KERNEL_RO for architectures Luis R. Rodriguez
2018-05-10 18:55 ` [PATCH v3 2/2] mm: provide a fallback for PAGE_KERNEL_EXEC " Luis R. Rodriguez
2018-05-16 16:44 ` [PATCH v3 0/2] mm: PAGE_KERNEL_* fallbacks Luis R. Rodriguez
2018-05-23 21:35 ` Luis R. Rodriguez
2018-05-30 19:55 ` Luis R. Rodriguez
2018-05-30 20:06 ` Greg KH
2018-05-30 20:21 ` Luis R. Rodriguez
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=20180510185507.2439-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox