Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) client-ip=23.128.96.36;
From:   Vignesh Raghavendra <vigneshr@ti.com>
To:     Conor Dooley <conor+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Rob Herring <robh+dt@kernel.org>, Nishanth Menon <nm@ti.com>
CC:     Vignesh Raghavendra <vigneshr@ti.com>,
        <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        Tero Kristo <kristo@kernel.org>, Tom Rini <trini@konsulko.com>,
        Bryan <bb@ti.com>, Praneeth <praneeth@ti.com>,
        Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [PATCH 0/3] arm64: dts: ti: k3-am625: Add boot phase marking
Date:   Tue, 3 Oct 2023 16:30:47 +0530
Message-ID: <169633065052.2221719.18006511616618309362.b4-ty@ti.com>
In-Reply-To: <20230911162535.1044560-1-nm@ti.com>
References: <20230911162535.1044560-1-nm@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Nishanth Menon,

On Mon, 11 Sep 2023 11:25:32 -0500, Nishanth Menon wrote:
> bootph-all as phase tag was added to dt-schema
> (dtschema/schemas/bootph.yaml) to describe various node usage during
> boot phases with DT.
> 
> Based on next-20230911
> 
> Nishanth Menon (3):
>   arm64: dts: ti: k3-am625: Add boot phase tags marking
>   arm64: dts: ti: k3-am625-beagleplay: Add boot phase tags marking
>   arm64: dts: ti: k3-am625-sk: Add boot phase tags marking
> 
> [...]

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

[1/3] arm64: dts: ti: k3-am625: Add boot phase tags marking
      commit: 87e437a0fb6cbecbabff293061793b32e3bcd3b1
[2/3] arm64: dts: ti: k3-am625-beagleplay: Add boot phase tags marking
      commit: 944adefc7f88aec1adf5f76f593d483938bc5e4e
[3/3] arm64: dts: ti: k3-am625-sk: Add boot phase tags marking
      commit: c412c2f26eed08b1836ccf79f5547b67c1b55d5d

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