From: Dmitry Torokhov <dtor@vmware.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] VMware balloon: force compiling as a module
Date: Mon, 28 Jun 2010 16:00:35 -0700 [thread overview]
Message-ID: <20100628230035.GA18971@dtor-ws.eng.vmware.com> (raw)
VMware Tools installer requires the upstream driver to be compiled
as a module in order to detect its presence and avoid installing
our own version on top of it. To avoid surprises with 2 versions
of the driver being installed and fighting with each other, let's
force the driver to be compiled as a module unless user selects
CONFIG_EMBEDDED.
Signed-off-by: Dmitry Torokhov <dtor@vmware.com>
---
Andrew,
Please consider forwarding this to Linus in your next batch.
Thanks,
Dmitry
drivers/misc/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 26386a9..bb5b6ea 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -339,7 +339,7 @@ config TI_DAC7512
config VMWARE_BALLOON
tristate "VMware Balloon Driver"
- depends on X86
+ depends on X86 && (EMBEDDED || m)
help
This is VMware physical memory management driver which acts
like a "balloon" that can be inflated to reclaim physical pages
--
1.7.0
next reply other threads:[~2010-06-28 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 23:00 Dmitry Torokhov [this message]
2010-06-29 8:27 ` [PATCH] VMware balloon: force compiling as a module Alexander Clouter
2010-06-29 16:28 ` Bruno Prémont
2010-06-29 16:40 ` Dmitry Torokhov
2010-07-01 22:18 ` Andrew Morton
2010-07-01 22:31 ` Dmitry Torokhov
2010-07-01 22:43 ` Andrew Morton
2010-07-01 22:59 ` Dmitry Torokhov
2010-07-02 8:09 ` Alexander Clouter
2010-06-29 16:39 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2010-06-30 18:42 Chetan Loke
2010-06-30 19:27 ` Dmitry Torokhov
2010-06-30 21:26 ` Chetan Loke
2010-06-30 21:39 ` Dmitry Torokhov
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=20100628230035.GA18971@dtor-ws.eng.vmware.com \
--to=dtor@vmware.com \
--cc=akpm@linux-foundation.org \
--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