From: Andrew Jones <drjones@redhat.com>
To: konrad@darnok.org
Cc: jeremy@goop.org, xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org,
konrad.wilk@oracle.com, stefano.stabellini@eu.citrix.com
Subject: [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin
Date: Wed, 11 Jan 2012 17:36:38 +0100 [thread overview]
Message-ID: <1326299801-7966-1-git-send-email-drjones@redhat.com> (raw)
In-Reply-To: <20120111161911.GB18203@andromeda.dapyr.net>
When XEN_XENBUS_FRONTEND gets selected as a module it can lead to
unbootable configs. If we need it, then we should just build it in.
Signed-off-by: Andrew Jones <drjones@redhat.com>
---
drivers/xen/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index 8795480..1d24061 100644
--- a/drivers/xen/Kconfig
+++ b/drivers/xen/Kconfig
@@ -118,7 +118,7 @@ config XEN_SYS_HYPERVISOR
but will have no xen contents.
config XEN_XENBUS_FRONTEND
- tristate
+ bool
config XEN_GNTDEV
tristate "userspace grant access device driver"
--
1.7.7.5
next prev parent reply other threads:[~2012-01-11 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F0B8D06.8050501@goop.org>
2012-01-11 15:37 ` [Xen-devel] [PATCH] xen: remove CONFIG_XEN_DOM0 compile option Andrew Jones
2012-01-11 16:19 ` Konrad Rzeszutek Wilk
2012-01-11 16:36 ` Andrew Jones [this message]
2012-01-11 16:36 ` [PATCH 2/4 v2] xen kconfig: relax INPUT_XEN_KBDDEV_FRONTEND deps Andrew Jones
2012-01-11 17:30 ` Konrad Rzeszutek Wilk
2012-01-12 10:59 ` Andrew Jones
2012-01-11 16:36 ` [PATCH 3/4 v2] xen kconfig: add dom0 support help text Andrew Jones
2012-01-11 16:36 ` [PATCH 4/4] xen kconfig: describe xen tmem in the config menu Andrew Jones
2012-01-11 17:35 ` Konrad Rzeszutek Wilk
2012-01-12 10:54 ` Andrew Jones
2012-01-11 17:28 ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Konrad Rzeszutek Wilk
2012-01-11 17:27 ` [Xen-devel] [PATCH] xen: remove CONFIG_XEN_DOM0 compile option Konrad Rzeszutek Wilk
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=1326299801-7966-1-git-send-email-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).