From: Jon Hunter <jonathanh@nvidia.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
JC Kuo <jckuo@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Wayne Chang <waynec@nvidia.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/3] phy: tegra: xusb: Add Tegra238 support
Date: Wed, 7 Oct 2026 15:46:54 +0100 [thread overview]
Message-ID: <d2ce164d-3481-41f0-97fe-9d6b21e59ade@nvidia.com> (raw)
In-Reply-To: <asERwJjj3eUMm8Kd@parshuram>
On 03/10/2026 15:31, Vinod Koul wrote:
> On 01-10-26, 14:28, Jon Hunter wrote:
>> Add support for the Tegra238 device to the Tegra XUSB PHY driver and
>> add the necessary device-tree binding documentation for this device.
>>
>> This series also includes a trivial clean-up patch to use the
>> dev_err_probe() function in the Tegra XUSB PHY driver instead of open
>> coding this function.
>>
>> This series is based on top of the series that adds support for the
>> Tegra264 device to the Tegra XUSB PHY driver [0].
>>
>> [0] https://lore.kernel.org/linux-tegra/20260903071937.533646-1-waynec@nvidia.com/
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> Changes in v2:
>> - Dropped extra 'err' variable from patch that migrates to dev_err_probe
>> - Added Krzysztof's Reviewed-by for device-tree binding.
>> - Link to v1: https://patch.msgid.link/20260921-tegra-phy-v1-0-83466bf9a7cd@nvidia.com
>>
>> ---
>> Jon Hunter (3):
>> dt-bindings: phy: tegra194: Add compatible for Tegra238
>
> Somehow this fails to apply on the current code, can you please rebase
> and also check the sashiko issues reported
It should apply fine if using b4. I heard that sashiko was recently updated
to fix this. I have fixed the issue reported by sashiko and sent a V3. This
should now apply fine because you have already queued the dependent series
and that is now in -next.
Jon
--
nvpublic
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-10-07 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:28 [PATCH v2 0/3] phy: tegra: xusb: Add Tegra238 support Jon Hunter
2026-10-01 13:28 ` [PATCH v2 1/3] dt-bindings: phy: tegra194: Add compatible for Tegra238 Jon Hunter
2026-10-01 13:28 ` [PATCH v2 2/3] phy: tegra: xusb: Use dev_err_probe() Jon Hunter
2026-10-01 13:28 ` [PATCH v2 3/3] phy: tegra: Add support for Tegra238 XUSB pad controller Jon Hunter
2026-10-01 13:38 ` sashiko-bot
2026-10-03 14:31 ` [PATCH v2 0/3] phy: tegra: xusb: Add Tegra238 support Vinod Koul
2026-10-07 14:46 ` Jon Hunter [this message]
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=d2ce164d-3481-41f0-97fe-9d6b21e59ade@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jckuo@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@kernel.org \
--cc=vkoul@kernel.org \
--cc=waynec@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