From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] generic early_ioremap support
Date: Tue, 7 Jan 2014 17:26:32 +0000 [thread overview]
Message-ID: <20140107172632.GC6234@arm.com> (raw)
In-Reply-To: <1389062120-31896-1-git-send-email-msalter@redhat.com>
On Tue, Jan 07, 2014 at 02:35:15AM +0000, Mark Salter wrote:
> This patch series takes the common bits from the x86 early ioremap
> implementation and creates a generic implementation which may be used
> by other architectures. The early ioremap interfaces are intended for
> situations where boot code needs to make temporary virtual mappings
> before the normal ioremap interfaces are available. Typically, this
> means before paging_init() has run.
>
> These patches are layered on top of generic fixmap patches which
> were discussed here (and are in the akpm tree):
>
> http://lkml.org/lkml/2013/11/25/474
>
> This is version 2 of the patch series. These patches (and underlying
> fixmap patches) may be found at:
>
> git://github.com/mosalter/linux.git (early-ioremap-v2 branch)
The patches look fine to me. I haven't acked the arm64 patches as I'll
eventually merge/sign them off once the first patch in the series goes
in.
Thanks.
--
Catalin
prev parent reply other threads:[~2014-01-07 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 2:35 [PATCH v2 0/5] generic early_ioremap support Mark Salter
2014-01-07 2:35 ` [PATCH v2 1/5] mm: create generic early_ioremap() support Mark Salter
2014-01-07 15:25 ` Catalin Marinas
2014-01-07 23:11 ` H. Peter Anvin
2014-01-08 16:09 ` Mark Salter
2014-01-09 10:15 ` Matt Fleming
2014-01-07 2:35 ` [PATCH v2 3/5] arm: add early_ioremap support Mark Salter
2014-01-07 17:23 ` Catalin Marinas
2014-01-07 2:35 ` [PATCH v2 4/5] arm64: initialize pgprot info earlier in boot Mark Salter
2014-01-07 2:35 ` [PATCH v2 5/5] arm64: add early_ioremap support Mark Salter
2014-01-07 17:26 ` Catalin Marinas [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=20140107172632.GC6234@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).