From: Palmer Dabbelt <palmer@sifive.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: two small nommu cleanups
Date: Mon, 29 Apr 2019 16:23:40 -0700 (PDT) [thread overview]
Message-ID: <mhng-3cb7e3ad-f586-46e0-8c29-48ab828607d2@palmer-si-x1e> (raw)
In-Reply-To: <20190429115526.GA30572@lst.de>
On Mon, 29 Apr 2019 04:55:26 PDT (-0700), Christoph Hellwig wrote:
> Any comments? It would be nice to get this in for this merge window
> to make my life simpler with the RISC-V tree next merge window..
>
> On Tue, Apr 23, 2019 at 06:30:57PM +0200, Christoph Hellwig wrote:
>> Hi all,
>>
>> these two patches avoid writing some boilerplate code for the upcoming
>> RISC-V nommu support, and might also help to clean up existing nommu
>> support in other architectures down the road.
> ---end quoted text---
I don't actually see any patches, can you point me to something?
prev parent reply other threads:[~2019-04-29 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 16:30 Christoph Hellwig
2019-04-23 16:30 ` [PATCH 1/2] mm: provide a print_vma_addr stub for !CONFIG_MMU Christoph Hellwig
2019-04-23 16:30 ` [PATCH 2/2] mm: stub out all of swapops.h " Christoph Hellwig
2019-04-29 11:55 ` two small nommu cleanups Christoph Hellwig
2019-04-29 23:23 ` 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-3cb7e3ad-f586-46e0-8c29-48ab828607d2@palmer-si-x1e \
--to=palmer@sifive.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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