From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
Marek Vasut <marex@nabladev.com>,
linux-phy@lists.infradead.org
Cc: "Pankaj Dev" <pankaj.dev@st.com>,
"Rahul Kumar" <rahul.kumar05@st.com>,
"Clément Le Goffic" <clement.legoffic@foss.st.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Christian Bruel" <christian.bruel@foss.st.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Patrice Chotard" <patrice.chotard@foss.st.com>,
"Rob Herring" <robh@kernel.org>, "Rosen Penev" <rosenp@gmail.com>,
"Vinod Koul" <vkoul@kernel.org>,
devicetree@vger.kernel.org, kernel@dh-electronics.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v5 1/2] dt-bindings: phy: Document ST STM32MP25 USB2-FEMTO PHY
Date: Thu, 3 Sep 2026 12:41:33 +0200 [thread overview]
Message-ID: <36e58345-a236-4b77-b49b-961a0c439b5a@oss.qualcomm.com> (raw)
In-Reply-To: <34e63564-0191-406a-973a-eb601292b255@foss.st.com>
On 03/09/2026 12:19, Fabrice Gasnier wrote:
> On 9/2/26 16:13, Marek Vasut wrote:
>> From: Pankaj Dev <pankaj.dev@st.com>
>>
>> Document USB2 PHY for STM32MP25 USB2 controllers, which includes the
>> USB2.0 host-only controller and USB 2.0 part of the DWC3 controller.
>> Two such PHYs in total are present in STM32MP25 SoC, they both are
>> slightly different, therefore they use different compatible string
>> to discern them.
>
> Hello Marek,
>
> I'm not sure if/how this fit with all below tags. For all the
> contributions you've made, you can add my:
> Reviewed-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
> Tested-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
This does not apply. Otherwise explain me how to execute or interpret
this code on the device.
This is a series of two patches, so why can't you provide two replies so
the tags will be accurate?
Best regards,
Krzysztof
prev parent reply other threads:[~2026-09-03 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 14:13 [PATCH v5 1/2] dt-bindings: phy: Document ST STM32MP25 USB2-FEMTO PHY Marek Vasut
2026-09-02 14:13 ` [PATCH v5 2/2] phy: stm32: Add support for " Marek Vasut
2026-09-03 10:19 ` Fabrice Gasnier
2026-09-03 10:19 ` [PATCH v5 1/2] dt-bindings: phy: Document " Fabrice Gasnier
2026-09-03 10:41 ` Krzysztof Kozlowski [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=36e58345-a236-4b77-b49b-961a0c439b5a@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=christian.bruel@foss.st.com \
--cc=clement.legoffic@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mani@kernel.org \
--cc=marex@nabladev.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=pankaj.dev@st.com \
--cc=patrice.chotard@foss.st.com \
--cc=rahul.kumar05@st.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.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