From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew+netdev@lunn.ch, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, andrew@lunn.ch,
linux@armlinux.org.uk, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next 0/3] net: phy: make phy_package a separate module
Date: Mon, 16 Jun 2025 22:10:40 +0000 [thread overview]
Message-ID: <175011184073.2530350.6087096152984005228.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <eec346a4-e903-48af-8150-0191932a7a0b@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Jun 2025 23:25:00 +0200 you wrote:
> Only a handful of PHY drivers needs the PHY package functionality,
> therefore make it a separate module which is built only if needed.
>
> Heiner Kallweit (3):
> net: phy: move __phy_package_[read|write]_mmd to phy_package.c
> net: phy: make phy_package a separate module
> net: phy: add Kconfig symbol PHY_PACKAGE
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: phy: move __phy_package_[read|write]_mmd to phy_package.c
https://git.kernel.org/netdev/net-next/c/cbd1ab0ce8f6
- [net-next,2/3] net: phy: make phy_package a separate module
https://git.kernel.org/netdev/net-next/c/a1acde1e1bcf
- [net-next,3/3] net: phy: add Kconfig symbol PHY_PACKAGE
https://git.kernel.org/netdev/net-next/c/7d57386905d4
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-06-16 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 21:25 [PATCH net-next 0/3] net: phy: make phy_package a separate module Heiner Kallweit
2025-06-12 21:26 ` [PATCH net-next 1/3] net: phy: move __phy_package_[read|write]_mmd to phy_package.c Heiner Kallweit
2025-06-12 21:26 ` [PATCH net-next 2/3] net: phy: make phy_package a separate module Heiner Kallweit
2025-06-12 21:28 ` [PATCH net-next 3/3] net: phy: add Kconfig symbol PHY_PACKAGE Heiner Kallweit
2025-06-16 22:10 ` 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=175011184073.2530350.6087096152984005228.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--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.