From: Sam Ravnborg <sam@ravnborg.org>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, Marcus Hartig <m.f.h@web.de>
Subject: Re: 2.6.5-mm4
Date: Mon, 12 Apr 2004 21:52:08 +0200 [thread overview]
Message-ID: <20040412195208.GA12665@mars.ravnborg.org> (raw)
In-Reply-To: <200404122135.57622@WOLK>
On Mon, Apr 12, 2004 at 09:35:57PM +0200, Marc-Christian Petersen wrote:
> On Monday 12 April 2004 21:19, Marcus Hartig wrote:
>
> Hi Marcus,
>
> > patch: "kbuild-external-module-support" ?
>
> actually, this one: "move-__this_module-to-modpost.patch" started breaking
> nvidia, but strangely not for all people. For me it worked fine (prior to
> 2.6.5-mm4), but other people got "invalid module format" after compiling
> nvidia driver and tried to load it. P.S.: kbuild-external-module-support
> breaks VMware too :p
Could I please get more info. I do not plan to install wmware right now,
so at least some minimal information allowing me to realise why it no
longer works.
Please with pointers to the used WMWare version so I can check their
Makefile etc.
Sam
next prev parent reply other threads:[~2004-04-12 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 19:19 2.6.5-mm4 Marcus Hartig
2004-04-12 19:35 ` 2.6.5-mm4 Marc-Christian Petersen
2004-04-12 19:52 ` Sam Ravnborg [this message]
2004-04-12 19:56 ` 2.6.5-mm4 Sam Ravnborg
2004-04-12 20:15 ` 2.6.5-mm4 Andrew Vasquez
2004-04-13 4:54 ` 2.6.5-mm4 Sam Ravnborg
2004-04-12 20:48 ` 2.6.5-mm4 Marcus Hartig
2004-04-13 2:47 ` 2.6.5-mm4 Michael Baehr
2004-04-13 4:58 ` 2.6.5-mm4 Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2004-04-13 15:22 2.6.5-mm4 Andrew Vasquez
2004-04-11 3:05 2.6.5-mm4 Andrew Morton
2004-04-12 6:46 ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12 7:42 ` 2.6.5-mm4 Andrew Morton
2004-04-12 8:22 ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12 8:28 ` 2.6.5-mm4 Andrew Morton
2004-04-12 9:10 ` 2.6.5-mm4 Paul P Komkoff Jr
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=20040412195208.GA12665@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=m.f.h@web.de \
/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