public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: lpieralisi@kernel.org, kw@linux.com,
	manivannan.sadhasivam@linaro.org, robh@kernel.org,
	bhelgaas@google.com, Vidya Sagar <vidyas@nvidia.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	treding@nvidia.com, jonathanh@nvidia.com, kthota@nvidia.com,
	mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V4] PCI: dwc: tegra194: Broaden architecture dependency
Date: Wed, 14 May 2025 14:17:26 +0100	[thread overview]
Message-ID: <aCSX5gKsehupIC35@vaman> (raw)
In-Reply-To: <aCSUfiwnZRTgMKGT@ryzen>

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

  reply	other threads:[~2025-05-14 13:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  7:46 [PATCH V3] PCI: dwc: tegra194: Broaden architecture dependency Vidya Sagar
2025-04-17  7:51 ` Niklas Cassel
2025-04-18 11:18   ` Vinod Koul
2025-04-18 17:21 ` Manivannan Sadhasivam
2025-05-05  6:47   ` Vidya Sagar
     [not found]   ` <SN7PR12MB8028F87148D1B635F832EEB9B88E2@SN7PR12MB8028.namprd12.prod.outlook.com>
2025-05-05  8:24     ` Manivannan Sadhasivam
2025-05-08  5:19 ` [PATCH V4] " Vidya Sagar
2025-05-08 12:17   ` Niklas Cassel
2025-05-08 12:51     ` Thierry Reding
2025-05-08 13:22       ` Krzysztof Wilczyński
2025-05-08 13:20   ` Krzysztof Wilczyński
2025-05-14 11:38   ` Vinod Koul
2025-05-14 13:02     ` Niklas Cassel
2025-05-14 13:17       ` Vinod Koul [this message]
2025-05-15 11:33         ` Manivannan Sadhasivam
2026-01-05 12:20   ` Manivannan Sadhasivam
2025-05-08  5:20 ` [PATCH V4] phy: tegra: p2u: " Vidya Sagar
2025-05-08 12:17   ` Niklas Cassel
2025-05-08 12:51   ` Thierry Reding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aCSX5gKsehupIC35@vaman \
    --to=vkoul@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kthota@nvidia.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=treding@nvidia.com \
    --cc=vidyas@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox