From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Linux-MM <linux-mm@kvack.org>, kernel test robot <lkp@intel.com>,
Anatoly Pugachev <matorola@gmail.com>,
mm-commits@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] sparc32: fix page table traversal in srmmu_nocache_init()
Date: Sat, 23 May 2020 14:00:07 -0700 [thread overview]
Message-ID: <CAHk-=wjW8QoT9Kawf1tkQdqsAJdLQakj_fh_XS6SeQO990DdtQ@mail.gmail.com> (raw)
In-Reply-To: <20200523195718.1479419-1-rppt@linux.ibm.com>
On Sat, May 23, 2020 at 12:57 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
>
> Remove __nocache_fix() for p4d_offset() and pud_offset() and keep it only
> for PUD and lower levels.
Davem - I took this directly, since it's a fix for the patch Andrew
sent and I merged that way. Just so you know.
Linus
prev parent reply other threads:[~2020-05-23 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 19:57 Mike Rapoport
2020-05-23 21:00 ` Linus Torvalds [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='CAHk-=wjW8QoT9Kawf1tkQdqsAJdLQakj_fh_XS6SeQO990DdtQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=matorola@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox