From: Alex Williamson <alex.williamson@hp.com>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: linux-scsi@vger.kernel.org
Subject: RE: mptscsih.c: discarded in section `.exit.text' from drivers/bu ilt-in.o
Date: Thu, 05 Feb 2004 13:20:02 -0700 [thread overview]
Message-ID: <1076012402.3744.97.camel@patsy.fc.hp.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E5703D1A5D4@exa-atlanta.se.lsil.com>
Eric,
2.6, the very latest in Linus' linux-2.5 bk tree. Thanks,
Alex
On Thu, 2004-02-05 at 13:15, Moore, Eric Dean wrote:
> Are you using 2.6 or 2.4 kernel? I have recently
> posted different patches against both kernel trees.
> I need to know with driver version your on.
>
> Eric
>
> On Thursday, February 05, 2004 12:53 PM, Alex Williamson wrote:
> >
> > The MPT Fusion driver seems to have developed a linker problem on
> > ia64. The latest linux-2.5 bk tree gives me the following:
> >
> > LD .tmp_vmlinux1
> > local symbol 0: discarded in section `.exit.text' from
> > drivers/built-in.o
> > make: *** [.tmp_vmlinux1] Error 1
> >
> > Running the reference discard checking tool:
> >
> > $ ~/reference_discarded.pl
> > Finding objects, 858 objects, ignoring 0 module(s)
> > Finding conglomerates, ignoring 81 conglomerate(s)
> > Scanning objects
> > Error: ./drivers/message/fusion/mptscsih.o .init.text refers
> > to 00000000000001e2 PCREL21B .exit.text
> > Done
> >
> > And, sure enough, if I remove the __exits from mptscsih_exit() I get a
> > linkable kernel. Looks like the __exits ought to be removed. Thanks,
> >
> > Alex
> >
> > --
> > Alex Williamson HP Linux & Open Source Lab
> >
--
Alex Williamson HP Linux & Open Source Lab
prev parent reply other threads:[~2004-02-05 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 20:15 mptscsih.c: discarded in section `.exit.text' from drivers/bu ilt-in.o Moore, Eric Dean
2004-02-05 20:19 ` Matthew Wilcox
2004-02-05 20:20 ` Alex Williamson [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=1076012402.3744.97.camel@patsy.fc.hp.com \
--to=alex.williamson@hp.com \
--cc=Emoore@lsil.com \
--cc=linux-scsi@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