From: Sean MacLennan <smaclennan@pikatech.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: emac/zmii link warnings
Date: Tue, 15 Jan 2008 00:45:33 -0500 [thread overview]
Message-ID: <478C487D.9050407@pikatech.com> (raw)
In-Reply-To: <20080115152748.d0a05e1b.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> On Mon, 14 Jan 2008 23:15:41 -0500 Sean MacLennan <smaclennan@pikatech.com> wrote:
>
>> I keep getting these link(?) warnings:
>>
>> WARNING: vmlinux.o(.data+0x16178): Section mismatch: reference to .init.text:emac_of_bus_notify (between 'emac_of_bus_notifier' and 'emac_phy_map_lock')
>>
>
> emac_of_bus_notify is marked __devinit and is referred to by
> emac_of_bus_notifier (which is not marked thus) (in
> drivers/net/ibm_newemac/core.c).
>
>
The __devinitdata solves this.
>> WARNING: vmlinux.o(.init.text+0x16ba8): Section mismatch: reference to .exit.text:zmii_detach (between 'emac_probe' and 'zmii_probe')
>> WARNING: vmlinux.o(.init.text+0x16bb4): Section mismatch: reference to .exit.text:mal_unregister_commac (between 'emac_probe' and 'zmii_probe')
>>
>
> These will be similar but function calls.
>
>
The problem here is that emac_probe calls zmii_detach. emacs_probe is a
__devinit and zmii_detach is a __devexit. At least I assume that is the
problem.
I am a long time emacs (actually xemacs) user. If I had a nickel for
every time I typed emacs rather than emac, I would be a very rich man.
Cheers,
Sean
next prev parent reply other threads:[~2008-01-15 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 4:15 emac/zmii link warnings Sean MacLennan
2008-01-15 4:27 ` Stephen Rothwell
2008-01-15 4:45 ` Sean MacLennan
2008-01-15 5:26 ` Stephen Rothwell
2008-01-15 5:45 ` Sean MacLennan [this message]
2008-02-07 5:08 ` [PATCH] " Sean MacLennan
2008-02-14 15:30 ` Josh Boyer
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=478C487D.9050407@pikatech.com \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.