[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <170719349984.2245010.11811390979313823199.b4-ty@ti.com>
Date: Tue, 6 Feb 2024 14:10:04 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Andrew Davis <afd@...com>, Nishanth Menon <nm@...com>,
Tero Kristo
<kristo@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Bryan Brattlof <bb@...com>,
Keerthy <j-keerthy@...com>, Manorit Chawdhry
<m-chawdhry@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Udit Kumar <u-kumar1@...com>
Subject: Re: [PATCH v2 0/2] TI: K3: Fix the device IDs for VTM node.
Hi Manorit Chawdhry,
On Thu, 01 Feb 2024 13:37:25 +0530, Manorit Chawdhry wrote:
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-j721s2: Fix power domain for VTM node
commit: 5ef196ed912e80a1e64936119ced8d7eb5635f0f
[2/2] arm64: dts: ti: k3-j784s4: Fix power domain for VTM node
commit: e4d252e6d29208aea56d4c04270523e306b1e3c2
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
--
Vignesh
Powered by blists - more mailing lists