public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-mm1, class_simple_* and GPL addition
Date: Thu, 28 Oct 2004 07:30:18 +1000	[thread overview]
Message-ID: <21d7e99704102714303bb9424@mail.gmail.com> (raw)
In-Reply-To: <20041027135052.GE32199@gamma.logic.tuwien.ac.at>

> 
> I don't want to start a flame war and long discussion, just want to ask
> wether this change (to _GPL) was intended, and if yes, if there is a way
> to fix nvidia kernel modules (or others) using this device management
> interface.

From:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0110.2/0369.html

EXPORT_SYMBOL_GPL() may only be used for new exported symbols, Linus
has spoken. I believe the phrase involved killer penguins with
chainsaws for anybody who changed existing exported interfaces. 

not sure if this applies or not to the class_simple interfaces,
probably not but just FYI....
there is no reason NV or who ever can't implement their own non-simple
class ....

Dave.

      parent reply	other threads:[~2004-10-27 21:36 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
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 [this message]

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=21d7e99704102714303bb9424@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=akpm@osdl.org \
    --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