From: Randy Dunlap <randy.dunlap@oracle.com>
To: kvm-devel@lists.sourceforge.net, lkml <linux-kernel@vger.kernel.org>
Cc: avi@qumranet.com, akpm <akpm@osdl.org>
Subject: [PATCH] kvm needs menu structure
Date: Mon, 11 Dec 2006 14:44:18 -0800 [thread overview]
Message-ID: <20061211144418.f10a7f5b.randy.dunlap@oracle.com> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
KVM config items need to be inside a menu structure instead of
dangling off of Device Drivers.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/kvm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.19-git18.orig/drivers/kvm/Kconfig
+++ linux-2.6.19-git18/drivers/kvm/Kconfig
@@ -1,7 +1,7 @@
#
# KVM configuration
#
-config KVM
+menuconfig KVM
tristate "Kernel-based Virtual Machine (KVM) support"
depends on X86 && EXPERIMENTAL
---help---
---
next reply other threads:[~2006-12-11 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 22:44 Randy Dunlap [this message]
2006-12-12 7:46 ` [PATCH] kvm needs menu structure Avi Kivity
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=20061211144418.f10a7f5b.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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