From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olof Johansson Subject: Re: [PATCH 2/4] ARM: tegra: avoid section mismatch warning Date: Wed, 12 Dec 2018 13:57:41 -0800 Message-ID: <20181212215741.uvkbvf5cvcvvod42@localhost> References: <20181210215856.2238253-1-arnd@arndb.de> <20181210215856.2238253-2-arnd@arndb.de> <20181211100550.GD14426@ulmo> <20181211102856.GI14426@ulmo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20181211102856.GI14426@ulmo> Sender: linux-kernel-owner@vger.kernel.org To: Thierry Reding Cc: Arnd Bergmann , arm-soc , Jonathan Hunter , Linux ARM , "open list:TEGRA ARCHITECTURE SUPPORT" , Linux Kernel Mailing List List-Id: linux-tegra@vger.kernel.org On Tue, Dec 11, 2018 at 11:28:56AM +0100, Thierry Reding wrote: > On Tue, Dec 11, 2018 at 11:08:53AM +0100, Arnd Bergmann wrote: > > On Tue, Dec 11, 2018 at 11:05 AM Thierry Reding > > wrote: > > > > > > On Mon, Dec 10, 2018 at 10:58:37PM +0100, Arnd Bergmann wrote: > > > > WARNING: vmlinux.o(.text+0x39ecc): Section mismatch in reference from the function tegra114_gic_cpu_pm_registration() to the (unknown reference) .init.rodata:(unknown) > > > > The function tegra114_gic_cpu_pm_registration() references > > > > the (unknown reference) __initconst (unknown). > > > > This is often because tegra114_gic_cpu_pm_registration lacks a __initconst > > > > annotation or the annotation of (unknown) is wrong. > > > > > > > > Signed-off-by: Arnd Bergmann > > > > --- > > > > arch/arm/mach-tegra/irq.c | 4 ++-- > > > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > > > I'm not seeing these. Do I need to enable any special options to trigger > > > these? Or are these just so new that I haven't run into them yet? > > > > My guess would be that this is a result of the CONFIG_NO_AUTO_INLINE > > option that is now available in linux-next. > > Okay, that would explain. It's not set in my configurations currently. > > Do you want to apply this to ARM-SoC directly with my Acked-by, or > should I queue it up for v4.22? I'm picking up a few others of these, so I'll include it in that batch. Applied to arm-soc next/soc. Thanks! -Olof