* Fwd: [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
@ 2014-11-11 22:52 Arnd Bergmann
2014-11-12 10:27 ` Linus Walleij
0 siblings, 1 reply; 5+ messages in thread
From: Arnd Bergmann @ 2014-11-11 22:52 UTC (permalink / raw)
To: linux-arm-kernel
The problem was introduced by f1bee783dd37 "bus: brcmstb_gisb: register the
fault code hook", as hook_fault_code is an __init function and is now
called from a probe function.
Arnd
---------- Forwarded Message ----------
Subject: [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
Date: Wednesday 12 November 2014, 06:41:51
From: kbuild test robot <fengguang.wu@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
CC: kbuild-all at 01.org, Arnd Bergmann <arnd@arndb.de>
tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git next/soc
head: dc680b989d519952e0e0d37204fec850925a0225
commit: dc680b989d519952e0e0d37204fec850925a0225 [1/1] ARM: fix multiplatform allmodcompile
config: arm-allmodconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout dc680b989d519952e0e0d37204fec850925a0225
# save the attached .config to linux build tree
make.cross ARCH=arm
All warnings:
>> WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
The function brcmstb_gisb_arb_probe() references
the function __init hook_fault_code().
This is often because brcmstb_gisb_arb_probe lacks a __init
annotation or the annotation of hook_fault_code is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
-----------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
* [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
2014-11-11 22:52 Fwd: [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code() Arnd Bergmann
@ 2014-11-12 10:27 ` Linus Walleij
2014-11-12 10:33 ` Arnd Bergmann
0 siblings, 1 reply; 5+ messages in thread
From: Linus Walleij @ 2014-11-12 10:27 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Nov 11, 2014 at 11:52 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> The problem was introduced by f1bee783dd37 "bus: brcmstb_gisb: register the
> fault code hook", as hook_fault_code is an __init function and is now
> called from a probe function.
I hope it's not my fault, it doesn't seem to have my name on it :)
Linus
^ permalink raw reply [flat|nested] 5+ messages in thread
* [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
2014-11-12 10:27 ` Linus Walleij
@ 2014-11-12 10:33 ` Arnd Bergmann
2014-11-12 23:23 ` Florian Fainelli
2014-11-20 18:16 ` Florian Fainelli
0 siblings, 2 replies; 5+ messages in thread
From: Arnd Bergmann @ 2014-11-12 10:33 UTC (permalink / raw)
To: linux-arm-kernel
On Wednesday 12 November 2014 11:27:20 Linus Walleij wrote:
> On Tue, Nov 11, 2014 at 11:52 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>
> > The problem was introduced by f1bee783dd37 "bus: brcmstb_gisb: register the
> > fault code hook", as hook_fault_code is an __init function and is now
> > called from a probe function.
>
> I hope it's not my fault, it doesn't seem to have my name on it
No, it's not. The reason that the build bot sent it to you is that you
fixed another problem that prevented the kernel from getting built, so
now it builds again and we see the new warning that was introduced while
the kernel didn't build.
Arnd
^ permalink raw reply [flat|nested] 5+ messages in thread
* [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
2014-11-12 10:33 ` Arnd Bergmann
@ 2014-11-12 23:23 ` Florian Fainelli
2014-11-20 18:16 ` Florian Fainelli
1 sibling, 0 replies; 5+ messages in thread
From: Florian Fainelli @ 2014-11-12 23:23 UTC (permalink / raw)
To: linux-arm-kernel
On 11/12/2014 02:33 AM, Arnd Bergmann wrote:
> On Wednesday 12 November 2014 11:27:20 Linus Walleij wrote:
>> On Tue, Nov 11, 2014 at 11:52 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>>
>>> The problem was introduced by f1bee783dd37 "bus: brcmstb_gisb: register the
>>> fault code hook", as hook_fault_code is an __init function and is now
>>> called from a probe function.
>>
>> I hope it's not my fault, it doesn't seem to have my name on it
>
> No, it's not. The reason that the build bot sent it to you is that you
> fixed another problem that prevented the kernel from getting built, so
> now it builds again and we see the new warning that was introduced while
> the kernel didn't build.
I will submit a fix for that. Thanks!
--
Florian
^ permalink raw reply [flat|nested] 5+ messages in thread
* [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()
2014-11-12 10:33 ` Arnd Bergmann
2014-11-12 23:23 ` Florian Fainelli
@ 2014-11-20 18:16 ` Florian Fainelli
1 sibling, 0 replies; 5+ messages in thread
From: Florian Fainelli @ 2014-11-20 18:16 UTC (permalink / raw)
To: linux-arm-kernel
On 11/12/2014 02:33 AM, Arnd Bergmann wrote:
> On Wednesday 12 November 2014 11:27:20 Linus Walleij wrote:
>> On Tue, Nov 11, 2014 at 11:52 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>>
>>> The problem was introduced by f1bee783dd37 "bus: brcmstb_gisb: register the
>>> fault code hook", as hook_fault_code is an __init function and is now
>>> called from a probe function.
>>
>> I hope it's not my fault, it doesn't seem to have my name on it
>
> No, it's not. The reason that the build bot sent it to you is that you
> fixed another problem that prevented the kernel from getting built, so
> now it builds again and we see the new warning that was introduced while
> the kernel didn't build.
I just sent a fix for this as
1416507286-14083-1-git-send-email-f.fainelli at gmail.com
Thanks!
--
Florian
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-11-20 18:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-11 22:52 Fwd: [arm-soc:next/soc 1/1] WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code() Arnd Bergmann
2014-11-12 10:27 ` Linus Walleij
2014-11-12 10:33 ` Arnd Bergmann
2014-11-12 23:23 ` Florian Fainelli
2014-11-20 18:16 ` Florian Fainelli
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.