All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Jaegermann <michal@harddata.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A "new driver model" and EXPORT_SYMBOL_GPL question
Date: Mon, 4 Jul 2005 10:00:22 -0600	[thread overview]
Message-ID: <20050704100022.A23509@mail.harddata.com> (raw)
In-Reply-To: <20050704054441.GA19936@kroah.com>; from greg@kroah.com on Sun, Jul 03, 2005 at 10:44:41PM -0700

On Sun, Jul 03, 2005 at 10:44:41PM -0700, Greg KH wrote:
> On Sun, Jul 03, 2005 at 05:12:02PM -0600, Michal Jaegermann wrote:
> 
> > 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.
> 
> Please see the archives for the answers to these questions.

I actually tried that before posting.  Maybe I attempted to look for
wrong things but, beyond conversion examples, I found some postings
with a general theme "there is no point to make life easy for
binary-only modules" and not much else.  I am afraid that this
leaves me not much wiser.

Also, at least when dealing with 2.6.13-r1, neither
Documentation/feature-removal-schedule.txt, nor files in
Documentation/driver-model/ directory, mention anything about a
switch to EXPORT_SYMBOL_GPL for relevant symbols.  The only thing I
can find about the later in "feature-removal..." is a note about RCU
API.

   Michal

  reply	other threads:[~2005-07-04 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 23:12 A "new driver model" and EXPORT_SYMBOL_GPL question Michal Jaegermann
2005-07-04  5:44 ` Greg KH
2005-07-04 16:00   ` Michal Jaegermann [this message]
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=20050704100022.A23509@mail.harddata.com \
    --to=michal@harddata.com \
    --cc=greg@kroah.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.