From: Arjan van de Ven <arjanv@redhat.com>
To: Martin Donnelly <md@uklinux.net>, linux-kernel@vger.kernel.org
Subject: Re: Non-GPL modules
Date: Thu, 18 Oct 2001 15:50:49 +0100 [thread overview]
Message-ID: <3BCEEC49.90A402A0@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1011018091343.32746A-100000@chaos.analogic.com> <20011018090412.I22296@0xd6.org> <1003415874.4004.45.camel@inchgower>
> Perhaps a less blunt tool could be used to encourage people to release
> GPL compatibly licensed code for their previously binary modules? I
> think you risk manufacturers withdrawing the support they have given by
> saying if they don't release their code we won't support anything to do
> with it.
This has been the case for a long time already (so long that I can't
remember
if/when it started:), so how did this change recently ? It didn't...
And vendors who supply binary only modules know already that they get to
do
all the support as rules of the game. That didn't change either.
It's just that it's now easier for the people who get to handle
bugreports
to ask "which modules do you use" as first question if the tainted flag
is set,
instead of spending hours investigating a weird oops.
Greetings,
Arjan van de Ven
(and yes, I do get a fair share of bugreports and really like to know
which
reports I should be suspicious of and ask for module lists etc)
next prev parent reply other threads:[~2001-10-18 14:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 13:15 Non-GPL modules Richard B. Johnson
2001-10-18 13:38 ` Adrian Bunk
2001-10-18 13:58 ` Richard B. Johnson
2001-10-18 14:11 ` Ben Collins
2001-10-18 14:46 ` Richard B. Johnson
2001-10-18 14:53 ` Peter T. Breuer
2001-10-18 15:21 ` Richard B. Johnson
2001-10-18 15:40 ` Peter T. Breuer
2001-10-18 16:40 ` Jan Niehusmann
2001-10-18 17:02 ` Martin Dalecki
2001-10-18 17:16 ` Ben Collins
2001-10-18 17:15 ` Martin Dalecki
2001-10-18 18:06 ` Mark Hahn
2001-10-18 14:06 ` Ben Collins
2001-10-18 14:04 ` M. R. Brown
2001-10-18 14:31 ` Jesper Juhl
2001-10-18 14:37 ` Martin Donnelly
2001-10-18 14:50 ` Arjan van de Ven [this message]
2001-10-18 15:48 ` M. R. Brown
2001-10-20 22:08 ` Alan Cox
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=3BCEEC49.90A402A0@redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=md@uklinux.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.