linux-kernel - Re: [PATCH V4] PCI: dwc: tegra194: Broaden architecture dependency

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aCSX5gKsehupIC35@vaman>
Date: Wed, 14 May 2025 14:17:26 +0100
From: Vinod Koul <vkoul@...nel.org>
To: Niklas Cassel <cassel@...nel.org>
Cc: lpieralisi@...nel.org, kw@...ux.com, manivannan.sadhasivam@...aro.org,
	robh@...nel.org, bhelgaas@...gle.com,
	Vidya Sagar <vidyas@...dia.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, treding@...dia.com,
	jonathanh@...dia.com, kthota@...dia.com, mmaddireddy@...dia.com,
	sagar.tv@...il.com
Subject: Re: [PATCH V4] PCI: dwc: tegra194: Broaden architecture dependency

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...

BR

-- 
~Vinod