The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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, mschmidt@redhat.com, poros@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/6] dpll: zl3073x: Refactor state management
Date: Tue, 18 Nov 2025 04:30:26 +0000	[thread overview]
Message-ID: <176344022699.3968687.11755986970582847257.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251113074105.141379-1-ivecera@redhat.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 13 Nov 2025 08:40:59 +0100 you wrote:
> This patch set is a refactoring of the zl3073x driver to clean up
> state management, improve modularity, and significantly reduce
> on-demand I/O.
> 
> The driver's dpll.c implementation previously performed on-demand
> register reads and writes (wrapped in mailbox operations) to get
> or set properties like frequency, phase, and embedded-sync settings.
> This cluttered the DPLL logic with low-level I/O, duplicated locking,
> and led to inefficient bus traffic.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/6] dpll: zl3073x: Store raw register values instead of parsed state
    https://git.kernel.org/netdev/net-next/c/58fb88d30b02
  - [net-next,v3,2/6] dpll: zl3073x: Split ref, out, and synth logic from core
    https://git.kernel.org/netdev/net-next/c/607f2c00c61f
  - [net-next,v3,3/6] dpll: zl3073x: Cache reference monitor status
    https://git.kernel.org/netdev/net-next/c/5534a8202d7c
  - [net-next,v3,4/6] dpll: zl3073x: Cache all reference properties in zl3073x_ref
    https://git.kernel.org/netdev/net-next/c/5bc02b190a3f
  - [net-next,v3,5/6] dpll: zl3073x: Cache all output properties in zl3073x_out
    https://git.kernel.org/netdev/net-next/c/5fb9b0d411f8
  - [net-next,v3,6/6] dpll: zl3073x: Remove unused dev wrappers
    https://git.kernel.org/netdev/net-next/c/01e0e8b6a2d7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-18  4:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  7:40 [PATCH net-next v3 0/6] dpll: zl3073x: Refactor state management Ivan Vecera
2025-11-13  7:41 ` [PATCH net-next v3 1/6] dpll: zl3073x: Store raw register values instead of parsed state Ivan Vecera
2025-11-13  7:41 ` [PATCH net-next v3 2/6] dpll: zl3073x: Split ref, out, and synth logic from core Ivan Vecera
2025-11-13  7:41 ` [PATCH net-next v3 3/6] dpll: zl3073x: Cache reference monitor status Ivan Vecera
2025-11-13  7:41 ` [PATCH net-next v3 4/6] dpll: zl3073x: Cache all reference properties in zl3073x_ref Ivan Vecera
2025-11-13  7:41 ` [PATCH net-next v3 5/6] dpll: zl3073x: Cache all output properties in zl3073x_out Ivan Vecera
2025-11-13  7:41 ` [PATCH net-next v3 6/6] dpll: zl3073x: Remove unused dev wrappers Ivan Vecera
2025-11-18  4: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=176344022699.3968687.11755986970582847257.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Prathosh.Satish@microchip.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --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