From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
robh+dt@kernel.org, krzk+dt@kernel.org,
jerome.pouiller@silabs.com, 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 0/2] Extend dt-bindings for PSE-PD controllers and update prtt1c dts
Date: Fri, 02 Jun 2023 05:00:20 +0000 [thread overview]
Message-ID: <168568202061.24823.10947582942293943932.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230531102113.3353065-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 31 May 2023 12:21:11 +0200 you wrote:
> changes v3:
> - reword commit message for the pse-controller.yaml patch
> - drop podl-pse-regulator.yaml patch
>
> changes v2:
> - extend ethernet-pse regexp in the PoDL PSE dt-bindings
>
> [...]
Here is the summary with links:
- [v3,1/2] dt-bindings: net: pse-pd: Allow -N suffix for ethernet-pse node names
https://git.kernel.org/netdev/net-next/c/bd415f6c748e
- [v3,2/2] ARM: dts: stm32: prtt1c: Add PoDL PSE regulator nodes
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-02 5:00 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
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 ` patchwork-bot+netdevbpf [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=168568202061.24823.10947582942293943932.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.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