linux-kernel - Re: (subset) [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <172452924926.505816.7580905718644351705.b4-ty@ti.com>
Date: Sat, 24 Aug 2024 14:54:48 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...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>,
        Jan
 Kiszka <jan.kiszka@...mens.com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        Bao Cheng Su
	<baocheng.su@...mens.com>,
        Diogo Ivo <diogo.ivo@...mens.com>
Subject: Re: (subset) [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs_check warnings

Hi Jan Kiszka,

On Wed, 14 Aug 2024 18:37:16 +0200, Jan Kiszka wrote:
> Changes in v4:
>  - drop no longer applicable mux-controller
>  - model dss-oldi-io-ctrl@...0 and clock-controller@...0 as regular property
> 
> Changes in v3:
>  - convert mux-controller from patternProperties to regular one
>  - dropped k3-j72xx-mcu-wakeup patch after simple-bus conversion
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
I have picked Andrew's fixups, so just 1 patch in this series
is relevant. Let me know if you disagree. Thank you!

[1/3] arm64: dts: ti: k3-am642-evm: Silence schema warning
      commit: 182a862560097dec7adf774af58076984cd6c1ed

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D