On Thu, 12 Nov 2020 12:35:33 -0600, Nishanth Menon wrote:
> Changes since v2[3]:
> - Rebase on top of ti-k3-dts-next (no functional changes)
> - picked up reviewed-by and acks from folks.
>
> Since we have all the required acks and reviews, I will apply this
> series tomorrow morning since this can cause churn for other folks.
>
> [...]
Hi,
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/5] arm64: dts: ti: k3-am65*: Cleanup disabled nodes at SoC dtsi level
commit: 957c8a49d2ed0d9ed710c8643d43912b64a3708a
[2/5] arm64: dts: ti: k3-j721e*: Cleanup disabled nodes at SoC dtsi level
commit: f388cb320905e0908429ce5ce8b14b5fadb6a1ea
[3/5] arm64: dts: ti: am65/j721e: Fix up un-necessary status set to "okay" for crypto
commit: 2fcb0ff200d0c9b0c5cab541cc8f8444d937e9ca
[4/5] arm64: dts: ti: k3-am654-base-board: Fix up un-necessary status set to "okay" for USB
commit: 399e08d521a34ca8180c8eaeaf181176ace85b47
[5/5] arm64: dts: ti: am65/j721e/j7200: Mark firmware used uart as "reserved"
commit: cf2e8c96b52984319c27f1e0b68fbef712df9bb9
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/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
