All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: EXPORT_NO_SYMBOLS vs. (null) ?
Date: Sat, 18 Nov 2000 12:45:00 -0500	[thread overview]
Message-ID: <3A16C01C.8421220A@mandrakesoft.com> (raw)
In-Reply-To: <200011181740.SAA14504@cave.bitwizard.nl>

Rogier Wolff wrote:
> 
> Alan Cox wrote:
> > > What is the difference between a module that exports no symbols and
> > > includes EXPORT_NO_SYMBOLS reference, and such a module that lacks
> > > EXPORT_NO_SYMBOLS?
> > >
> > > Alan once upbraided me for assuming they were the same :)
> >
> > EXPORT_NO_SYMBOLS             -       nothing exported
> > MODULE_foo                    -       export specific symbol
> >
> > none of the above, export all globals but without modvers
>                                 ^^^^^^^ and statics!!!!
> 
> I consider that a bug, but...

eh?  Can you give an example of this?  This should definitely -not- be
the case.

	Jeff


-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-18 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18  5:15 EXPORT_NO_SYMBOLS vs. (null) ? Jeff Garzik
2000-11-18  7:40 ` Keith Owens
2000-11-18 17:12 ` Alan Cox
2000-11-18 17:40   ` Rogier Wolff
2000-11-18 17:45     ` Jeff Garzik [this message]
2000-11-18 17:50       ` Rogier Wolff
2000-11-18 18:44         ` Jeff Garzik
2000-11-19  8:12         ` Keith Owens

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=3A16C01C.8421220A@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.