From: Christoph Hellwig <hch@lst.de>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: two small nommu cleanups
Date: Tue, 23 Apr 2019 18:30:57 +0200 [thread overview]
Message-ID: <20190423163059.8820-1-hch@lst.de> (raw)
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.
next reply other threads:[~2019-04-23 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 16:30 Christoph Hellwig [this message]
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
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=20190423163059.8820-1-hch@lst.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.