From: Adrian Bunk <bunk@stusta.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
len.brown@intel.com, Paul Bristow <paul@paulbristow.net>,
mpm@selenic.com, B.Zolnierkiewicz@elka.pw.edu.pl,
dtor_core@ameritech.net, kkeil@suse.de,
linux-dvb-maintainer@linuxtv.org, philb@gnu.org, gregkh@suse.de,
dwmw2@infradead.org
Subject: Re: kbuild: Section mismatch warnings
Date: Sat, 18 Feb 2006 00:56:33 +0100 [thread overview]
Message-ID: <20060217235633.GO4422@stusta.de> (raw)
In-Reply-To: <20060217233848.GA26630@mars.ravnborg.org>
On Sat, Feb 18, 2006 at 12:38:48AM +0100, Sam Ravnborg wrote:
> Hi Adrian
>
> > > I did not find a way to look up the offending symbol but maybe some elf
> > > expert can help?
> > >...
> >
> > I'm not an ELF expert, but simply checking all __init functions in this
> > files finds that this seems to be the following:
> >
> > <-- snip -->
> >
> > ...
> > static struct acpi_driver asus_hotk_driver = {
> > .name = ACPI_HOTK_NAME,
> > .class = ACPI_HOTK_CLASS,
> > .ids = ACPI_HOTK_HID,
> > .ops = {
> > .add = asus_hotk_add,
> > .remove = asus_hotk_remove,
> > },
> > };
> > ...
> > static int __init asus_hotk_add(struct acpi_device *device)
> > ...
> >
> Correct.
> What I wanted was modpost to tell that the symbol being referenced in
> the .data section was 'asus_hotk_add' and not just an offset after
> asus_hotk_driver.
>
> What is needed is a link from the RELOCATION RECORD to the symbol table.
Ah sorry, I misunderstood your question.
> Sam
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-17 23:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 21:48 kbuild: Sam Ravnborg
2006-02-17 22:47 ` kbuild: Section mismatch warnings Sam Ravnborg
2006-02-17 23:32 ` Adrian Bunk
2006-02-17 23:38 ` Sam Ravnborg
2006-02-17 23:56 ` Adrian Bunk [this message]
2006-02-18 0:14 ` Nicholas Miell
2006-02-18 21:25 ` Sam Ravnborg
2006-02-18 0:09 ` Greg KH
2006-02-18 0:48 ` David Brownell
2006-02-18 0:57 ` Greg KH
2006-02-18 20:32 ` David Brownell
2006-02-19 0:21 ` Sam Ravnborg
2006-02-22 5:09 ` Greg KH
2006-02-18 0:49 ` Dmitry Torokhov
2006-02-18 12:14 ` Sam Ravnborg
2006-02-18 13:34 ` Russell King
2006-02-19 11:36 ` Sam Ravnborg
2006-02-19 12:59 ` [v4l-dvb-maintainer] " Johannes Stezenbach
2006-02-19 13:19 ` Sam Ravnborg
2006-02-19 13:30 ` Johannes Stezenbach
2006-02-25 15:31 ` Adrian Bunk
2006-02-19 14:18 ` Sam Ravnborg
2006-02-19 22:38 ` Rusty Russell
2006-02-19 22:44 ` Sam Ravnborg
2006-02-18 22:12 ` kbuild: Andi Kleen
2006-02-18 22:38 ` kbuild: Sam Ravnborg
2006-02-18 23:41 ` kbuild: Sam Ravnborg
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=20060217235633.GO4422@stusta.de \
--to=bunk@stusta.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=dtor_core@ameritech.net \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=kkeil@suse.de \
--cc=len.brown@intel.com \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paul@paulbristow.net \
--cc=philb@gnu.org \
--cc=sam@ravnborg.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.