From: Niklas Cassel <cassel@kernel.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
bhelgaas@google.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: Thu, 8 May 2025 14:17:24 +0200 [thread overview]
Message-ID: <aByg1GUBno3Gzf4w@ryzen> (raw)
In-Reply-To: <20250508051922.4134041-1-vidyas@nvidia.com>
On Thu, May 08, 2025 at 10:49:22AM +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.
>
> Link: https://patchwork.kernel.org/project/linux-pci/patch/20250128044244.2766334-1-vidyas@nvidia.com/
> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> ---
Looks good to me, but there will need coordination between the
PHY and PCI maintainers for this to not cause a kernel test bot
build failure, if the PCI patch is merged before the PHY patch.
Reviewed-by: Niklas Cassel <cassel@kernel.org>
next prev parent reply other threads:[~2025-05-08 12:17 UTC|newest]
Thread overview: 16+ 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 [this message]
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
2025-05-15 11:33 ` Manivannan Sadhasivam
2026-01-05 12:20 ` Manivannan Sadhasivam
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=aByg1GUBno3Gzf4w@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--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