linux-kernel - Re: [PATCH 1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node

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: <171417102550.3482062.1616101241058926180.b4-ty@ti.com>
Date: Fri, 26 Apr 2024 17:37:21 -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>, Andrew Davis <afd@...com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node

Hi Andrew Davis,

On Tue, 26 Mar 2024 15:59:17 -0500, Andrew Davis wrote:
> The FSS bus contains several register ranges. Using an empty
> ranges property works but causes a DT warning when we give
> this node an address. Fix this by explicitly defining the
> memory ranges in use.
> 
> 

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

[1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node
      commit: 8ec19dbe9217edbb564b16a5f68465b8cd42a167
[2/4] arm64: dts: ti: k3-j7200: Use exact ranges for FSS node
      commit: 98b939a9b3204120bd3a96015d74cbe818a3a2e9
[3/4] arm64: dts: ti: k3-j721e: Use exact ranges for FSS node
      commit: 74904fc1f1f1c802eaed10edc3744f0997c154ff
[4/4] arm64: dts: ti: k3-j784s4: Use exact ranges for FSS node
      commit: b3f629482cade3a6ada44d2e83dd65f0f1ed1293

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