All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org
Subject: A "new driver model" and EXPORT_SYMBOL_GPL question
Date: Sun, 3 Jul 2005 17:12:02 -0600	[thread overview]
Message-ID: <20050703171202.A7210@mail.harddata.com> (raw)

It dawned on me only now that a "new driver model" introduced
in patches from GKH export symbols like that:

EXPORT_SYMBOL_GPL(class_create);
EXPORT_SYMBOL_GPL(class_destroy);

and so on.  The problem is that corresponding old symbols, which
are still present in 2.6.12, were exported

EXPORT_SYMBOL(class_simple_create);
EXPORT_SYMBOL(class_simple_destroy);
....

This creates a problem.  There exist out-of-tree drivers which are
using those symbols and, even if sources are available, are not
licensed GPL for whatever reasons.  No, I am not the author of any
of those so I cannot do very much about re-licensing.  As an effect
a conversion to a "new driver model", even if simple, does not work.
In particular I bumped into that with Myrinet card drivers.

Was a decision to use EXPORT_SYMBOL_GPL deliberate and if yes then
what considerations dictated it, other then the patch author wrote
it that way, and what drivers in question are supposed to use when
this change will show up in the mainline?  It looks that 2.6.13
will do this.

  Thanks,
  Michal

             reply	other threads:[~2005-07-03 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 23:12 Michal Jaegermann [this message]
2005-07-04  5:44 ` A "new driver model" and EXPORT_SYMBOL_GPL question Greg KH
2005-07-04 16:00   ` Michal Jaegermann
2005-07-05 21:50   ` Zan Lynx
2005-07-05 21:57     ` Greg KH
2005-07-06  4:37       ` Michal Jaegermann
2005-07-06  5:26         ` Greg KH
2005-07-05 11:09 ` Richard B. Johnson
2005-07-05 12:06   ` Lars Marowsky-Bree

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=20050703171202.A7210@mail.harddata.com \
    --to=michal@harddata.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.