From: Keith Owens <kaos@ocs.com.au>
To: "David S. Miller" <davem@redhat.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.6-pre3 unresolved symbol do_softirq
Date: Thu, 14 Jun 2001 00:11:57 +1000 [thread overview]
Message-ID: <10347.992441517@ocs4.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 13 Jun 2001 07:06:42 MST." <15143.29554.888847.108615@pizda.ninka.net>
On Wed, 13 Jun 2001 07:06:42 -0700 (PDT),
"David S. Miller" <davem@redhat.com> wrote:
>
>Keith Owens writes:
> > OTOH if any *.S code is compiled into a module then all symbols it
> > refers to must be EXPORT_SYMBOL_NOVERS().
>
>Why not just add --include modversions.h to the gcc command line to
>build it, why wouldn't this work?
Assembler code is not hooked into the generic module symbol version
handling. Every .S rule is unique and I'm not going to change every
one.
next prev parent reply other threads:[~2001-06-13 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 12:07 [patch] 2.4.6-pre3 unresolved symbol do_softirq Keith Owens
2001-06-13 12:13 ` David S. Miller
2001-06-13 13:48 ` Jeff Garzik
2001-06-13 13:58 ` David S. Miller
2001-06-13 14:03 ` Keith Owens
2001-06-13 14:06 ` David S. Miller
2001-06-13 14:11 ` Keith Owens [this message]
2001-06-13 14:15 ` David S. Miller
2001-06-13 14:37 ` Keith Owens
2001-06-13 13:58 ` Keith Owens
2001-06-13 14:01 ` David S. Miller
2001-06-13 14:09 ` Keith Owens
2001-06-13 14:21 ` David S. Miller
2001-06-13 14:37 ` Andrew Morton
2001-06-13 14:44 ` Andreas Schwab
2001-06-13 14:53 ` Russell King
2001-06-13 14:55 ` David S. Miller
2001-06-13 16:39 ` Keith Owens
2001-06-13 14:52 ` Russell King
2001-06-13 14:31 ` Bill Pringlemeir
2001-06-13 14:39 ` 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=10347.992441517@ocs4.ocs-net \
--to=kaos@ocs.com.au \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox