From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christian Bruel <christian.bruel@foss.st.com>,
vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
p.zabel@pengutronix.de
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, fabrice.gasnier@foss.st.com
Subject: Re: [PATCH v3 0/5] Add STM32MP25 USB3/PCIE COMBOPHY driver
Date: Tue, 27 Aug 2024 15:23:56 +0200 [thread overview]
Message-ID: <2e634ee8-7622-4eb8-ba5b-0d218bb092eb@kernel.org> (raw)
In-Reply-To: <20240827122459.1102889-1-christian.bruel@foss.st.com>
On 27/08/2024 14:24, Christian Bruel wrote:
> This patch series adds USB3/PCIE COMBOPHY driver for the STM32MP25 SoC from
> STMicrolectronics, respective yaml schema and enable for the stm32mp257f-ev1
> device into which it is used for PCIe.
>
> Changes in v3:
> Address comments from Rob and Krzysztof:
> - Reorder MAINTAINERS patch
> - Drop wakeup-source from bindings (should be generic)
Where? Point me to the exact line being dropped.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-08-27 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 12:24 [PATCH v3 0/5] Add STM32MP25 USB3/PCIE COMBOPHY driver Christian Bruel
2024-08-27 12:24 ` [PATCH 1/5] dt-bindings: phy: Add STM32MP25 COMBOPHY bindings Christian Bruel
2024-08-27 13:23 ` Krzysztof Kozlowski
2024-08-28 8:16 ` Christian Bruel
2024-08-27 12:24 ` [PATCH 2/5] phy: stm32: Add support for STM32MP25 COMBOPHY Christian Bruel
2024-08-27 12:24 ` [PATCH 3/5] MAINTAINERS: add entry for ST STM32MP25 COMBOPHY driver Christian Bruel
2024-08-27 12:24 ` [PATCH 4/5] arm64: dts: st: Add combophy node on stm32mp251 Christian Bruel
2024-08-27 12:24 ` [PATCH 5/5] arm64: dts: st: Enable COMBOPHY on the stm32mp257f-ev1 board Christian Bruel
2024-08-27 13:23 ` 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=2e634ee8-7622-4eb8-ba5b-0d218bb092eb@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=christian.bruel@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=kishon@kernel.org \
--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=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--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