From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Herve Codina (Schneider Electric)" <herve.codina@bootlin.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pascal Eberhard <pascal.eberhard@se.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] ARM: dts: r9a06g032: Add #address-cells in the GIC node
Date: Tue, 10 Mar 2026 23:06:57 +0100 [thread overview]
Message-ID: <abCWATS9MiRhcqlM@shikoro> (raw)
In-Reply-To: <20260303102029.147359-1-herve.codina@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Tue, Mar 03, 2026 at 11:20:29AM +0100, Herve Codina (Schneider Electric) wrote:
> When checking dts involving the r9a06g032.dtsi file, the following kind
> of warnings are reported:
> Missing property '#address-cells' in node xxx, using 0 as fallback
>
> Indeed, #address-cells is not present in the GIC interrupt controller
> node.
>
> Fix it adding the missing property.
>
> No functional change.
>
> Signed-off-by: Herve Codina (Schneider Electric) <herve.codina@bootlin.com>
How did you trigger this? It doesn't show up with the upstream DTs for
N1D. Can you share the snippet which causes the problem for you?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-10 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 10:20 [PATCH] ARM: dts: r9a06g032: Add #address-cells in the GIC node Herve Codina (Schneider Electric)
2026-03-10 22:06 ` Wolfram Sang [this message]
2026-03-11 7:30 ` Herve Codina
2026-03-11 8:29 ` Wolfram Sang
2026-03-11 7:35 ` Krzysztof Kozlowski
2026-03-11 8:32 ` Wolfram Sang
2026-03-11 8:39 ` Geert Uytterhoeven
2026-03-11 10:21 ` Herve Codina
2026-03-24 9:17 ` Herve Codina
2026-03-24 19:13 ` Wolfram Sang
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=abCWATS9MiRhcqlM@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=pascal.eberhard@se.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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