From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olof Johansson Subject: Re: [PATCH] ARM: omap2: remove incorrect __init annotation Date: Wed, 19 Jun 2019 07:27:22 -0700 Message-ID: <20190619142722.hsujtf3svd7p2pt4@localhost> References: <20190619130529.1502322-1-arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20190619130529.1502322-1-arnd@arndb.de> Sender: linux-kernel-owner@vger.kernel.org To: Arnd Bergmann Cc: arm@kernel.org, Nathan Chancellor , Tony Lindgren , Rajendra Nayak , Paul Walmsley , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org List-Id: linux-omap@vger.kernel.org On Wed, Jun 19, 2019 at 03:04:54PM +0200, Arnd Bergmann wrote: > omap3xxx_prm_enable_io_wakeup() is marked __init, but its caller is not, so > we get a warning with clang-8: > > WARNING: vmlinux.o(.text+0x343c8): Section mismatch in reference from the function omap3xxx_prm_late_init() to the function .init.text:omap3xxx_prm_enable_io_wakeup() > The function omap3xxx_prm_late_init() references > the function __init omap3xxx_prm_enable_io_wakeup(). > This is often because omap3xxx_prm_late_init lacks a __init > annotation or the annotation of omap3xxx_prm_enable_io_wakeup is wrong. > > When building with gcc, omap3xxx_prm_enable_io_wakeup() is always > inlined, so we never noticed in the past. > > Signed-off-by: Arnd Bergmann > Reviewed-by: Nathan Chancellor > Acked-by: Tony Lindgren Applied to fixes. Thanks! -Olof