Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Nishanth Menon <nm@ti.com>
To:     <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
        <krzysztof.kozlowski+dt@linaro.org>,
        Vaishnav Achath <vaishnav.a@ti.com>
CC:     Nishanth Menon <nm@ti.com>, <linux-arm-kernel@lists.infradead.org>,
        <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <j-keerthy@ti.com>, <u-kumar1@ti.com>, <j-luthra@ti.com>
Subject: Re: [PATCH v3 0/4] arm64: dts: ti: j7: Add device-tree nodes for MCSPI
Date:   Tue, 28 Mar 2023 07:13:04 -0500
Message-ID: <168000556145.589951.11862527421010581648.b4-ty@ti.com>
In-Reply-To: <20230321082827.14274-1-vaishnav.a@ti.com>
References: <20230321082827.14274-1-vaishnav.a@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Vaishnav Achath,

On Tue, 21 Mar 2023 13:58:23 +0530, Vaishnav Achath wrote:
> This series adds device tree nodes for Multi Channel Serial Peripheral
> Interface (MCSPI) on J721E, J7200, J721S2 and J784S4 platforms. All the
> MCSPI instances are disabled by default and can be enabled through overlays
> as required, the changes were tested using spidev loopback test for all
> instances and the data verified only for main_spi4 which is connected
> internally as slave to mcu_spi2 for all existing J7 devices.
> 
> [...]

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

[1/4] arm64: dts: ti: k3-j721e: Add MCSPI nodes
      commit: 29cb8ddaab1cdbe2ace42fc1f7f5795d7c0bd82b
[2/4] arm64: dts: ti: k3-j7200: Add MCSPI nodes
      commit: e416410edf5b35632eefad09ad022eb70dc7b926
[3/4] arm64: dts: ti: k3-j721s2: Add MCSPI nodes
      commit: e1ce299d86fbb831de1a8ae76ea6d7f911fa554a
[4/4] arm64: dts: ti: k3-j784s4: Add MCSPI nodes
      commit: e1ecd17c0d1e2219c58e5152243e4702bae4f0a4

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] git://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