linux-kernel - Re: [PATCH 0/2] arm64: dts: ti: k3-j784s4-evm: SERDES0 lane cleanup

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <173012710985.558239.2190537617884915440.b4-ty@ti.com>
Date: Mon, 28 Oct 2024 20:35:21 +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>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        "Siddharth
 Vadapalli" <s-vadapalli@...com>, <mranostay@...com>,
        Andrew Halaney
	<ahalaney@...hat.com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] arm64: dts: ti: k3-j784s4-evm: SERDES0 lane cleanup

Hi Andrew Halaney,

On Wed, 10 Jul 2024 10:36:12 -0500, Andrew Halaney wrote:
> This fixes a splat caused due to overlapping lane usage of SERDES0 by
> PCIe1 and USB0. It also cleans up the dts a hair to be more readable.
> 
> 

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

[1/2] arm64: dts: ti: k3-j784s4-evm: Assign only lanes 0 and 1 to PCIe1
      commit: 84f78178b6fe37b5eb8b90b5bb1239abce0b64d8
[2/2] arm64: dts: ti: k3-j784s4-evm: Consolidate serdes0 references
      commit: cc5049007d722364bca4a4eeb619d5629733a004

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