From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
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: Wed, 12 Nov 2014 15:23:42 -0800 [thread overview]
Message-ID: <5463EBFE.6070009@gmail.com> (raw)
In-Reply-To: <70798892.n4gYya0yuK@wuerfel>
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
next prev parent reply other threads:[~2014-11-12 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2014-11-20 18:16 ` Florian Fainelli
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=5463EBFE.6070009@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).