From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm/arm64: KVM: Fix and refactor unmap_range
Date: Wed, 4 Jun 2014 15:16:03 +0200 [thread overview]
Message-ID: <20140604131603.GC19587@lvm> (raw)
In-Reply-To: <080001cf7e3c$646ebc30$2d4c3490$@samsung.com>
On Mon, Jun 02, 2014 at 05:26:46PM +0900, Jungseok Lee wrote:
> On Wednesday, May 28, 2014 11:23 PM, Christoffer Dall wrote:
[...]
>
> This is a pretty good idea. It helps to accommodate different translation
> level options supported by ARMv8.
>
> It looks reasonable to me:
>
> Reviewed-by: Jungseok Lee <jays.lee@samsung.com>
>
Thanks!
next prev parent reply other threads:[~2014-06-04 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 14:22 [PATCH v2] arm/arm64: KVM: Fix and refactor unmap_range Christoffer Dall
2014-06-02 8:26 ` Jungseok Lee
2014-06-04 13:16 ` Christoffer Dall [this message]
2014-06-02 17:29 ` Mario Smarduch
2014-06-04 13:22 ` Christoffer Dall
2014-06-03 13:52 ` Steve Capper
2014-06-04 13:30 ` Christoffer Dall
2014-06-04 13:37 ` Marc Zyngier
2014-06-04 13:54 ` Christoffer Dall
2014-06-04 13:59 ` Steve Capper
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=20140604131603.GC19587@lvm \
--to=christoffer.dall@linaro.org \
--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).