From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rob Herring <robherring2@gmail•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: build warnings after merge of the devicetree tree
Date: Wed, 5 Sep 2018 10:39:06 +1000 [thread overview]
Message-ID: <20180905103906.232545a4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Hi Rob,
After merging the devicetree tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the function of_fdt_limit_memory() to the variable .init.data:dt_root_addr_cells
The function of_fdt_limit_memory() references
the variable __initdata dt_root_addr_cells.
This is often because of_fdt_limit_memory lacks a __initdata
annotation or the annotation of dt_root_addr_cells is wrong.
WARNING: vmlinux.o(.text+0xf40a1d): Section mismatch in reference from the function of_fdt_limit_memory() to the variable .init.data:dt_root_size_cells
The function of_fdt_limit_memory() references
the variable __initdata dt_root_size_cells.
This is often because of_fdt_limit_memory lacks a __initdata
annotation or the annotation of dt_root_size_cells is wrong.
Introduced by commit
bb35ea5c7c30 ("of/fdt: avoid re-parsing '#{address,size}-cells' in of_fdt_limit_memory")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-09-05 0:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 0:39 Stephen Rothwell [this message]
2018-09-05 1:54 ` linux-next: build warnings after merge of the devicetree tree Stephen Rothwell
2018-09-05 11:20 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2018-09-20 1:47 Stephen Rothwell
2018-09-20 13:49 ` Rob Herring
2020-03-16 1:11 Stephen Rothwell
2021-03-29 8:53 Stephen Rothwell
2021-03-29 9:48 ` Lee Jones
2022-01-15 4:32 Stephen Rothwell
2022-01-15 11:33 ` Michael Walle
2025-11-18 3:38 Stephen Rothwell
2025-11-28 5:10 ` Stephen Rothwell
2025-11-28 14:54 ` Rob Herring
2025-11-28 22:31 ` Stephen Rothwell
2025-12-16 1:19 ` Stephen Rothwell
2025-12-18 10:15 ` Stephen Rothwell
2025-12-18 13:06 ` Rob Herring
2026-01-05 5:44 ` Stephen Rothwell
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=20180905103906.232545a4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robherring2@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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