public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Section mismatch warnings
Date: Tue, 31 Jul 2007 23:58:06 +0200	[thread overview]
Message-ID: <46AFB06E.2020401@googlemail.com> (raw)
In-Reply-To: <20070731204846.GA9985@uranus.ravnborg.org>

Sam Ravnborg wrote:
> On Tue, Jul 31, 2007 at 09:45:22PM +0200, Gabriel C wrote:
>> Hi Sam ,
>>
>> me again. I got some more mismatch warnings with a randconfig ( http://194.231.229.228/git-current/randconfig-auto-14 )
>>
>>
>> ...
>>
>>
>>   MODPOST vmlinux.o
>> WARNING: vmlinux.o(.text+0x8adb): Section mismatch: reference to .init.text:register_cpu (between 'arch_register_cpu' and 'text_poke')
>> WARNING: vmlinux.o(.text+0xb790c): Section mismatch: reference to .init.text:pcibios_fixup_bus (between 'pci_scan_child_bus' and 'pci_scan_bus_parented')
> They need further analysis.

< big snip >

> All the hda_preset stuff should be marked __devinit as far as I can see.
> Care to give that a spin yourself?

Yes.

I'm not sure I can do it today but tomorrow for sure.
 
> 
>> WARNING: vmlinux.o(.data+0xacb10): Section mismatch: reference to .init.text:snd_ad1889_probe (between 'ad1889_pci' and 'ops.20707')
>> WARNING: vmlinux.o(.text+0x12f014): Section mismatch: reference to .exit.text:mlx4_remove_one (between 'mlx4_restart_one' and 'mlx4_cleanup_mcg_table')
> Did not look at these two yet.
> 
>> WARNING: vmlinux.o(.init.text+0x29d40): Section mismatch: reference to .exit.text:wbsd_release_resources (between 'wbsd_init' and 'wbsd_probe')
>> WARNING: vmlinux.o(.init.text+0x29d49): Section mismatch: reference to .exit.text:wbsd_free_mmc (between 'wbsd_init' and 'wbsd_probe')
>> WARNING: vmlinux.o(.init.text+0x29f28): Section mismatch: reference to .exit.text:wbsd_free_mmc (between 'wbsd_init' and 'wbsd_probe')
> When a function is marked __exit and used from an init function then the safe choice
> is to just remove the __exit marking. Usually this is small functions used
> only in error situations.
> Should be trivial too.

I'll look at those too

> 
> Sorry - no patch this time. Could you try to look at it yorself then I will review.

Ok I'll try.


> 
> 	Sam
> 

Gabriel

  reply	other threads:[~2007-07-31 21:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 17:48 Section mismatch warnings Gabriel C
2007-07-30 18:51 ` Sam Ravnborg
2007-07-30 19:31   ` Gabriel C
2007-07-31 19:45     ` Gabriel C
2007-07-31 20:48       ` Sam Ravnborg
2007-07-31 21:58         ` Gabriel C [this message]
2007-08-01  1:30           ` [PATCH] Fix section mismatch warnings in sound/pci/hda/ Gabriel C
2007-08-02 14:27           ` Section mismatch warnings Gabriel C
2007-08-02 16:31             ` Sam Ravnborg
2007-08-02 17:12               ` Gabriel C
2007-08-02 17:59                 ` Sam Ravnborg
2007-08-02 18:24                   ` Gabriel C
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23 17:40 Jan Engelhardt
2006-06-23 22:12 ` Sam Ravnborg
2006-06-23 22:22   ` Al Viro
2006-06-24 21:02     ` Sam Ravnborg
2006-06-23 22:23   ` Al Viro
2006-06-26 12:37     ` Roman Zippel

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=46AFB06E.2020401@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox