From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: drevil@warpcore.org, linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Tue, 23 Oct 2001 07:37:47 -0500 (CDT) [thread overview]
Message-ID: <200110231237.HAA16435@tomcat.admin.navo.hpc.mil> (raw)
--------- Received message begins Here ---------
>
> On Mon, Oct 22, 2001 at 09:24:11PM +0100, Alan Cox wrote:
> > Only Nvidia can help you
>
> With a problem caused by someone else and not them? Interesting viewpoint. I
> also find it interesting that people think NVidia is the sole company in control
> of whether or not ther drivers are opened considering SGI and other 3rd parties
> own code in the 'driver pie'. This is a simplistic naive view IMHO....
> -
Not really. Driver writers have always had to provide updates if/when other
parts of the kernel evolved. Especially if they inadvertently depended on
a bug in that other part.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2001-10-23 12:37 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 12:37 Jesse Pollard [this message]
[not found] <fa.fm7f5dv.1cn8eg6@ifi.uio.no>
[not found] ` <fa.hbvlhav.v369au@ifi.uio.no>
[not found] ` <023001c15cf4$4fd5ecc0$1a01a8c0@allyourbase>
2001-10-25 4:15 ` 2.4.13-pre6 breaks Nvidia's kernel module Reid Hekman
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 9:52 PVotruba
2001-10-23 1:50 BH
2001-10-22 18:45 jarausch
2001-10-22 18:45 jarausch
2005-01-13 16:19 ` Arjan van de Ven
2005-01-13 16:50 ` Valdis.Kletnieks
2005-01-13 17:25 ` Zan Lynx
2005-01-13 17:38 ` Zwane Mwaikambo
2001-10-22 18:45 jarausch
2001-10-22 18:51 ` Benjamin LaHaise
2001-10-22 18:51 ` Alexander Viro
2001-10-22 19:35 ` Rik van Riel
2001-10-22 19:46 ` Christopher Friesen
2001-10-22 19:53 ` Daniel T. Chen
2001-10-22 20:24 ` Alan Cox
2001-10-22 22:27 ` drevil
2001-10-22 22:43 ` Charles Cazabon
2001-10-22 22:46 ` Doug McNaught
2001-10-22 22:50 ` Alan Cox
2001-10-23 1:31 ` drevil
2001-10-23 1:43 ` Michael H. Warfield
2001-10-23 2:16 ` drevil
2001-10-23 4:44 ` Nicholas Knight
2001-10-23 5:06 ` Cort Dougan
2001-10-23 11:36 ` Rik van Riel
2001-10-23 16:13 ` Alan Cox
2001-10-23 5:08 ` drevil
2001-10-23 5:18 ` J Sloan
2001-10-23 5:59 ` Nicholas Knight
2001-10-23 7:21 ` Helge Hafting
2001-10-23 5:35 ` Matt D. Robinson
2001-10-23 16:16 ` Alan Cox
2001-10-23 9:50 ` David Woodhouse
2001-10-23 23:45 ` Ragnar Hojland Espinosa
2001-10-23 7:57 ` Alan Cox
2001-10-23 14:18 ` drevil
2001-10-23 16:01 ` Geert Uytterhoeven
2001-10-22 23:48 ` Jeff Golds
2001-10-22 23:53 ` Horst von Brand
2001-10-23 9:05 ` Jesper Juhl
2001-10-23 18:07 ` Josh McKinney
2001-10-23 22:51 ` J . A . Magallon
2001-10-24 21:06 ` Reid Hekman
2001-10-25 0:19 ` J . A . Magallon
2001-10-22 18:45 jarausch
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=200110231237.HAA16435@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=drevil@warpcore.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