All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Rusty Russell <rusty@rustcorp.com.au>,
	David Howells <dhowells@redhat.com>
Cc: vlobanov <vlobanov@speakeasy.net>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	lethal@linux-sh.org, kkojima@rr.iij4u.or.jp
Subject: Re: EXPORT_SYMBOL_NOVERS question
Date: Mon, 29 Nov 2004 00:00:43 +0100	[thread overview]
Message-ID: <20041128230043.GH4390@stusta.de> (raw)
In-Reply-To: <1101681740.25347.21.camel@localhost.localdomain>

On Mon, Nov 29, 2004 at 09:42:20AM +1100, Rusty Russell wrote:
> On Wed, 2004-11-03 at 00:10 -0800, vlobanov wrote:
> > Hi,
> > 
> > I was looking over the /include/linux/module.h file, and the
> > EXPORT_SYMBOL_NOVERS macro caught my eye. To quote the source:
> > 
> >   /* We don't mangle the actual symbol anymore, so no need for
> >    * special casing EXPORT_SYMBOL_NOVERS.  FIXME: Deprecated */
> >   #define EXPORT_SYMBOL_NOVERS(sym) EXPORT_SYMBOL(sym)
> > 
> > A quick grep through the tree brought up no usage cases for this macro.
> > Is there any reason to keep it around, instead of cutting it out, as the
> > FIXME comment seems to suggest?
> 
> Yep, it's time.
> 
> Rusty.
> 
> Name: Remove EXPORT_SYMBOL_NOVERS
> Status: Trivial
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> 
> Vadim Lobanov points out that EXPORT_SYMBOL_NOVERS is no longer used;
> in fact, SH still uses it, but once we fix that, the kernel is clean.
> Remove it.
>...

Thaat's true for Linus' tree, but not for -mm.

@David:
arch/frv/kernel/frv_ksyms.c has to be changed.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-11-28 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03  8:10 EXPORT_SYMBOL_NOVERS question vlobanov
2004-11-28 22:42 ` Rusty Russell
2004-11-28 23:00   ` Adrian Bunk [this message]
2004-11-29 13:38     ` David Howells
2004-12-03  2:59   ` Paul Mundt

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=20041128230043.GH4390@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vlobanov@speakeasy.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 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.