linux-kernel - Re: [PATCH 0/4] arm64: dts: ti: k3-*: Fixup nodes to exposed to be non-compliant with yaml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <162101471740.23039.13267585824105304513.b4-ty@ti.com>
Date:   Fri, 14 May 2021 12:52:07 -0500
From:   Nishanth Menon <nm@...com>
To:     Tero Kristo <kristo@...nel.org>, Nishanth Menon <nm@...com>
CC:     <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] arm64: dts: ti: k3-*: Fixup nodes to exposed to be non-compliant with yaml

On Mon, 10 May 2021 09:50:29 -0500, Nishanth Menon wrote:
> Series of minor fixups for v5.13-rc1 for compliance exposed by yaml
> conversion in the series:
> https://lore.kernel.org/linux-arm-kernel/20210503190824.GA2192378@robh.at.kernel.org/#t
> 
> Minimal testing performed on k3 platforms.
> 
> If possible, will be good to get in 5.13 window.
> 
> [...]

Hi Nishanth Menon,

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

[1/4] arm64: dts: ti: k3-*: Rename the TI-SCI clocks node name
      commit: a0812885fa7a1074c8003484b8176ffe28d5df68
[2/4] arm64: dts: ti: k3-am65-wakeup: Add debug region to TI-SCI node
      commit: 830454bbd628330c3779c3de637b709dae790da0
[3/4] arm64: dts: ti: k3-am65-wakeup: Drop un-necessary properties from dmsc node
      commit: 421c06b8761abd7d953148f5b955b4149df9846e
[4/4] arm64: dts: ti: k3-*: Rename the TI-SCI node
      commit: 9d3c9378f96a95f15881ee3373d2c2f773273fc2

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