linux-kernel - Re: [PATCH v2 0/3] arm64: dts: ti: k3-am62p/j722s: Fix gpio-ranges

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: <172294634855.366372.6539527201402606616.b4-ty@ti.com>
Date: Tue, 6 Aug 2024 07:12:34 -0500
From: Nishanth Menon <nm@...com>
To: Conor Dooley <conor+dt@...nel.org>,
        Krzysztof Kozlowski
	<krzk+dt@...nel.org>,
        Rob Herring <robh@...nel.org>, Jared McArthur
	<j-mcarthur@...com>
CC: Nishanth Menon <nm@...com>, <linux-kernel@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        Tero
 Kristo <kristo@...nel.org>,
        Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [PATCH v2 0/3] arm64: dts: ti: k3-am62p/j722s: Fix gpio-ranges

Hi Jared McArthur,

On Thu, 01 Aug 2024 16:04:11 -0500, Jared McArthur wrote:
> Fixes issues within the am62p and j722s gpio-ranges. Adds the missing
> holes within the ranges as well as the the missing gpio-ranges
> property within the mcu_gpio0 node of the am62p.
> 
> v2 changes: Removes the duplicate ti,ngpio property from the mcu_gpio0
> node of the k3-am62p-j722s-common-mcu.dtsi.
> 
> [...]

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

[1/3] arm64: dts: ti: k3-am62p: Add gpio-ranges for mcu_gpio0
      commit: 4e436f6fb95e507131df78c0d98052237db60ecc
[2/3] arm64: dts: ti: k3-am62p: Fix gpio-range for main_pmx0
      commit: 98897a300859dca62f834a5d1f60267032a9fe54
[3/3] arm64: dts: ti: k3-j722s: Fix gpio-range for main_pmx0
      commit: 04c90681144c40619524367c69e40736a6fa690c

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D