mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Yuri Vilmanis <vilmanis@internode.on.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXPORT_SYMBOL_GPL for __symbol_get replacing EXPORT_SYMBOL for deprecated inter_module_get
Date: Wed, 13 Apr 2005 11:56:00 +0200	[thread overview]
Message-ID: <1113386160.6275.44.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200504131855.00806.vilmanis@internode.on.net>

On Wed, 2005-04-13 at 18:55 +0930, Yuri Vilmanis wrote:
> I believe that, in general, new functions which replace deprecated functions 
> which were exported as EXPORT_SYMBOL, should also be exported as 
> EXPORT_SYMBOL, not as EXPORT_SYMBOL_GPL. The reason I say this is because 
> deprecation of old functions breaks old modules and drivers that use them, 
> and changing the level of GPL strictness of the function prevents these old 
> modules being updated and used with newer kernels.
> 
> The case in point for me is ATI's binary openGL accelerated drivers (fglrx) - 
> these used inter_module_get() to communicate with the agp gart module, 

except that the AGP gart module no longer uses inter_module_*


> for 
> obvious reasons - this AGP communication is essential to the functionality of 
> the driver.

this is thus non-obvious..




> The case of inter_module_get deprecation and replacement with symbol_get 

inter_module_get is absolutely not replaced by symbol_get. They are
entirely different usages and only have a few letters in common in the
name.




  reply	other threads:[~2005-04-13  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13  9:25 Yuri Vilmanis
2005-04-13  9:56 ` Arjan van de Ven [this message]
2005-04-13 13:34 ` Dave Airlie
2005-04-13 14:54 ` Dave Jones
2005-04-13 15:57   ` Richard B. Johnson
2005-04-13 16:01     ` Sean

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=1113386160.6275.44.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vilmanis@internode.on.net \
    /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

all inboxes | Powered by JetHome®