linux-kernel - Re: [PATCH v2 0/2] arm64: dts: ti: k3-am65: add boot phases to critical nodes

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: <175240652599.4073742.12757905646611609157.b4-ty@ti.com>
Date: Tue, 15 Jul 2025 10:58:59 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>, Bryan Brattlof <bb@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] arm64: dts: ti: k3-am65: add boot phases to critical nodes

Hi Bryan Brattlof,

On Thu, 10 Jul 2025 09:38:58 -0500, Bryan Brattlof wrote:
> To save precious on chip RAM space during bootup 'bootph-*' flags was
> added to the dt-schema to describe which nodes need to be present during
> each phase of the bootup process and which can be pruned to recover RAM
> space that would otherwise be wasted.
> 
> This small series adds the bootph-all flags to all the boot critical
> nodes for all boards that utilize the AM65x as well as to the AM65's
> reference board.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am65: add boot phase tags
      commit: 3302e07346fea5709621a71c2cdb93ffbef2108a
[2/2] arm64: dts: ti: k3-am654-base-board: add boot phase tags
      commit: df62b42b0f37c4fe71613383c6a083dfff7f2c86

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