From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andreas Steinmetz <ast@domdv.de>
Cc: linux-kernel@vger.kernel.org, Rik van Riel <riel@conectiva.com.br>
Subject: Re: [OT] 2.4.19 BUG in page_alloc.c:91
Date: 08 Aug 2002 14:41:19 +0100 [thread overview]
Message-ID: <1028814079.28882.40.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <m17cmFU-003oZpC@zeus.domdv.de>
On Thu, 2002-08-08 at 13:19, Andreas Steinmetz wrote:
> # insmod xircom_tulip_cb
> Using /lib/modules/2.4.19/kernel/drivers/net/pcmcia/xircom_tulip_cb.o
> Warning: loading
> /lib/modules/2.4.19/kernel/drivers/net/pcmcia/xircom_tulip_cb.o will taint the
> kernel: non-GPL license - GPL v2
Sounds like its missing the license tag - ok that would explain it. I'll
take a look at that
> That's no criticism of the nvidia handling (I don't own such a card), it is
> more the new "P=must be proprietary" attitude I don't exactly like.
Its the only way I can filter bugs efficiently enough. The alternative
is I only look at bug reports from Red Hat paying customers, and that
isnt helpful to anyone
next prev parent reply other threads:[~2002-08-08 12:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 2:45 Anthony Russo., a.k.a. Stupendous Man
2002-08-08 2:50 ` Rik van Riel
2002-08-08 2:54 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 7:55 ` Willy Tarreau
2002-08-08 15:42 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 19:43 ` Alan Cox
2002-08-08 18:26 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 20:04 ` Alan Cox
2002-08-08 12:38 ` Alan Cox
2002-08-08 12:19 ` [OT] " Andreas Steinmetz
2002-08-08 13:41 ` Alan Cox [this message]
2002-08-09 9:14 ` Keith Owens
2002-08-08 15:45 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 16:07 ` Willy Tarreau
2002-08-08 16:15 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 15:56 ` 2.4.19 BUG in page_alloc.c:91 -- NOT NVidia driver! Anthony Russo., a.k.a. Stupendous Man
2002-08-14 15:19 ` 2.4.19 BUG in page_alloc.c:91 Ingo Saitz
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=1028814079.28882.40.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®