From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Beulich <JBeulich@suse.com>, gleb@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: KVM: don't pointlessly leave KVM_COMPAT=y in non-KVM configs
Date: Mon, 19 Oct 2015 12:40:27 +0200 [thread overview]
Message-ID: <5624C89B.7030300@redhat.com> (raw)
In-Reply-To: <5624E3FE02000078000AC49D@prv-mh.provo.novell.com>
On 19/10/2015 12:37, Jan Beulich wrote:
> The symbol was missing a KVM dependency.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> virt/kvm/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- 4.3-rc6/virt/kvm/Kconfig
> +++ 4.3-rc6-KVM_COMPAT-dependency/virt/kvm/Kconfig
> @@ -46,4 +46,4 @@ config KVM_GENERIC_DIRTYLOG_READ_PROTECT
>
> config KVM_COMPAT
> def_bool y
> - depends on COMPAT && !S390
> + depends on KVM && COMPAT && !S390
>
>
>
Thanks, rebased and pushed to kvm/queue.
Paolo
prev parent reply other threads:[~2015-10-19 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 10:37 KVM: don't pointlessly leave KVM_COMPAT=y in non-KVM configs Jan Beulich
2015-10-19 10:40 ` Paolo Bonzini [this message]
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=5624C89B.7030300@redhat.com \
--to=pbonzini@redhat.com \
--cc=JBeulich@suse.com \
--cc=gleb@kernel.org \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).