From:   Nishanth Menon <nm@ti.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Rob Herring <robh+dt@kernel.org>,
        Arnd Bergmann <arnd@arndb.de>, Nishanth Menon <nm@ti.com>
CC:     <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        Tero Kristo <kristo@kernel.org>,
        Vignesh Raghavendra <vigneshr@ti.com>,
        Julien Panis <jpanis@baylibre.com>, Bryan Brattlof <bb@ti.com>,
        Andrew Davis <afd@ti.com>, Jason Kridner <jkridner@gmail.com>,
        Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [PATCH V2 0/3] arm64: dts/defconfig/binding: Add support for BeaglePlay
Date:   Mon, 20 Mar 2023 18:03:25 -0500
Message-ID: <167935333606.215823.10442790342780935769.b4-ty@ti.com>
In-Reply-To: <20230316152143.2438928-1-nm@ti.com>
References: <20230316152143.2438928-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 Thu, 16 Mar 2023 10:21:40 -0500, Nishanth Menon wrote:
> BeagleBoard.org BeaglePlay[1][2] is an easy to use, affordable open source
> hardware single board computer based on the Texas Instruments AM625
> SoC. Add the base support for the same.
> 
> Bootlog: https://gist.github.com/nmenon/2e7647970a4d6af05017e545ac0f8218
> 
> Changes Since v1: (major ones)
> - All patches updated
> - signed-off-by order fixups
> - Cleanup to drop errant pre-production board vestiges
> - defconfig adds SPI to get to mikrobus spi interface.
> 
> [...]

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

[1/3] dt-bindings: arm: ti: Add BeaglePlay
      commit: 3cd557272ef0b1bbad3c5450f09629e451e101f3
[2/3] arm64: dts: ti: Add k3-am625-beagleplay
      commit: 2afe6a26744bf4245a6b33593a9c38e7cb464078

I have applied the following to branch ti-k3-config-next on [1].
[3/3] arm64: defconfig: Enable drivers for BeaglePlay
      commit: 673c8894d7d0124f14c900313d85dba0870bb7cc

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