WARNING: vmlinux.o(.text+0x730e38): Section mismatch in reference from the function brcmstb_gisb_arb_probe() to the function .init.text:hook_fault_code()

PATCH New Arnd Bergmann 3 participants 5 messages Nov 11, 2014 – Nov 20, 2014

Share & tools

Arnd Bergmann

author

2014-11-11 22:52 UTC #0 lore raw

PATCH 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()

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 <[email protected]>
To: Linus Walleij <[email protected]>
CC: kbuild-all at 01.org, Arnd Bergmann <[email protected]>

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:

Quoted 1 line

Quoted 1 line
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
-----------------------------------------

Linus Walleij

2014-11-12 10:27 UTC #1 lore raw

PATCH 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()

Quoted 3 lines · Arnd Bergmann

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

Arnd Bergmann

author

2014-11-12 10:33 UTC #2 lore raw

PATCH 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()

Quoted 7 lines · On Wednesday 12 November 2014 11:27:20 Linus Walleij wrote:

Quoted 3 lines · Arnd Bergmann
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

Florian Fainelli

2014-11-12 23:23 UTC #3 lore raw

PATCH 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()

Quoted 7 lines · Arnd Bergmann

Quoted 6 lines · On Wednesday 12 November 2014 11:27:20 Linus Walleij wrote:
Quoted 3 lines · Arnd Bergmann
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.

Quoted 6 lines

Quoted 1 line
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

Florian Fainelli

2014-11-20 18:16 UTC #4 lore raw

PATCH 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()

In reply to Arnd Bergmann

Quoted 7 lines · Arnd Bergmann

Quoted 6 lines · On Wednesday 12 November 2014 11:27:20 Linus Walleij wrote:
Quoted 3 lines · Arnd Bergmann
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.

Quoted 6 lines

Quoted 1 line
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