linux-kernel - Re: [PATCH v2] arm: dts: k3-am642-evm-nand: Add bootph-all to NAND related 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: <171984950183.3152309.6737334326106721786.b4-ty@ti.com>
Date: Thu, 4 Jul 2024 13:22:13 +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>, Roger Quadros <rogerq@...nel.org>
CC: Vignesh Raghavendra <vigneshr@...com>, <srk@...com>, <praneeth@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] arm: dts: k3-am642-evm-nand: Add bootph-all to NAND related nodes

Hi Roger Quadros,

On Fri, 28 Jun 2024 13:30:38 +0300, Roger Quadros wrote:
> NAND boot would require these nodes to be present at early stage.
> Ensure that by adding "bootph-all" to relevant nodes.
> 
> 

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

[1/1] arm: dts: k3-am642-evm-nand: Add bootph-all to NAND related nodes
      commit: 447f85b70f6553218e0aa7889e8615e4b31c8a2f

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