From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>, arm-soc <arm@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH 2/4] ARM: tegra: avoid section mismatch warning
Date: Tue, 11 Dec 2018 11:28:56 +0100 [thread overview]
Message-ID: <20181211102856.GI14426@ulmo> (raw)
In-Reply-To: <CAK8P3a1zbmYMFZB8R+rs=vdJY=KNqgRPBCQNO91LcSSTR0O03Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1295 bytes --]
On Tue, Dec 11, 2018 at 11:08:53AM +0100, Arnd Bergmann wrote:
> On Tue, Dec 11, 2018 at 11:05 AM Thierry Reding
> <thierry.reding@gmail.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@arndb.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.
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?
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-11 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 21:58 [PATCH 1/4] ARM: omap2: avoid section mismatch warning Arnd Bergmann
2018-12-10 21:58 ` [PATCH 2/4] ARM: tegra: " Arnd Bergmann
2018-12-11 10:05 ` Thierry Reding
2018-12-11 10:08 ` Arnd Bergmann
2018-12-11 10:28 ` Thierry Reding [this message]
2018-12-12 21:57 ` Olof Johansson
2018-12-10 21:58 ` [PATCH 3/4] ARM: ks8695: fix " Arnd Bergmann
2018-12-12 21:56 ` Olof Johansson
2018-12-10 21:58 ` [PATCH 4/4] ARM: pxa: avoid " Arnd Bergmann
2018-12-11 9:39 ` Ulf Hansson
2018-12-11 10:10 ` Arnd Bergmann
2018-12-11 10:44 ` Linus Walleij
2018-12-12 21:56 ` Olof Johansson
2018-12-10 22:09 ` [PATCH 1/4] ARM: omap2: " Tony Lindgren
2018-12-12 22:05 ` Olof Johansson
2018-12-11 2:11 ` Santosh Shilimkar
2018-12-11 18:12 ` Kevin Hilman
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=20181211102856.GI14426@ulmo \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).