From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] Consolidate identity mapping code in idmap.c
Date: Wed, 30 Nov 2011 22:18:00 +0000 [thread overview]
Message-ID: <20111130221800.GV9581@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1322504937-24718-1-git-send-email-will.deacon@arm.com>
On Mon, Nov 28, 2011 at 06:28:51PM +0000, Will Deacon wrote:
> Hello,
>
> This is version 2 of the patch series originally posted here:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2011-November/073033.html
>
> Changes from v1 include:
> * Updated following Catalin's comments
> * Rebased onto rmk/devel-stable
> * Includes update to SMP booting so that the idmap_pgd can be
> used there too
>
> This is a pre-requisite for my kexec patches, which I will post separately.
>
> All feedback welcome.
This patch set looks fine.
next prev parent reply other threads:[~2011-11-30 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 18:28 [PATCH v2 0/6] Consolidate identity mapping code in idmap.c Will Deacon
2011-11-28 18:28 ` [PATCH v2 1/6] ARM: idmap: populate identity map pgd at init time using .init.text Will Deacon
2011-11-30 11:29 ` Catalin Marinas
2011-11-28 18:28 ` [PATCH v2 2/6] ARM: suspend: use idmap_pgd instead of suspend_pgd Will Deacon
2011-11-28 18:28 ` [PATCH v2 3/6] ARM: proc-*.S: place cpu_reset functions into .idmap.text section Will Deacon
2011-11-28 18:28 ` [PATCH v2 4/6] ARM: idmap: use idmap_pgd when setting up mm for reboot Will Deacon
2011-11-30 11:31 ` Catalin Marinas
2011-11-30 14:37 ` Will Deacon
2011-11-28 18:28 ` [PATCH v2 5/6] ARM: head.S: only include __turn_mmu_on in the initial identity mapping Will Deacon
2011-11-28 18:28 ` [PATCH v2 6/6] ARM: SMP: use idmap_pgd for mapping MMU enable during secondary booting Will Deacon
2011-11-30 22:18 ` Russell King - ARM Linux [this message]
2011-12-01 13:26 ` [PATCH v2 0/6] Consolidate identity mapping code in idmap.c Will Deacon
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=20111130221800.GV9581@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).