From: Shawn Guo <shawnguo@kernel•org>
To: Arnd Bergmann <arnd@arndb•de>
Cc: Dong Aisheng <aisheng.dong@nxp•com>,
Abel Vesa <abel.vesa@nxp•com>, Anson Huang <anson.huang@nxp•com>,
Stephen Boyd <sboyd@kernel•org>,
Michael Turquette <mturquette@baylibre•com>,
linux-kernel@vger•kernel.org, linux-clk@vger•kernel.org,
NXP Linux Team <linux-imx@nxp•com>,
Pengutronix Kernel Team <kernel@pengutronix•de>,
Fabio Estevam <festevam@gmail•com>,
Sascha Hauer <s.hauer@pengutronix•de>,
linux-arm-kernel@lists•infradead.org,
Lucas Stach <l.stach@pengutronix•de>
Subject: Re: [PATCH] clk: imx6q: fix section mismatch warning
Date: Tue, 18 Jun 2019 21:17:35 +0800 [thread overview]
Message-ID: <20190618131734.GE1959@dragon> (raw)
In-Reply-To: <20190617111159.2124152-1-arnd@arndb.de>
On Mon, Jun 17, 2019 at 01:11:35PM +0200, Arnd Bergmann wrote:
> The imx6q_obtain_fixed_clk_hw lacks an __init marker, which
> leads to this otherwise harmless warning:
>
> WARNING: vmlinux.o(.text+0x495358): Section mismatch in reference from the function imx6q_obtain_fixed_clk_hw() to the function .init.text:imx_obtain_fixed_clock_hw()
> The function imx6q_obtain_fixed_clk_hw() references
> the function __init imx_obtain_fixed_clock_hw().
> This is often because imx6q_obtain_fixed_clk_hw lacks a __init
> annotation or the annotation of imx_obtain_fixed_clock_hw is wrong.
>
> Fixes: 992b703b5b38 ("clk: imx6q: Switch to clk_hw based API")
> Signed-off-by: Arnd Bergmann <arnd@arndb•de>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-18 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 11:11 [PATCH] clk: imx6q: fix section mismatch warning Arnd Bergmann
2019-06-18 13:17 ` Shawn Guo [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=20190618131734.GE1959@dragon \
--to=shawnguo@kernel$(echo .)org \
--cc=abel.vesa@nxp$(echo .)com \
--cc=aisheng.dong@nxp$(echo .)com \
--cc=anson.huang@nxp$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=festevam@gmail$(echo .)com \
--cc=kernel@pengutronix$(echo .)de \
--cc=l.stach@pengutronix$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mturquette@baylibre$(echo .)com \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=sboyd@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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