From: Peter Samuelson <peter@cadcamlab.org>
To: Christoph Hellwig <hch@infradead.org>,
Jaroslav Kysela <perex@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
"kbuild-devel@lists.sourceforge.net"
<kbuild-devel@lists.sourceforge.net>
Subject: Re: 2.5 kbuild: use of '-z muldefs' for LD?
Date: Mon, 9 Jun 2003 09:29:56 -0500 [thread overview]
Message-ID: <20030609142956.GH573@cadcamlab.org> (raw)
In-Reply-To: <20030609151945.A10352@infradead.org>
[Christoph Hellwig]
> Well, if you want separate copies of it you have to make sure the
> symbols won't clash, e.g. calling all functions in it
>
> MYPREFIX_foo
>
> and then do #define MYPREFIX KBUILD_MODNAME
...or just move everything into a header file as static functions.
Inline, even, if the code is really trivial enough that you don't want
to make a separate module of it.
Peter
next prev parent reply other threads:[~2003-06-09 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 11:56 2.5 kbuild: use of '-z muldefs' for LD? Jaroslav Kysela
2003-06-09 11:56 ` Jaroslav Kysela
2003-06-09 12:04 ` Christoph Hellwig
2003-06-09 14:01 ` Jaroslav Kysela
2003-06-09 14:01 ` Jaroslav Kysela
2003-06-09 14:19 ` Christoph Hellwig
2003-06-09 14:29 ` Peter Samuelson [this message]
2003-06-09 19:45 ` Sam Ravnborg
2003-06-09 20:15 ` Kai Germaschewski
2003-06-09 12:08 ` Christoph Hellwig
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=20030609142956.GH573@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=hch@infradead.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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.