From: Niklas Cassel <cassel@kernel.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: vkoul@kernel.org, kishon@kernel.org,
manivannan.sadhasivam@linaro.org, bhelgaas@google.com,
linux-phy@lists.infradead.org, linux-tegra@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] phy: tegra: p2u: Broaden architecture dependency
Date: Thu, 8 May 2025 14:17:43 +0200 [thread overview]
Message-ID: <aByg58pvj3onDveF@ryzen> (raw)
In-Reply-To: <20250508052021.4135874-1-vidyas@nvidia.com>
On Thu, May 08, 2025 at 10:50:21AM +0530, Vidya Sagar wrote:
> Replace the ARCH_TEGRA_194_SOC || ARCH_TEGRA_234_SOC dependency with a
> more generic ARCH_TEGRA check for the Tegra194 PIPE2UPHY PHY driver.
> This allows the PHY driver to be built on all Tegra platforms instead
> of being limited to specific SoCs.
>
> 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: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250417074607.2281010-1-vidyas@nvidia.com>
2025-05-08 5:20 ` [PATCH V4] phy: tegra: p2u: Broaden architecture dependency Vidya Sagar
2025-05-08 12:17 ` Niklas Cassel [this message]
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=aByg58pvj3onDveF@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mmaddireddy@nvidia.com \
--cc=sagar.tv@gmail.com \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.com \
--cc=vkoul@kernel.org \
/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