[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <170904289248.941614.3402741542948596682.b4-ty@ti.com>
Date: Tue, 27 Feb 2024 19:39:46 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
Rob Herring
<robh+dt@...nel.org>,
Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Josua Mayer <josua@...id-run.com>
CC: Vignesh Raghavendra <vigneshr@...com>,
Yazan Shhady
<yazan.shhady@...id-run.com>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
"Krzysztof
Kozlowski" <krzysztof.kozlowski@...aro.org>,
Suman Anna <s-anna@...com>,
Grygorii Strashko <grygorii.strashko@...com>,
MD Danish Anwar
<danishanwar@...com>
Subject: Re: (subset) [PATCH v7 0/4] arm64: dts: add description for solidrun am642 som and hummingboard evb
Hi Josua Mayer,
On Mon, 19 Feb 2024 16:02:59 +0100, Josua Mayer wrote:
> This series adds DT bindings and dts descriptions for SolidRun AM642
> based SoM and Hummingboard EVB.
>
> Additionally a commit from downstream vendor kernel are included,
> enhancing support for pru based ethernet.
> I wasn't sure how to properly annotate it in commit description /
> signed-off area ...:
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/4] dt-bindings: arm: ti: Add bindings for SolidRun AM642 HummingBoard-T
commit: d14bae4087c5abf5bd2d56c0cc3c9e849ad2ae44
[3/4] arm64: dts: add description for solidrun am642 som and evaluation board
commit: d60483faf914b4d404a9732476278ac13bb33b70
[4/4] arm64: dts: ti: hummingboard-t: add overlays for m.2 pci-e and usb-3
commit: bbef42084cc170cbfc035bf784f2ff055c939d7e
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
Powered by blists - more mailing lists