From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
Matthew Wilcox <mawilcox@microsoft.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures
Date: Thu, 10 May 2018 01:24:26 +0000 [thread overview]
Message-ID: <20180510012426.GA27853@wotan.suse.de> (raw)
In-Reply-To: <20180502151113.GB27853@wotan.suse.de>
On Wed, May 02, 2018 at 03:11:13PM +0000, Luis R. Rodriguez wrote:
> On Wed, May 02, 2018 at 12:08:57PM +0200, Geert Uytterhoeven wrote:
> > Hi Luis,
> >
> > On Sat, Apr 28, 2018 at 2:15 AM, Luis R. Rodriguez <mcgrof@kernel.org> wrote:
> > > Some architectures do not define PAGE_KERNEL_RO, best we can do
> > > for them is to provide a fallback onto PAGE_KERNEL. Remove the
> > > hack from the firmware loader and move it onto the asm-generic
> > > header, and document while at it the affected architectures
> > > which do not have a PAGE_KERNEL_RO:
> > >
> > > o alpha
> > > o ia64
> > > o m68k
> > > o mips
> > > o sparc64
> > > o sparc
> > >
> > > Blessed-by: 0-day
> > > Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
> >
> > I believe the "best we can do" is to add the missing definitions for the
> > architectures where the hardware does support it?
>
> True, but we cannot wait for every architecture to implement a feature to then
> such generics upstream,
Come to think of it your point was the wording. I changed it to not be as misleading.
Luis
prev parent reply other threads:[~2018-05-10 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 0:15 [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures Luis R. Rodriguez
2018-04-28 3:18 ` Matthew Wilcox
2018-05-09 1:04 ` Luis R. Rodriguez
2018-05-09 1:39 ` Matthew Wilcox
2018-05-10 1:15 ` Luis R. Rodriguez
2018-04-28 5:04 ` Greg KH
2018-05-02 10:08 ` Geert Uytterhoeven
2018-05-02 15:11 ` Luis R. Rodriguez
2018-05-10 1:24 ` Luis R. Rodriguez [this message]
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=20180510012426.GA27853@wotan.suse.de \
--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-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
/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;
as well as URLs for NNTP newsgroup(s).