From: Dhruva Gole <d-gole@ti.com>
To: 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>,
Roger Quadros <rogerq@kernel.org>, Andrew Davis <afd@ti.com>,
Tero Kristo <kristo@kernel.org>, Dhruva Gole <d-gole@ti.com>
Subject: [RFT][PATCH 0/2] dts: ti: Fix build warns in usb@31000000
Date: Wed, 26 Jun 2024 15:45:18 +0530 [thread overview]
Message-ID: <20240626101520.1782320-1-d-gole@ti.com> (raw)
Hi,
The series has been marked as RFT because although I was able to boot
test, it needs to be made sure that usb features aren't affected by this
change. Ideally, looking at the driver, I don't think it really is
looking at port@X but incase I missed anything please feel free to point
out.
I'm working on top of tag: next-20240625
Dhruva Gole (2):
arm64: dts: ti: k3-am62p5-sk: fix graph_child_address warnings
arm64: dts: ti: k3-am62x-sk-common: Fix graph_child_address warns
arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 16 ++++------------
arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 17 ++++-------------
2 files changed, 8 insertions(+), 25 deletions(-)
base-commit: 0fc4bfab2cd45f9acb86c4f04b5191e114e901ed
--
2.34.1
next reply other threads:[~2024-06-26 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 10:15 Dhruva Gole [this message]
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
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=20240626101520.1782320-1-d-gole@ti.com \
--to=d-gole@ti.com \
--cc=afd@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=rogerq@kernel.org \
--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).