[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174500265898.95535.4453778649749724956.b4-ty@ti.com>
Date: Fri, 18 Apr 2025 13:57:50 -0500
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, Yemike Abhilash Chandra <y-abhilashchandra@...com>
CC: Nishanth Menon <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <vaishnav.a@...com>,
<jai.luthra@...ux.dev>, <linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <imx@...ts.linux.dev>,
<linux-kernel@...r.kernel.org>, <u-kumar1@...com>
Subject: Re: [PATCH v3 0/7] Fix dtbs_check warnings in CSI overlays
Hi Yemike Abhilash Chandra,
On Tue, 15 Apr 2025 16:43:21 +0530, Yemike Abhilash Chandra wrote:
> There are a bunch of new warnings generated using CONFIG_OF_ALL_DTBS.
> This configuration applies DTB and overlay together to generate test DTBs,
> which are then validated using dtbs_check.
>
> This patch series fixes all warnings related to sensor overlays on
> jacinto platforms and a few minor warnings on sitara as well.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/7] arm64: dts: ti: j721e-sk: Add DT nodes for power regulators
commit: 97b67cc102dc2cc8aa39a569c22a196e21af5a21
[2/7] arm64: dts: ti: am68-sk: Fix regulator hierarchy
commit: 7edf0a4d3bb7f5cd84f172b76c380c4259bb4ef8
[3/7] arm64: dts: ti: k3-j721e-sk: Remove clock-names property from IMX219 overlay
commit: 24ab76e55ef15450c6681a2b5db4d78f45200939
[4/7] arm64: dts: ti: k3-j721e-sk: Add requiried voltage supplies for IMX219
commit: c6a20a250200da6fcaf80fe945b7b92cba8cfe0f
[5/7] arm64: dts: ti: k3-am62x: Remove clock-names property from IMX219 overlay
commit: c68ab54a89a8c935732589a35ea2596e2329f167
[6/7] arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in IMX219 overlay
commit: 7b75dd2029ee01a8c11fcf4d97f3ccebbef9f8eb
[7/7] arm64: dts: ti: k3-am62x: Rename I2C switch to I2C mux in OV5640 overlay
commit: b22cc402d38774ccc552d18e762c25dde02f7be0
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists