From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, arkadiusz.kubalewski@intel.com,
kuba@kernel.org, jiri@resnulli.us, min.li@microchip.com,
pabeni@redhat.com, poros@redhat.com, richardcochran@gmail.com,
vadim.fedorenko@linux.dev, linux-kernel@vger.kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] dpll: use pin owner's dpll ref for pin-level set callbacks
Date: Tue, 11 Aug 2026 09:40:08 +0000 [thread overview]
Message-ID: <178644120889.442634.3282180900336189180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807095926.386923-1-ivecera@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 7 Aug 2026 11:59:24 +0200 you wrote:
> Pin-level attributes (frequency, phase adjust, embedded sync, reference
> sync) are properties of the pin itself. The get callbacks already use
> only the pin owner's DPLL reference, but the set callbacks iterate over
> all registered DPLL devices, resulting in redundant HW writes for
> drivers that share a pin across multiple DPLLs.
>
> This series simplifies the set side to match the get side: call the set
> callback only through the owner's reference.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] dpll: zl3073x: update all DPLL channels on ref_sync_set
https://git.kernel.org/netdev/net-next/c/346630e46b38
- [net-next,v3,2/2] dpll: use pin owner's dpll ref for pin-level attribute setting
https://git.kernel.org/netdev/net-next/c/84e85c325e5e
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-08-11 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 9:59 [PATCH net-next v3 0/2] dpll: use pin owner's dpll ref for pin-level set callbacks Ivan Vecera
2026-08-07 9:59 ` [PATCH net-next v3 1/2] dpll: zl3073x: update all DPLL channels on ref_sync_set Ivan Vecera
2026-08-09 18:12 ` Ivan Vecera
2026-08-11 8:59 ` Petr Oros
2026-08-07 9:59 ` [PATCH net-next v3 2/2] dpll: use pin owner's dpll ref for pin-level attribute setting Ivan Vecera
2026-08-08 9:58 ` Jiri Pirko
2026-08-11 9: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=178644120889.442634.3282180900336189180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=richardcochran@gmail.com \
--cc=skhan@linuxfoundation.org \
--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