From: Shea Levy <shea@shealevy.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.4-rc1
Date: Sat, 31 Mar 2012 22:07:35 -0400 [thread overview]
Message-ID: <4F77B867.602@shealevy.com> (raw)
In-Reply-To: <4F77B3FA.1040001@shealevy.com>
On 03/31/2012 09:48 PM, Shea Levy wrote:
> Hello,
>
> On 03/31/2012 07:58 PM, Linus Torvalds wrote:
>> Ok, it's been two weeks, and the merge window is over. Linux 3.4-rc1
>> has been pushed out to the git servers, and the tar-ball and patches
>> are going out as I type this (probably done by the time I'm done).
>>
>
> Building this fails with:
>
> Kernel: arch/x86/boot/bzImage is ready (#1)
> ERROR: "snd_tea575x_init" [drivers/media/radio/radio-maxiradio.ko]
> undefined!
> ERROR: "snd_tea575x_exit" [drivers/media/radio/radio-maxiradio.ko]
> undefined!
> WARNING: modpost: Found 6 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> .config follows, I'll build with CONFIG_DEBUG_SECTION_MISMATCH and
> report back.
>
Warnings I get:
WARNING: drivers/usb/host/xhci-hcd.o(.init.text+0x3b): Section mismatch
in reference from the function init_module() to the function
.exit.text:xhci_unregister_pci()
The function __init init_module() references
a function __exit xhci_unregister_pci().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
xhci_unregister_pci() so it may be used outside an exit section.
WARNING: drivers/usb/gadget/g_audio.o(.init.text+0x612): Section
mismatch in reference from the function afunc_bind() to the function
.devexit.text:snd_uac2_remove()
The function __init afunc_bind() references
a function __devexit snd_uac2_remove().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __devexit annotation of
snd_uac2_remove() so it may be used outside an exit section.
WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x255a): Section
mismatch in reference from the function s626_attach() to the variable
.devinit.rodata:s626_pci_table
The function s626_attach() references
the variable __devinitconst s626_pci_table.
This is often because s626_attach lacks a __devinitconst
annotation or the annotation of s626_pci_table is wrong.
WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x2560): Section
mismatch in reference from the function s626_attach() to the variable
.devinit.rodata:s626_pci_table
The function s626_attach() references
the variable __devinitconst s626_pci_table.
This is often because s626_attach lacks a __devinitconst
annotation or the annotation of s626_pci_table is wrong.
WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x2566): Section
mismatch i
n reference from the function s626_attach() to the variable
.devinit.rodata:s626_pci_table
The function s626_attach() references
the variable __devinitconst s626_pci_table.
This is often because s626_attach lacks a __devinitconst
annotation or the annotation of s626_pci_table is wrong.
WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x256c): Section
mismatch in reference from the function s626_attach() to the variable
.devinit.rodata:s626_pci_table
The function s626_attach() references
the variable __devinitconst s626_pci_table.
This is often because s626_attach lacks a __devinitconst
annotation or the annotation of s626_pci_table is wrong.
WARNING: drivers/usb/gadget/g_audio.o(.init.text+0x612): Section
mismatch in reference from the function afunc_bind() to the function
.devexit.text:snd_uac2_remove()
The function __init afunc_bind() references
a function __devexit snd_uac2_remove().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __devexit annotation of
snd_uac2_remove() so it may be used outside an exit section.
WARNING: drivers/usb/host/xhci-hcd.o(.init.text+0x3b): Section mismatch
in reference from the function init_module() to the function
.exit.text:xhci_unregister_pci()
The function __init init_module() references
a function __exit xhci_unregister_pci().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
xhci_unregister_pci() so it may be used outside an exit section.
next prev parent reply other threads:[~2012-04-01 2:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 23:58 Linux 3.4-rc1 Linus Torvalds
2012-04-01 0:09 ` Christoph Hellwig
2012-04-01 1:46 ` Shea Levy
2012-04-01 3:11 ` Linus Torvalds
2012-04-01 1:48 ` Shea Levy
2012-04-01 2:07 ` Shea Levy [this message]
2012-04-01 8:34 ` Ingo Molnar
2012-04-01 12:03 ` Stephen Rothwell
2012-04-01 19:19 ` David Miller
2012-04-01 13:14 ` linux-next stats (Was: Linux 3.4-rc1) Stephen Rothwell
2012-04-01 15:34 ` Linux 3.4-rc1 Rob Clark
2012-04-02 3:40 ` Kyungmin Park
2012-04-02 8:41 ` Daniel Vetter
[not found] ` <20120402084152.GA4612-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2012-04-04 12:24 ` Subash Patel
2012-04-04 12:24 ` Subash Patel
[not found] ` <4F7C3D84.1080407-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-04 12:33 ` Anca Emanuel
2012-04-04 12:33 ` Anca Emanuel
[not found] ` <CAJL_dMt55kRBw71om9FLdT=XbsbaY2RB5_BsBeEqFCk7f-5=0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-05 7:41 ` Marek Szyprowski
2012-04-05 7:41 ` Marek Szyprowski
2012-04-02 12:31 ` Alex Deucher
2012-04-02 9:15 ` Artem Bityutskiy
2012-04-02 9:20 ` Shubhrajyoti Datta
2012-04-02 15:48 ` Linus Walleij
2012-04-02 20:30 ` Carlos Chinea
2012-04-03 2:57 ` Kyungmin Park
2012-04-03 3:57 ` Linus Torvalds
[not found] ` <CA+55aFw1ZG9R2MzgXmi0YE64t+xH95QnVuJB55sQ6xgDbnzkyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-03 6:29 ` Hiroshi Doyu
2012-04-03 6:29 ` Hiroshi Doyu
2012-04-03 9:07 ` Arnd Bergmann
2012-04-03 14:58 ` Jerome Glisse
2012-04-03 15:35 ` Arnd Bergmann
2012-04-03 19:26 ` Krishna Reddy
2012-04-04 12:10 ` Anca Emanuel
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=4F77B867.602@shealevy.com \
--to=shea@shealevy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.