All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@sourcefrog.net>
To: linux-ia64@vger.kernel.org
Subject: Re: bug? fpswa_interface needs to be exported
Date: Fri, 16 Apr 2004 04:04:04 +0000	[thread overview]
Message-ID: <20040416040403.GA12253@hp.com> (raw)
In-Reply-To: <20040413073643.GB11350@hp.com>

On 13 Apr 2004, David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Tue, 13 Apr 2004 17:36:43 +1000, Martin Pool <mbp@sourcefrog.net> said:
> 
>   Martin> Hi, In 2.6.4/5, efivars can be built as a module, but it
>   Martin> depends on 'fpswa_interface' which is not exported by
>   Martin> fpswa.c.  I think you need a EXPORT_SYMBOL for that
>   Martin> variable.
> 
>   Martin> Debian's 2.6.4-mckinley-smp kernel has this built as a
>   Martin> module but it cannot be loaded:
> 
>   Martin>   efivars: Unknown symbol fpswa_interface
> 
> Want to send a (tested) patch?

This will fix it:

--- linus--release--2.6.5--version-0/arch/ia64/kernel/traps.c	2004-04-15 12:42:32.000000000 +1000
+++ ./arch/ia64/kernel/traps.c	2004-04-15 16:18:55.000000000 +1000
@@ -13,6 +13,7 @@
 #include <linux/sched.h>
 #include <linux/tty.h>
 #include <linux/vt_kern.h>		/* For unblank_screen() */
+#include <linux/module.h>       /* for EXPORT_SYMBOL */
 
 #include <asm/fpswa.h>
 #include <asm/hardirq.h>
@@ -47,6 +48,7 @@
 extern spinlock_t timerlist_lock;
 
 fpswa_interface_t *fpswa_interface;
+EXPORT_SYMBOL(fpswa_interface);
 
 void __init
 trap_init (void)


There was also a bug in modpost that suppressed the warning that
should have come out at compile time.  Rusty has fixed it in Linus's
tree.

-- 
Martin 

      parent reply	other threads:[~2004-04-16  4:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  7:36 bug? fpswa_interface needs to be exported Martin Pool
2004-04-13 22:49 ` David Mosberger
2004-04-16  4:04 ` Martin Pool [this message]

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=20040416040403.GA12253@hp.com \
    --to=mbp@sourcefrog.net \
    --cc=linux-ia64@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.