linux-kernel - Re: [PATCH] arm64: dts: ti: k3-am62p-j722s: fix pinctrl-single size

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: <175079060338.1874839.7157016701678665684.b4-ty@ti.com>
Date: Wed, 25 Jun 2025 00:14:08 +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>,
        Dhruva Gole
	<d-gole@...com>, Andrew Davis <afd@...com>,
        Michael Walle <mwalle@...nel.org>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62p-j722s: fix pinctrl-single size

Hi Michael Walle,

On Wed, 18 Jun 2025 08:52:39 +0200, Michael Walle wrote:
> Pinmux registers ends at 0x000f42ac (including). Thus, the size argument
> of the pinctrl-single node has to be 0x2b0. Fix it.
> 
> This will fix the following error:
> pinctrl-single f4000.pinctrl: mux offset out of range: 0x2ac (0x2ac)
> 
> 
> [...]

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

[1/1] arm64: dts: ti: k3-am62p-j722s: fix pinctrl-single size
      commit: fdc8ad019ab9a2308b8cef54fbc366f482fb746f

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