linux-kernel - Re: [PATCH 0/2] dt-bindings: arm: ti: k3: Sort alphabetically

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: <166195533442.358015.9606670388489997924.b4-ty@ti.com>
Date:   Wed, 31 Aug 2022 19:47:15 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     Nishanth Menon <nm@...com>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>,
        Daniel Thompson <daniel.thompson@...aro.org>,
        Tero Kristo <kristo@...nel.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>
Subject: Re: [PATCH 0/2] dt-bindings: arm: ti: k3: Sort alphabetically

Hi Nishanth Menon,

On Tue, 30 Aug 2022 11:05:05 -0500, Nishanth Menon wrote:
> Inspired by the discussion in [1] - sort the yaml to keep things clean
> for the new SoCs and boards that are getting added in.
> 
> [1] https://lore.kernel.org/all/d7303503-70ef-7307-8cc0-1bc334c9e6af@linaro.org/
> 
> Nishanth Menon (2):
>   dt-bindings: arm: ti: k3: Sort the am654 board enums
>   dt-bindings: arm: ti: k3: Sort the SoC definitions alphabetically
> 
> [...]

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

[1/2] dt-bindings: arm: ti: k3: Sort the am654 board enums
      commit: 5f120a4dc7a71187fdae0a11f6c65b7e2cf7a2d7
[2/2] dt-bindings: arm: ti: k3: Sort the SoC definitions alphabetically
      commit: b7365658294304fac75bf33d11824d3a949122a2

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