Hi Kishon Vijay Abraham I, On Thu, 2 Jun 2022 17:36:10 +0530, Kishon Vijay Abraham I wrote: > Series adds AM62x specific compatible string to enable PRUSS-M in > AM62x SoCs. > > Changes from v1: > 1) Added a new patch to re-arrange "compatible" in alphabetic > order > > [...] I have applied the following to branch ti-drivers-soc-next on [1]. Thank you! [1/3] dt-bindings: soc: ti: pruss: Re-arrange "compatible" in alphabetic order commit: b8c8d647f2fe4e263864b800f4647431ec0aabdf [2/3] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs commit: 75938bab63a4bf5c654360aebfb96235de10d882 [3/3] soc: ti: pruss: Enable support for PRUSS-M subsystem on K3 AM62x SoCs commit: f16afe238a7ff3c71a943cf74392538974c29b22 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