From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, min.li@microchip.com,
vadim.fedorenko@linux.dev, arkadiusz.kubalewski@intel.com,
jiri@resnulli.us, kuba@kernel.org, Prathosh.Satish@microchip.com,
pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5 0/5] dpll: zl3073x: fix output pin frequency, esync and sibling notifications
Date: Sat, 17 Oct 2026 01:10:05 +0000 [thread overview]
Message-ID: <179219940577.1041032.9554002490347498296.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011061211.448373-1-ivecera@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 08:12:06 +0200 you wrote:
> This series fixes several issues in the zl3073x output pin handling:
>
> 1. Do not offer 0 Hz as a supported frequency, it leads to a division
> by zero.
> 2. Reject N-divided output frequencies that cannot be set exactly.
> 3. Reject output frequencies whose divisor is too small for the HW.
> 4. Update the eSync period and width when the output frequency changes.
> 5. Notify the sibling pin when a shared output setting changes.
>
> [...]
Here is the summary with links:
- [net,v5,1/5] dpll: zl3073x: do not offer 0 Hz as a supported pin frequency
https://git.kernel.org/netdev/net-next/c/23171065fb43
- [net,v5,2/5] dpll: zl3073x: reject inexact frequencies for N-divided outputs
https://git.kernel.org/netdev/net-next/c/f8993627d310
- [net,v5,3/5] dpll: zl3073x: reject output frequencies with too small divisor
https://git.kernel.org/netdev/net-next/c/456027325c9c
- [net,v5,4/5] dpll: zl3073x: make embedded sync follow the output carrier frequency
https://git.kernel.org/netdev/net-next/c/bf6f105f2cb6
- [net,v5,5/5] dpll: zl3073x: notify sibling pin when shared output config changes
https://git.kernel.org/netdev/net-next/c/0748e473b65a
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-10-17 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 6:12 Ivan Vecera
2026-10-11 6:12 ` [PATCH net v5 1/5] dpll: zl3073x: do not offer 0 Hz as a supported pin frequency Ivan Vecera
2026-10-12 6:13 ` netdev-bot+sashiko
2026-10-12 7:14 ` Ivan Vecera
2026-10-17 1:02 ` Jakub Kicinski
2026-10-11 6:12 ` [PATCH net v5 2/5] dpll: zl3073x: reject inexact frequencies for N-divided outputs Ivan Vecera
2026-10-12 6:13 ` netdev-bot+sashiko
2026-10-12 7:16 ` Ivan Vecera
2026-10-11 6:12 ` [PATCH net v5 3/5] dpll: zl3073x: reject output frequencies with too small divisor Ivan Vecera
2026-10-12 6:13 ` netdev-bot+sashiko
2026-10-12 7:56 ` Ivan Vecera
2026-10-11 6:12 ` [PATCH net v5 4/5] dpll: zl3073x: make embedded sync follow the output carrier frequency Ivan Vecera
2026-10-11 6:12 ` [PATCH net v5 5/5] dpll: zl3073x: notify sibling pin when shared output config changes Ivan Vecera
2026-10-12 6:13 ` netdev-bot+sashiko
2026-10-12 7:59 ` Ivan Vecera
2026-10-17 1: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=179219940577.1041032.9554002490347498296.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=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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
all inboxes | Powered by JetHome®