Hi Manorit Chawdhry,
On Mon, 02 Sep 2024 17:56:48 +0530, Manorit Chawdhry wrote:
> The series adds support for J742S2 family of SoCs. Also adds J742S2 EVM
> Support and re-uses most of the stuff from the superset device J784s4.
>
> It initially cleans up the J784s4 SoC files so that they can be
> re-usable for j742s2 by introducing -common files. Next it cleans up the
> EVM files for j784s4 in a similar way and then goes about adding the
> support for j742s2.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/5] arm64: dts: ti: Refactor J784s4 SoC files to a common file
commit: 9cc161a4509c2fda7cbe35b4858b496cec03c5d0
[2/5] arm64: dts: ti: Refactor J784s4-evm to a common file
commit: 39b623c05c4652f2ec450a07cee3d179a283733b
[3/5] dt-bindings: arm: ti: Add bindings for J742S2 SoCs and Boards
commit: 9c65033884bfec836fe45f21d079de40fc7c7bda
[4/5] arm64: dts: ti: Introduce J742S2 SoC family
commit: 38fd90a3e1ac7e948081cf168cf10f0a20febc21
[5/5] arm64: dts: ti: Add support for J742S2 EVM board
commit: 13dc96a52712053cfad59b0d11cab694ed5bc5ef
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
