Received-SPF: pass (google.com: domain of linux-kernel+bounces-68107-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Vignesh Raghavendra <vigneshr@ti.com>
To: <nm@ti.com>, <conor+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
        <kristo@kernel.org>, <robh+dt@kernel.org>,
        Vaishnav Achath
	<vaishnav.a@ti.com>
CC: Vignesh Raghavendra <vigneshr@ti.com>, <devicetree@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
        <u-kumar1@ti.com>, <j-choudhary@ti.com>
Subject: Re: [PATCH v2 0/3] arm64: dts: ti: Introduce J722S SoC and EVM
Date: Fri, 16 Feb 2024 12:01:29 +0530
Message-ID: <170806504068.3877215.8092202742138440785.b4-ty@ti.com>
In-Reply-To: <20240206100608.127702-1-vaishnav.a@ti.com>
References: <20240206100608.127702-1-vaishnav.a@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Vaishnav Achath,

On Tue, 06 Feb 2024 15:36:05 +0530, Vaishnav Achath wrote:
> This series adds basic support for J722S family of SoCs. Also add
> J722S EVM support with basic peripheral like MMC and UART.
> 
> TRM: https://www.ti.com/lit/zip/sprujb3
> EVM Schematics: https://www.ti.com/lit/zip/sprr495
> 
> Bootlog (6.8.0-rc3-next-20240206):
> https://gist.github.com/vaishnavachath/23d859925277df9ccd628190e7c23371
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/3] dt-bindings: arm: ti: Add bindings for J722S SoCs
      commit: de82585f62e08283572d385d0cd6b57893a99d1c
[2/3] arm64: dts: ti: Introduce J722S family of SoCs
      commit: ea55b9335ad81e32f2833c71b2dcb591792e54dd
[3/3] arm64: dts: ti: Add support for TI J722S Evaluation Module
      commit: 2f277dbe1a4ac40b1157ba3b2914d39f4040bbed

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