public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Cc: "cornelia.huck@de.ibm.com" <cornelia.huck@de.ibm.com>,
	"Alex.Williamson@redhat.com" <Alex.Williamson@redhat.com>,
	"agraf@suse.de" <agraf@suse.de>,
	"gleb@kernel.org" <gleb@kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>
Subject: Re: [PATCH v3 0/4] Make kvm_device_ops registration dynamic
Date: Thu, 11 Sep 2014 18:12:13 +0100	[thread overview]
Message-ID: <20140911171213.GC6158@arm.com> (raw)
In-Reply-To: <1409650056-27065-1-git-send-email-will.deacon@arm.com>

Hi Paolo,

On Tue, Sep 02, 2014 at 10:27:32AM +0100, Will Deacon wrote:
> Hi all,
> 
> This is version 3 of the patches originally posted here:
> 
>   v1: http://www.spinics.net/lists/kvm-arm/msg10219.html
>   v2: http://www.spinics.net/lists/kvm/msg105197.html
> 
> Changes since v2 include:
> 
>   - Rebased onto 3.17-rc* (the vgic code changed a lot!)
>   - Added relevant acks
> 
> The mpic, flic and xics are still not ported over, as I don't want to
> risk breaking those devices (it's not clear at which point they need to
> be registered).

Any further comments on this lot?

Will

  parent reply	other threads:[~2014-09-11 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  9:27 [PATCH v3 0/4] Make kvm_device_ops registration dynamic Will Deacon
2014-09-02  9:27 ` [PATCH v3 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Will Deacon
2014-09-02  9:27 ` [PATCH v3 2/4] KVM: ARM: vgic: register kvm_device_ops dynamically Will Deacon
2014-09-02  9:27 ` [PATCH v3 3/4] KVM: s390: register flic ops dynamically Will Deacon
2014-09-02  9:27 ` [PATCH v3 4/4] KVM: VFIO: register kvm_device_ops dynamically Will Deacon
2014-09-11 17:12 ` Will Deacon [this message]
2014-09-16 10:33 ` [PATCH v3 0/4] Make kvm_device_ops registration dynamic Paolo Bonzini

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=20140911171213.GC6158@arm.com \
    --to=will.deacon@arm.com \
    --cc=Alex.Williamson@redhat.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=agraf@suse.de \
    --cc=christoffer.dall@linaro.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=pbonzini@redhat.com \
    /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