From: Brian Gerst <bgerst@didntduck.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Move __this_module to xxx.mod.c
Date: Sun, 16 Feb 2003 21:29:48 -0500 [thread overview]
Message-ID: <3E50491C.2030901@didntduck.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302161946220.5217-100000@chaos.physics.uiowa.edu>
Kai Germaschewski wrote:
> On Sun, 16 Feb 2003, Brian Gerst wrote:
>
>
> >This patch moves the module structure to the generated .mod.c file,
> >instead of compiling it into each object and relying on the linker to
> >include it only once.
>
>
> Yeah, it's something I though about doing, but I was not sure. I think
> it's up to Rusty to comment ;)
>
> It will need an associated change to module_init_tools.
>
> Another comment:
>
> diff -urN linux-2.5.61-bk1/scripts/modpost.c linux/scripts/modpost.c
> --- linux-2.5.61-bk1/scripts/modpost.c 2003-02-16 10:06:35.000000000 -0500
> +++ linux/scripts/modpost.c 2003-02-16 14:10:19.000000000 -0500
> @@ -287,6 +287,10 @@
> /* undefined symbol */
> if (ELF_ST_BIND(sym->st_info) != STB_GLOBAL)
> break;
> +
> + /* ignore __this_module */
> + if (!strcmp(symname, "__this_module"))
> + break;
>
> s = alloc_symbol(symname);
> /* add to list */
>
> Is that necessary? __this_module shouldn't be unresolved, so this case
> should never be hit AFAICS.
After the definition is removed from module.h, it is unresolved before
it is linked to xxx.mod.c.
--
Brian Gerst
next prev parent reply other threads:[~2003-02-17 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 21:23 [PATCH] Move __this_module to xxx.mod.c Brian Gerst
2003-02-17 1:57 ` Kai Germaschewski
2003-02-17 2:29 ` Brian Gerst [this message]
2003-02-17 3:42 ` Rusty Russell
2003-02-17 4:26 ` Kai Germaschewski
2003-02-17 4:53 ` Rusty Russell
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=3E50491C.2030901@didntduck.org \
--to=bgerst@didntduck.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/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