From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>, Will Deacon <will.deacon@arm.com>
Cc: Alex Williamson <Alex.Williamson@redhat.com>,
Gleb Natapov <gleb@kernel.org>,
kvm@vger.kernel.org
Subject: Re: KVM: remove Kconfig symbol KVM_VFIO?
Date: Tue, 23 Sep 2014 22:29:34 +0200 [thread overview]
Message-ID: <5421D82E.6090103@redhat.com> (raw)
In-Reply-To: <1411499391.24045.13.camel@x220>
Il 23/09/2014 21:09, Paul Bolle ha scritto:
> Will,
>
> Your commit 80ce1639727e ("KVM: VFIO: register kvm_device_ops
> dynamically") is included in linux-next since next-20140918. It removes
> the last usage of CONFIG_KVM_VFIO. After that commit setting KVM_VFIO is
> pointless.
>
> Is the patch to remove the Kconfig symbol KVM_VFIO from the tree queued
> somewhere? If not, should I submit a trivial patch that does that?
No, if you send that yourself it will be appreciated. Thanks!
Paolo
next prev parent reply other threads:[~2014-09-23 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 19:09 KVM: remove Kconfig symbol KVM_VFIO? Paul Bolle
2014-09-23 20:29 ` Paolo Bonzini [this message]
2014-09-24 8:22 ` [PATCH] [next-20140923] KVM: Remove KVM_VFIO Paul Bolle
2014-09-24 9:45 ` 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=5421D82E.6090103@redhat.com \
--to=pbonzini@redhat.com \
--cc=Alex.Williamson@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=will.deacon@arm.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