public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Coatti <cova@ferrara.linux.it>
To: Greg KH <greg@kroah.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org,
	Norbert Preining <preining@logic.at>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-mm1, class_simple_* and GPL addition
Date: Sat, 30 Oct 2004 16:44:33 +0200	[thread overview]
Message-ID: <200410301644.33997.cova@ferrara.linux.it> (raw)
In-Reply-To: <20041029205505.GB30638@kroah.com>

Alle 22:55, venerdì 29 ottobre 2004, Greg KH ha scritto:


>
> So we can change things, little things like this can help everyone out,
> even if I'm going to get a ton of nvidia user hate mail directed to me
> after the next kernel comes out...
>
> Remember, binary kernel modules are a leach on our community.

I'm one of the users biten by this change, and I can undestand your reason; 
anyway from my standpoint the situation is that a change that has no 
technical motivation (at least to my knowledge) is going to remove an 
interface that until now was available, and prevents me to use my card with 
new kernels; this is too similar to some closed souce companies behaviour. No 
big deal, I can live with that, but if this is the right way to handle that 
interface, why this is enforced only now and not from the very first time? 
Granted that you have all the rights to do that, may I ask if this is not in 
contrast with is stated in this post? 
http://www.uwsg.iu.edu/hypermail/linux/kernel/0110.2/0369.html

I understand all your motivation,and I agree with most of them, but I'm asking 
if this is the right way to handle this GPL issue...


-- 
Fabio Coatti       http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

  parent reply	other threads:[~2004-10-30 15:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 13:50 2.6.10-mm1, class_simple_* and GPL addition Norbert Preining
2004-10-27 15:37 ` Greg KH
     [not found]   ` <1098890583.6990.20.camel@laptop.fenrus.org>
2004-10-27 17:08     ` Norbert Preining
2004-10-27 19:17   ` Petr Vandrovec
2004-10-27 19:55     ` Arjan van de Ven
2004-10-27 21:21       ` Petr Vandrovec
2004-10-28  1:12   ` Dmitry Torokhov
2004-10-29 20:55     ` Greg KH
2004-10-29 22:06       ` Petr Vandrovec
2004-10-30 11:44       ` Dave Airlie
2004-10-30 14:44       ` Fabio Coatti [this message]
2004-11-01 22:31         ` Greg KH
2004-11-09 23:12           ` Luke Maurer
2004-11-10 10:32             ` Fabio Coatti
2004-12-16 17:50           ` Chris Wright
2004-12-16 18:57             ` Greg KH
2004-10-27 21:30 ` Dave Airlie

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=200410301644.33997.cova@ferrara.linux.it \
    --to=cova@ferrara.linux.it \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    /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