The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Greg KH <greg@kroah.com>
Cc: Michal Jaegermann <michal@harddata.com>, linux-kernel@vger.kernel.org
Subject: Re: A "new driver model" and EXPORT_SYMBOL_GPL question
Date: Tue, 05 Jul 2005 15:50:43 -0600	[thread overview]
Message-ID: <1120600243.27600.75.camel@localhost> (raw)
In-Reply-To: <20050704054441.GA19936@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

On Sun, 2005-07-03 at 22:44 -0700, Greg KH wrote:
> On Sun, Jul 03, 2005 at 05:12:02PM -0600, Michal Jaegermann wrote:
[snip]
> Then take it up with them.  Users of those symbols have had many months
> advance notice that this was going to happen.
> 
> > 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.

The archives say:
Greg KH wrote:
> I have been recently advised that I should not change these symbols,
> and so I will not.
> 
> Sorry for the noise and wasted bandwidth, will not happen again.
> 
> greg k-h

Sourced from here:
http://hulllug.principalhosting.net/archive/index.php/t-52440.html

That was the way it was as of 2.6.10-mm1 and it stayed that way through
2.6.12.  When did that decision change?  If it was there in the
archives, I missed it in the search.

If this was a Greg-only decision, perhaps a patch reversing the change
addressed to Linus would get a solid yes/no decision from the top.

From what I gather in the archives, the last time this happened it was
just a leak from Greg's tree and not an official policy change.  It
isn't in the feature removal schedule, even though other _GPL changes
are listed there.
-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-07-05 22:03 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
2005-07-05 21:50   ` Zan Lynx [this message]
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=1120600243.27600.75.camel@localhost \
    --to=zlynx@acm.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@harddata.com \
    /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