From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, aleksander.lobakin@intel.com,
andrew+netdev@lunn.ch, arkadiusz.kubalewski@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
jiri@resnulli.us, jonathan.lemon@gmail.com, leon@kernel.org,
mbloch@nvidia.com, pabeni@redhat.com,
Prathosh.Satish@microchip.com, przemyslaw.kitszel@intel.com,
richardcochran@gmail.com, saeedm@nvidia.com, tariqt@nvidia.com,
anthony.l.nguyen@intel.com, vadim.fedorenko@linux.dev,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/9] dpll: Core improvements and ice E825-C SyncE support
Date: Thu, 05 Feb 2026 15:10:17 +0000 [thread overview]
Message-ID: <177030421708.447604.18321209785815350003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203174002.705176-1-ivecera@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 3 Feb 2026 18:39:53 +0100 you wrote:
> This series introduces Synchronous Ethernet (SyncE) support for the Intel
> E825-C Ethernet controller. Unlike previous generations where DPLL
> connections were implicitly assumed, the E825-C architecture relies
> on the platform firmware (ACPI) to describe the physical connections
> between the Ethernet controller and external DPLLs (such as the ZL3073x).
>
> To accommodate this, the series extends the DPLL subsystem to support
> firmware node (fwnode) associations, asynchronous discovery via notifiers,
> and dynamic pin management. Additionally, a significant refactor of
> the DPLL reference counting logic is included to ensure robustness and
> debuggability.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/9] dpll: Allow associating dpll pin with a firmware node
https://git.kernel.org/netdev/net-next/c/d0f4771e2bef
- [net-next,v5,2/9] dpll: zl3073x: Associate pin with fwnode handle
https://git.kernel.org/netdev/net-next/c/e6dc7727b608
- [net-next,v5,3/9] dpll: Add notifier chain for dpll events
https://git.kernel.org/netdev/net-next/c/2be467588d6b
- [net-next,v5,4/9] dpll: Support dynamic pin index allocation
https://git.kernel.org/netdev/net-next/c/711696b3e168
- [net-next,v5,5/9] dpll: zl3073x: Add support for mux pin type
https://git.kernel.org/netdev/net-next/c/fdad05ed4ec2
- [net-next,v5,6/9] dpll: Enhance and consolidate reference counting logic
https://git.kernel.org/netdev/net-next/c/729f5e0153bd
- [net-next,v5,7/9] dpll: Add reference count tracking support
https://git.kernel.org/netdev/net-next/c/3c0da1030c58
- [net-next,v5,8/9] drivers: Add support for DPLL reference count tracking
https://git.kernel.org/netdev/net-next/c/085ca5d20171
- [net-next,v5,9/9] ice: dpll: Support E825-C SyncE and dynamic pin discovery
https://git.kernel.org/netdev/net-next/c/ad1df4f2d591
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-02-05 15:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:39 [PATCH net-next v5 0/9] dpll: Core improvements and ice E825-C SyncE support Ivan Vecera
2026-02-03 17:39 ` [PATCH net-next v5 1/9] dpll: Allow associating dpll pin with a firmware node Ivan Vecera
2026-02-05 9:05 ` Kubalewski, Arkadiusz
2026-02-03 17:39 ` [PATCH net-next v5 2/9] dpll: zl3073x: Associate pin with fwnode handle Ivan Vecera
2026-02-05 9:19 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-02-03 17:39 ` [PATCH net-next v5 3/9] dpll: Add notifier chain for dpll events Ivan Vecera
2026-02-05 9:19 ` Kubalewski, Arkadiusz
2026-02-05 10:17 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-02-03 17:39 ` [PATCH net-next v5 4/9] dpll: Support dynamic pin index allocation Ivan Vecera
2026-02-05 9:01 ` Kubalewski, Arkadiusz
2026-02-03 17:39 ` [PATCH net-next v5 5/9] dpll: zl3073x: Add support for mux pin type Ivan Vecera
2026-02-05 9:01 ` Kubalewski, Arkadiusz
2026-02-03 17:39 ` [PATCH net-next v5 6/9] dpll: Enhance and consolidate reference counting logic Ivan Vecera
2026-02-05 8:58 ` Kubalewski, Arkadiusz
2026-02-03 17:40 ` [PATCH net-next v5 7/9] dpll: Add reference count tracking support Ivan Vecera
2026-02-05 8:58 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-02-03 17:40 ` [PATCH net-next v5 8/9] drivers: Add support for DPLL reference count tracking Ivan Vecera
2026-02-05 8:58 ` Kubalewski, Arkadiusz
2026-02-03 17:40 ` [PATCH net-next v5 9/9] ice: dpll: Support E825-C SyncE and dynamic pin discovery Ivan Vecera
2026-02-05 15: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=177030421708.447604.18321209785815350003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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