From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew@lunn.ch, linux@armlinux.org.uk, pabeni@redhat.com,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
andersson@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
vkoul@kernel.org, neil.armstrong@linaro.org,
netdev@vger.kernel.org, p.zabel@pengutronix.de,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v2 net-next 0/5] net: phy: further decouple provider from consumer part
Date: Sat, 14 Mar 2026 19:30:19 +0000 [thread overview]
Message-ID: <177351661903.1763199.2542451163758230122.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9d5724bc-e525-4f8f-b3f8-b16dd5a1164e@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Mar 2026 18:01:16 +0100 you wrote:
> This series aims at further decoupling the provider and consumer part
> in phylib.
>
> v2:
> - patch 2: add needed Kconfig dependency changes
> - patch 5: explain false positive checkpatch error
>
> [...]
Here is the summary with links:
- [v2,net-next,1/5] net: phy: move mdio_device reset handling functions in the code
https://git.kernel.org/netdev/net-next/c/2d7bebc9dd79
- [v2,net-next,2/5] net: phy: make mdio_device.c part of libphy
https://git.kernel.org/netdev/net-next/c/6df1459605ce
- [v2,net-next,3/5] net: phy: move (of_)mdio_find_bus to mdio_bus_provider.c
https://git.kernel.org/netdev/net-next/c/b69ceb387aca
- [v2,net-next,4/5] net: phy: move registering mdio_bus_class and mdio_bus_type to libphy
https://git.kernel.org/netdev/net-next/c/25b23d828318
- [v2,net-next,5/5] net: phy: move remaining provider code to mdio_bus_provider.c
https://git.kernel.org/netdev/net-next/c/c4399af5e556
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:[~2026-03-14 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 17:01 [PATCH v2 net-next 0/5] net: phy: further decouple provider from consumer part Heiner Kallweit
2026-03-09 17:02 ` [PATCH v2 net-next 1/5] net: phy: move mdio_device reset handling functions in the code Heiner Kallweit
2026-03-09 17:03 ` [PATCH v2 net-next 2/5] net: phy: make mdio_device.c part of libphy Heiner Kallweit
2026-03-12 11:06 ` Paolo Abeni
2026-03-09 17:04 ` [PATCH v2 net-next 3/5] net: phy: move (of_)mdio_find_bus to mdio_bus_provider.c Heiner Kallweit
2026-03-09 17:04 ` [PATCH v2 net-next 4/5] net: phy: move registering mdio_bus_class and mdio_bus_type to libphy Heiner Kallweit
2026-03-09 17:06 ` [PATCH v2 net-next 5/5] net: phy: move remaining provider code to mdio_bus_provider.c Heiner Kallweit
2026-03-14 19:30 ` 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=177351661903.1763199.2542451163758230122.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=sboyd@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