linux-kernel - Re: [PATCH 0/2] arm64: dts: ti: Use simple-bus wherever possible

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: <169764101784.299606.7410332060176644485.b4-ty@ti.com>
Date:   Wed, 18 Oct 2023 20:28:15 +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>,
        Vignesh Raghavendra <vigneshr@...com>
CC:     <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] arm64: dts: ti: Use simple-bus wherever possible

Hi Vignesh Raghavendra,

On Thu, 05 Oct 2023 20:43:00 +0530, Vignesh Raghavendra wrote:
> This series coverts simple-mfd to simple-bus for segments housing Data
> movement related IPs (DMASS on AM64/AM62 and AM62A), NAVSS on the rest)
> 
> Boot tested on all K3 SoCs. excerised DMA by using ethernet and OSPI for
> sanity.
> 
> Vignesh Raghavendra (2):
>   arm64: dts: ti: k3-*: Convert DMSS to simple-bus
>   arm64: dts: ti: k3-*: Convert NAVSS to simple-bus
> 
> [...]

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

[1/2] arm64: dts: ti: k3-*: Convert DMSS to simple-bus
      commit: 6ff2e5bb81895247f0414ff6b129c8e025b99a17
[2/2] arm64: dts: ti: k3-*: Convert NAVSS to simple-bus
      commit: 6507bfa7e0cde01c5feecdbc163b392021d15cbb

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