[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190618131734.GE1959@dragon>
Date: Tue, 18 Jun 2019 21:17:35 +0800
From: Shawn Guo <shawnguo@...nel.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Dong Aisheng <aisheng.dong@....com>,
Abel Vesa <abel.vesa@....com>,
Anson Huang <anson.huang@....com>,
linux-kernel@...r.kernel.org, NXP Linux Team <linux-imx@....com>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Lucas Stach <l.stach@...gutronix.de>
Subject: Re: [PATCH] clk: imx6q: fix section mismatch warning
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@...db.de>
Applied, thanks.
Powered by blists - more mailing lists