From: Marcelo Tosatti <mtosatti@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: kvm_vm_ioctl_get_dirty_log() fix and cleanup
Date: Tue, 22 Jun 2010 18:56:15 +0000 [thread overview]
Message-ID: <20100622185615.GA11573@amt.cnet> (raw)
In-Reply-To: <20100622180358.be8fd912.yoshikawa.takuya@oss.ntt.co.jp>
On Tue, Jun 22, 2010 at 06:03:58PM +0900, Takuya Yoshikawa wrote:
> This patch set is for making dirty logging development, and of course
> maintenance, easier. Please see individual patches for details.
>
> Takuya
>
> ---
> arch/ia64/kvm/kvm-ia64.c | 54 ++++++++++++++++++--------------------------
> arch/powerpc/kvm/book3s.c | 29 ++++++++++++++----------
> arch/x86/kvm/x86.c | 14 +----------
> include/linux/kvm_host.h | 6 +---
> virt/kvm/kvm_main.c | 24 +++++--------------
> 5 files changed, 50 insertions(+), 77 deletions(-)
>
> --
> 1.7.0.4
Looks good to me.
next prev parent reply other threads:[~2010-06-22 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 9:03 [PATCH 0/4] KVM: kvm_vm_ioctl_get_dirty_log() fix and cleanup Takuya Yoshikawa
2010-06-22 18:56 ` Marcelo Tosatti [this message]
2010-06-23 1:09 ` Takuya Yoshikawa
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=20100622185615.GA11573@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm-ia64@vger.kernel.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