From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: head.S cleanup
Date: Tue, 21 Mar 2017 15:37:11 +0000 [thread overview]
Message-ID: <20170321153711.GC8319@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1487170457-17986-1-git-send-email-mark.rutland@arm.com>
On Wed, Feb 15, 2017 at 02:54:15PM +0000, Mark Rutland wrote:
> Mark Rutland (2):
> arm64: reduce el2_setup branching
> arm64: move !VHE work to end of el2_setup
Mark, Marc, do these patches conflict with the hyp stub cleanup? If
there is some overlap, I'm happy for them to go via the kvm tree
together with the others.
--
Catalin
next prev parent reply other threads:[~2017-03-21 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:54 [PATCH 0/2] arm64: head.S cleanup Mark Rutland
2017-02-15 14:54 ` [PATCH 1/2] arm64: reduce el2_setup branching Mark Rutland
2017-03-21 15:43 ` Marc Zyngier
2017-02-15 14:54 ` [PATCH 2/2] arm64: move !VHE work to end of el2_setup Mark Rutland
2017-03-21 15:47 ` Marc Zyngier
2017-03-21 15:37 ` Catalin Marinas [this message]
2017-03-21 15:51 ` [PATCH 0/2] arm64: head.S cleanup Marc Zyngier
2017-03-21 16:03 ` Catalin Marinas
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=20170321153711.GC8319@e104818-lin.cambridge.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).