From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dave Gerlach <d-gerlach@ti.com>, Keerthy <j-keerthy@ti.com>,
Kevin Hilman <khilman@kernel.org>,
linux-kernel@vger.kernel.org, Tero Kristo <t-kristo@ti.com>,
arm@kernel.org, Santosh Shilimkar <ssantosh@kernel.org>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] ARM: omap2: avoid section mismatch warning
Date: Mon, 10 Dec 2018 14:09:26 -0800 [thread overview]
Message-ID: <20181210220926.GF6707@atomide.com> (raw)
In-Reply-To: <20181210215856.2238253-1-arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [181210 21:59]:
> WARNING: vmlinux.o(.text+0x27530): Section mismatch in reference from the function am43xx_suspend_init() to the function .init.text:am43xx_map_scu()
> The function am43xx_suspend_init() references
> the function __init am43xx_map_scu().
> This is often because am43xx_suspend_init lacks a __init
> annotation or the annotation of am43xx_map_scu is wrong.
Acked-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-10 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 21:58 [PATCH 1/4] ARM: omap2: avoid section mismatch warning Arnd Bergmann
2018-12-10 21:58 ` [PATCH 2/4] ARM: tegra: " Arnd Bergmann
2018-12-11 10:05 ` Thierry Reding
2018-12-11 10:08 ` Arnd Bergmann
2018-12-11 10:28 ` Thierry Reding
2018-12-12 21:57 ` Olof Johansson
2018-12-10 21:58 ` [PATCH 3/4] ARM: ks8695: fix " Arnd Bergmann
2018-12-12 21:56 ` Olof Johansson
2018-12-10 21:58 ` [PATCH 4/4] ARM: pxa: avoid " Arnd Bergmann
2018-12-11 9:39 ` Ulf Hansson
2018-12-11 10:10 ` Arnd Bergmann
2018-12-11 10:44 ` Linus Walleij
2018-12-12 21:56 ` Olof Johansson
2018-12-10 22:09 ` Tony Lindgren [this message]
2018-12-12 22:05 ` [PATCH 1/4] ARM: omap2: " Olof Johansson
2018-12-11 2:11 ` Santosh Shilimkar
2018-12-11 18:12 ` Kevin Hilman
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=20181210220926.GF6707@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
/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).