[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1zbmYMFZB8R+rs=vdJY=KNqgRPBCQNO91LcSSTR0O03Q@mail.gmail.com>
Date: Tue, 11 Dec 2018 11:08:53 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Thierry Reding <thierry.reding@...il.com>
Cc: arm-soc <arm@...nel.org>, Jonathan Hunter <jonathanh@...dia.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"open list:TEGRA ARCHITECTURE SUPPORT" <linux-tegra@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] ARM: tegra: avoid section mismatch warning
On Tue, Dec 11, 2018 at 11:05 AM Thierry Reding
<thierry.reding@...il.com> 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 <arnd@...db.de>
> > ---
> > 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.
Arnd
Powered by blists - more mailing lists