From: Christoph Hellwig <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 08/21] x86: clean up ioremap
Date: Mon, 28 Oct 2019 16:29:56 +0100 [thread overview]
Message-ID: <20191028152956.GA28048@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1910211019540.1904@nanos.tec.linutronix.de>
On Mon, Oct 21, 2019 at 10:23:03AM +0200, Thomas Gleixner wrote:
> Should this go with your larger series or can this be picked up
> independently?
This should all go together.
next prev parent reply other threads:[~2019-10-28 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191017174554.29840-1-hch@lst.de>
[not found] ` <20191017174554.29840-21-hch@lst.de>
2019-10-21 7:58 ` [OpenRISC] [PATCH 20/21] csky: remove ioremap_cache Guo Ren
2019-11-05 1:26 ` Christoph Hellwig
[not found] ` <20191017174554.29840-9-hch@lst.de>
2019-10-21 8:23 ` [OpenRISC] [PATCH 08/21] x86: clean up ioremap Thomas Gleixner
2019-10-28 15:29 ` Christoph Hellwig [this message]
[not found] ` <20191017174554.29840-4-hch@lst.de>
2019-10-21 8:47 ` [OpenRISC] [PATCH 03/21] ia64: rename ioremap_nocache to ioremap_uc Sergei Shtylyov
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=20191028152956.GA28048@lst.de \
--to=hch@lst.de \
--cc=openrisc@lists.librecores.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;
as well as URLs for NNTP newsgroup(s).