From: Christoph Hellwig <hch@infradead.org>
To: Jaroslav Kysela <perex@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
ALSA development <alsa-devel@alsa-project.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 15:19:45 +0100 [thread overview]
Message-ID: <20030609151945.A10352@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0306091550000.1323-100000@pnote.perex-int.cz>; from perex@suse.cz on Mon, Jun 09, 2003 at 04:01:41PM +0200
On Mon, Jun 09, 2003 at 04:01:41PM +0200, Jaroslav Kysela wrote:
> But this solution will create a new kernel module. The shared code is
> really small and having small codes in separated modules is waste of
> memory in my eyes.
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 something like that
next prev parent reply other threads:[~2003-06-09 14:06 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 [this message]
2003-06-09 14:29 ` Peter Samuelson
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=20030609151945.A10352@infradead.org \
--to=hch@infradead.org \
--cc=alsa-devel@alsa-project.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.