public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>, Norbert Preining <preining@logic.at>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-mm1, class_simple_* and GPL addition
Date: Wed, 27 Oct 2004 20:12:44 -0500	[thread overview]
Message-ID: <200410272012.44361.dtor_core@ameritech.net> (raw)
In-Reply-To: <20041027153715.GB13991@kroah.com>

On Wednesday 27 October 2004 10:37 am, Greg KH wrote:
> On Wed, Oct 27, 2004 at 03:50:52PM +0200, Norbert Preining wrote:
> > Hi Andrew!
> > 
> > The change from 
> > 	EXPORT_SYMBOL
> > to
> > 	EXPORT_SYMBOL_GPL
> > for class_simple_* makes the nvidia module useless as it uses several:
> > nvidia: Unknown symbol class_simple_device_add
> > nvidia: Unknown symbol class_simple_destroy
> > nvidia: Unknown symbol class_simple_device_remove
> > nvidia: Unknown symbol class_simple_create
> 
> I think these changes are only in the Gentoo modified version of the
> driver, right?  I don't think that nvidia wrote the driver that way.
> 
> > I don't want to start a flame war and long discussion, just want to ask
> > wether this change (to _GPL) was intended,
> 
> Yes it was.
> 

I wonder what are the technical merits of this change. I certainly agree
with Pat's assertion that the rest of driver model functions should be used
by in-kernel subsystems (such as PCI, USB, serio etc) only and not exposed
to the outside world. This will allow freely fix/enhance the core without
fear of silently breaking external modules.

But class_simple is itself a limited and contained interface with well-
defined semantic. Which I believe was advertised aat one time as a wrapper
for the objects wanting to plug into hotplug/udev model but either living
outside of established subsystems or within subsystem not yet ready to
implement proper refcounting needed for full-blown sysfs integration.

I think it is a mistake to convert class_simple into GPL-only export.  

--  
Dmitry

  parent reply	other threads:[~2004-10-28  1:13 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 [this message]
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

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=200410272012.44361.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --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