From: Palmer Dabbelt <palmerdabbelt@google.com>
To: penberg@gmail.com
Cc: rientjes@google.com, akpm@linux-foundation.org,
linux-riscv@lists.infradead.org, linux-mm@kvack.org,
rppt@linux.ibm.com, thomas.lendacky@amd.com
Subject: Re: [PATCH v2 1/2] mm: pgtable: Make generic pgprot_* macros available for no-MMU
Date: Tue, 21 Jul 2020 20:29:25 -0700 (PDT) [thread overview]
Message-ID: <mhng-de42568c-1963-4b45-8ad2-be5ac849be2f@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <CAOJsxLGm0B15nsyRNTCOYWUXLbjRSc-CTtv-Mv-OLq2k3ZjMvQ@mail.gmail.com>
On Thu, 16 Jul 2020 23:14:10 PDT (-0700), penberg@gmail.com wrote:
> On Wed, 15 Jul 2020, Pekka Enberg wrote:
>> > From: Pekka Enberg <penberg@kernel.org>
>> >
>> > The <linux/pgtable.h> header defines some generic pgprot_*
>> > implementations, but they are only available when CONFIG_MMU is enabled.
>> > The RISC-V architecture, for example, therefore defines some of these
>> > pgprot_* macros for !NOMMU.
>> >
>> > Let's make the pgprot_* generic available even for !NOMMU so we can
>> > remove the RISC-V specific definitions.
>> >
>> > Compile-tested with x86 defconfig, and riscv defconfig and !MMU defconfig.
>> >
>> > Suggested-by: Palmer Dabbelt <palmerdabbelt@google.com>
>> > Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
>> > Cc: Tom Lendacky <thomas.lendacky@amd.com>
>> > Signed-off-by: Pekka Enberg <penberg@kernel.org>
>
> On Wed, Jul 15, 2020 at 8:39 PM David Rientjes <rientjes@google.com> wrote:
>> Acked-by: David Rientjes <rientjes@google.com>
>
> Palmer, will you pick up these patches in the riscv tree, or should I
> ask Andrew to queue them in -mm?
I just put them on for-next. Thanks!
prev parent reply other threads:[~2020-07-22 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 5:33 Pekka Enberg
2020-07-15 5:33 ` [PATCH v2 2/2] riscv: Use generic pgprot_* macros from <linux/pgtable.h> Pekka Enberg
2020-07-15 17:39 ` [PATCH v2 1/2] mm: pgtable: Make generic pgprot_* macros available for no-MMU David Rientjes
2020-07-17 6:14 ` Pekka Enberg
2020-07-22 3:29 ` Palmer Dabbelt [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=mhng-de42568c-1963-4b45-8ad2-be5ac849be2f@palmerdabbelt-glaptop1 \
--to=palmerdabbelt@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=penberg@gmail.com \
--cc=rientjes@google.com \
--cc=rppt@linux.ibm.com \
--cc=thomas.lendacky@amd.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