linux-kernel - Re: [PATCH v3 0/2] J784S4/J742S2: Enable ACSPCIE0 output for PCIe1

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: <174619706058.3123134.8004461889197725220.b4-ty@ti.com>
Date: Fri, 2 May 2025 09:44:30 -0500
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>, <u-kumar1@...com>,
        <parth105105@...il.com>, <parth.pancholi@...adex.com>,
        Siddharth Vadapalli
	<s-vadapalli@...com>
CC: Nishanth Menon <nm@...com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <srk@...com>
Subject: Re: [PATCH v3 0/2] J784S4/J742S2: Enable ACSPCIE0 output for PCIe1

Hi Siddharth Vadapalli,

On Tue, 22 Apr 2025 18:02:16 +0530, Siddharth Vadapalli wrote:
> This series enables the reference clock output from the ACSPCIE0 module
> to the PCIe Connector corresponding to the PCIe1 instance of PCIe on
> J784S4-EVM and J742S2-EVM.
> 
> Series is based on linux-next tagged next-20250417.
> 
> The previous versions of this series were a single patch. Based on the
> feedback received on previous versions, the SoC and Board support has
> been split in order to allow reuse for other Boards based on the same
> SoC.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j784s4-j742s2-main-common: add ACSPCIE0 node
      commit: 9bfebd8750a06f5f8bf16ac58eb7deb638686d07
[2/2] arm64: dts: ti: k3-j784s4-j742s2-evm-common: enable ACSPCIE0 output for PCIe1
      commit: e3dfcf482d0787a5882f10a33daa4c1ec62b87d2

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