From: Alexander Clouter <alex@digriz.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VMware balloon: force compiling as a module
Date: Tue, 29 Jun 2010 09:27:43 +0100 [thread overview]
Message-ID: <vcnof7-b9p.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: 20100628230035.GA18971@dtor-ws.eng.vmware.com
Dmitry Torokhov <dtor@vmware.com> wrote:
>
> 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.
>
*barf*
This surely is a problem in the installer and not the kernel? Can you
not nosey around in /sys/class/misc or where-ever your driver appears?
If it does not, then I would probably suggest a patch to your balloon
driver that dumps some details in there, including module version
information.
Eugh.
--
Alexander Clouter
.sigmonster says: Who goeth a-borrowing goeth a-sorrowing.
-- Thomas Tusser
next prev parent reply other threads:[~2010-06-29 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 23:00 [PATCH] VMware balloon: force compiling as a module Dmitry Torokhov
2010-06-29 8:27 ` Alexander Clouter [this message]
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=vcnof7-b9p.ln1@chipmunk.wormnet.eu \
--to=alex@digriz.org.uk \
--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