From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Oleksij Rempel" <o.rempel@pengutronix.de>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: net: pse-pd: Allow -N suffix for ethernet-pse node names
Date: Thu, 1 Jun 2023 19:34:18 +0200 [thread overview]
Message-ID: <d74a4aea-7e8c-cde7-0293-2c3a41997e41@linaro.org> (raw)
In-Reply-To: <20230531102113.3353065-2-o.rempel@pengutronix.de>
On 31/05/2023 12:21, Oleksij Rempel wrote:
> Extend the pattern matching for PSE-PD controller nodes to allow -N
> suffixes. This enables the use of multiple "ethernet-pse" nodes without the
> need for a "reg" property.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-01 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 10:21 [PATCH v3 0/2] Extend dt-bindings for PSE-PD controllers and update prtt1c dts Oleksij Rempel
2023-05-31 10:21 ` [PATCH v3 1/2] dt-bindings: net: pse-pd: Allow -N suffix for ethernet-pse node names Oleksij Rempel
2023-06-01 17:34 ` Krzysztof Kozlowski [this message]
2023-05-31 10:21 ` [PATCH v3 2/2] ARM: dts: stm32: prtt1c: Add PoDL PSE regulator nodes Oleksij Rempel
2023-06-02 5:00 ` [PATCH v3 0/2] Extend dt-bindings for PSE-PD controllers and update prtt1c dts patchwork-bot+netdevbpf
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=d74a4aea-7e8c-cde7-0293-2c3a41997e41@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=jerome.pouiller@silabs.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).