From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, Prathosh.Satish@microchip.com,
vadim.fedorenko@linux.dev, arkadiusz.kubalewski@intel.com,
jiri@resnulli.us, poros@redhat.com, mschmidt@redhat.com,
horms@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] dpll: zl3073x: refactor state management
Date: Wed, 18 Mar 2026 03:20:13 +0000 [thread overview]
Message-ID: <177380401316.109214.6390588576885603605.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260315174224.399074-1-ivecera@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 15 Mar 2026 18:42:18 +0100 you wrote:
> This series refactors the zl3073x DPLL driver to centralize hardware
> state management behind dedicated per-module state interfaces, replacing
> scattered direct register accesses in dpll.c with cached state and
> proper accessor functions.
>
> The driver already uses a fetch/get/set pattern for ref, out, and synth
> modules. This series extends and refines that pattern:
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] dpll: zl3073x: use struct_group to partition states
https://git.kernel.org/netdev/net-next/c/f327f5a8115e
- [net-next,v2,2/6] dpll: zl3073x: add zl3073x_ref_state_update helper
https://git.kernel.org/netdev/net-next/c/05ea2ab3b100
- [net-next,v2,3/6] dpll: zl3073x: introduce zl3073x_chan for DPLL channel state
https://git.kernel.org/netdev/net-next/c/3032e95987fa
- [net-next,v2,4/6] dpll: zl3073x: add DPLL channel status fields to zl3073x_chan
https://git.kernel.org/netdev/net-next/c/41bab554d7e9
- [net-next,v2,5/6] dpll: zl3073x: add reference priority to zl3073x_chan
https://git.kernel.org/netdev/net-next/c/f6b075bc3ad5
- [net-next,v2,6/6] dpll: zl3073x: drop selected and simplify connected ref getter
https://git.kernel.org/netdev/net-next/c/acee049a6af2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-03-18 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 17:42 [PATCH net-next v2 0/6] dpll: zl3073x: refactor state management Ivan Vecera
2026-03-15 17:42 ` [PATCH net-next v2 1/6] dpll: zl3073x: use struct_group to partition states Ivan Vecera
2026-03-15 17:42 ` [PATCH net-next v2 2/6] dpll: zl3073x: add zl3073x_ref_state_update helper Ivan Vecera
2026-03-15 17:42 ` [PATCH net-next v2 3/6] dpll: zl3073x: introduce zl3073x_chan for DPLL channel state Ivan Vecera
2026-03-15 17:42 ` [PATCH net-next v2 4/6] dpll: zl3073x: add DPLL channel status fields to zl3073x_chan Ivan Vecera
2026-03-15 17:42 ` [PATCH net-next v2 5/6] dpll: zl3073x: add reference priority " Ivan Vecera
2026-03-15 17:42 ` [PATCH net-next v2 6/6] dpll: zl3073x: drop selected and simplify connected ref getter Ivan Vecera
2026-03-18 3:20 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-11 18:12 [PATCH net-next v2 0/6] dpll: zl3073x: Refactor state management Ivan Vecera
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=177380401316.109214.6390588576885603605.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=poros@redhat.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