From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: hwmod: fix section mismatch warnings
Date: Mon, 18 Sep 2017 09:52:04 -0700 [thread overview]
Message-ID: <20170918165204.GX5024@atomide.com> (raw)
In-Reply-To: <20170915194527.1171677-1-arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [170915 12:46]:
> Older compilers choose not to inline _setup_clkctrl_provider(),
> leading to a harmless warning:
>
> WARNING: vmlinux.o(.text+0x27b34): Section mismatch in reference from the function _setup_clkctrl_provider() to the function .init.text:memblock_virt_alloc_try_nid()
> The function _setup_clkctrl_provider() references
> the function __init memblock_virt_alloc_try_nid().
> This is often because _setup_clkctrl_provider lacks a __init
> annotation or the annotation of memblock_virt_alloc_try_nid is wrong.
>
> This annotates it as __init as well, which lets the linker
> see that it is actually correct.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Tony Lindgren <tony@atomide.com>
prev parent reply other threads:[~2017-09-18 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 19:45 [PATCH] omap: hwmod: fix section mismatch warnings Arnd Bergmann
2017-09-18 16:52 ` Tony Lindgren [this message]
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=20170918165204.GX5024@atomide.com \
--to=tony@atomide.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).