On Wed, May 14, 2025 at 02:17:26PM +0100, Vinod Koul wrote: > On 14-05-25, 15:02, Niklas Cassel wrote: > > Hello Vinod, Krzysztof, > > > > On Wed, May 14, 2025 at 12:38:01PM +0100, Vinod Koul wrote: > > > > > > On Thu, 08 May 2025 10:49:22 +0530, Vidya Sagar wrote: > > > > Replace ARCH_TEGRA_194_SOC dependency with a more generic ARCH_TEGRA > > > > check for the Tegra194 PCIe controller, allowing it to be built on > > > > Tegra platforms beyond Tegra194. Additionally, ensure compatibility > > > > by requiring ARM64 or COMPILE_TEST. > > > > > > > > > > > > > > Applied, thanks! > > > > > > [1/1] PCI: dwc: tegra194: Broaden architecture dependency > > > (no commit info) > > > [1/1] phy: tegra: p2u: Broaden architecture dependency > > > commit: 0c22287319741b4e7c7beaedac1f14fbe01a03b9 > > > > > > Best regards, > > > -- > > > > I see that Vinod has queued patch 1/2. > > > > Please don't forget that this series requires coordination. > > > > There are many ways to solve it. > > > > 1) One tree takes both patches. > > > > 2) PHY tree puts the PHY patch on an immutable branch with just that > > commit, and PCI merges that branch, so the same SHA1 of the PHY patch > > is in both trees. > > > > 3) Send PHY patch for the upcoming merge window. Send PCI patch for > > merge window + 1. > > 1, 3 works for me, for 2 pls let me know, I need to prep a branch with > this patch and tag on it... > Feel free to take the patch 1 through PHY tree with: Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx> I believe there should be no conflict with the PCI tree. - Mani -- மணிவண்ணன் சதாசிவம்
