From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: linux@armlinux.org.uk, andrew@lunn.ch, andrew+netdev@lunn.ch,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, olteanv@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: remove mdio_board_info support from phylib
Date: Wed, 17 Sep 2025 22:40:08 +0000 [thread overview]
Message-ID: <175814880825.2172991.6411163169375469216.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4ccf7476-0744-4f6b-aafc-7ba84d15a432@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 13 Sep 2025 23:05:15 +0200 you wrote:
> Since its introduction in 2017 mdio_board_info has had only two users:
> - dsa_loop (still existing)
> - arm orion, added in 2017 and removed with fd68572b57f2 ("ARM: orion5x:
> remove dsa_chip_data references")
>
> So let's remove usage of mdio_board_info from dsa_loop, then support
> for mdio_board_info can be dropped from phylib.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dsa: dsa_loop: remove usage of mdio_board_info
https://git.kernel.org/netdev/net-next/c/41357bc7b94b
- [net-next,2/2] net: phy: remove mdio_board_info support from phylib
https://git.kernel.org/netdev/net-next/c/b67a8631a4a8
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:[~2025-09-17 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 21:05 [PATCH net-next 0/2] net: phy: remove mdio_board_info support from phylib Heiner Kallweit
2025-09-13 21:07 ` [PATCH net-next 1/2] net: dsa: dsa_loop: remove usage of mdio_board_info Heiner Kallweit
2025-09-17 7:40 ` Vladimir Oltean
2025-09-13 21:08 ` [PATCH net-next 2/2] net: phy: remove mdio_board_info support from phylib Heiner Kallweit
2025-09-17 22:40 ` 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=175814880825.2172991.6411163169375469216.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.