From: Roger Quadros <rogerq@kernel.org>
To: Dhruva Gole <d-gole@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Andrew Davis <afd@ti.com>,
Tero Kristo <kristo@kernel.org>
Subject: Re: [RFT][PATCH 2/2] arm64: dts: ti: k3-am62x-sk-common: Fix graph_child_address warns
Date: Mon, 1 Jul 2024 15:41:54 +0300 [thread overview]
Message-ID: <d9efc055-523c-4afe-8945-7bfc1ddbb481@kernel.org> (raw)
In-Reply-To: <20240626101520.1782320-3-d-gole@ti.com>
On 26/06/2024 13:15, Dhruva Gole wrote:
> Fix the following warnings when compiling dtbs with W=1:
>
> ../arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi:343.10-353.6: Warning (graph_child_address): /bus@f0000/i2c@20000000/tps6598x@3f/connector/ports: graph node has single child node 'port@0', #address-cells/#size-cells are not necessary
> ../arch/arm64/boot/dts/ti/k3-am62-main.dtsi:633.22-643.5: Warning (graph_child_address): /bus@f0000/dwc3-usb@f900000/usb@31000000: graph node has single child node 'port@0', #address-cells/#size-cells are not necessary
>
> Cc: Roger Quadros <rogerq@kernel.org>
> Signed-off-by: Dhruva Gole <d-gole@ti.com>
Tested-by: Roger Quadros <rogerq@kernel.org>
next prev parent reply other threads:[~2024-07-01 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 10:15 [RFT][PATCH 0/2] dts: ti: Fix build warns in usb@31000000 Dhruva Gole
2024-06-26 10:15 ` [RFT][PATCH 1/2] arm64: dts: ti: k3-am62p5-sk: fix graph_child_address warnings Dhruva Gole
2024-07-01 12:41 ` Roger Quadros
2024-06-26 10:15 ` [RFT][PATCH 2/2] arm64: dts: ti: k3-am62x-sk-common: Fix graph_child_address warns Dhruva Gole
2024-07-01 12:41 ` Roger Quadros [this message]
2024-07-03 4:39 ` [RFT][PATCH 0/2] dts: ti: Fix build warns in usb@31000000 Vignesh Raghavendra
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=d9efc055-523c-4afe-8945-7bfc1ddbb481@kernel.org \
--to=rogerq@kernel.org \
--cc=afd@ti.com \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).