linux-kernel - Re: [PATCH] [next-20140923] KVM: Remove KVM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <542292A7.6000600@redhat.com>
Date:	Wed, 24 Sep 2014 11:45:11 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Paul Bolle <pebolle@...cali.nl>, Gleb Natapov <gleb@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
CC:	Will Deacon <will.deacon@....com>,
	Alex Williamson <Alex.Williamson@...hat.com>,
	kvm@...r.kernel.org, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [next-20140923] KVM: Remove KVM_VFIO

Il 24/09/2014 10:22, Paul Bolle ha scritto:
> There are no checks for CONFIG_KVM_VFIO and nothing depends on KVM_VFIO.
> Setting KVM_VFIO has no effect. Remove that Kconfig symbol.
> 
> Signed-off-by: Paul Bolle <pebolle@...cali.nl>
> ---
> I choose not to mention commit 80ce1639727e ("KVM: VFIO: register
> kvm_device_ops dynamically") as references to linux-next commits might
> go stale and only confuse future readers.

In the case of KVM, linux-commit hashes are substantially stable.  I'll
add back the reference.

Thanks for the patch, I'll apply it.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/