Received-SPF: pass (google.com: domain of linux-kernel+bounces-212882-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: Vignesh Raghavendra <vigneshr@ti.com>
To: <robh@kernel.org>, <conor+dt@kernel.org>, <krzk+dt@kernel.org>,
        <kristo@kernel.org>, <nm@ti.com>,
        Neha Malcom Francis <n-francis@ti.com>
CC: Vignesh Raghavendra <vigneshr@ti.com>,
        <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>, <s-k6@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH] arm64: boot: dts: ti: k3-*: Add memory node to bootloader stage
Date: Thu, 13 Jun 2024 14:19:44 +0530
Message-ID: <171826022271.240984.16412947163722025506.b4-ty@ti.com>
In-Reply-To: <20240506110203.3230255-1-n-francis@ti.com>
References: <20240506110203.3230255-1-n-francis@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Neha Malcom Francis,

On Mon, 06 May 2024 16:32:03 +0530, Neha Malcom Francis wrote:
> Add the bootph-all property to the memory node so that it can be
> accessed by FDT functions at bootloader stage.
> 
> The bootloader requires the memory node to be able to initialize and set
> the size of the DRAM banks. For this purpose, make sure all memory nodes
> are present and standardized, and modify them if not.
> 
> [...]

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

[1/1] arm64: boot: dts: ti: k3-*: Add memory node to bootloader stage
      commit: 12a29fb4f9a0597ad598f2c986c8e2509a62b6ff

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