Received-SPF: pass (google.com: domain of linux-kernel+bounces-76598-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: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
        Rob Herring
	<robh@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Greg Kroah-Hartman
	<gregkh@linuxfoundation.org>,
        Peter Rosin <peda@axentia.se>, Andrew Davis
	<afd@ti.com>
CC: Vignesh Raghavendra <vigneshr@ti.com>,
        <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-j721e: Fix mux-reg-masks in hbmc_mux
Date: Thu, 22 Feb 2024 18:59:17 +0530
Message-ID: <170860805561.1966114.12049702081667007759.b4-ty@ti.com>
In-Reply-To: <20240215141957.13775-1-afd@ti.com>
References: <20240215141957.13775-1-afd@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Andrew Davis,

On Thu, 15 Feb 2024 08:19:57 -0600, Andrew Davis wrote:
> Change offset in mux-reg-masks property for hbmc_mux node
> since reg-mux property is used in compatible.
> 
> While here, update the reg region to include 4 bytes as this
> is a 32bit register.
> 
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j721e: Fix mux-reg-masks in hbmc_mux
      commit: 3d585389d454e147187684e492a0eb8f56adf311

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