From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, poros@redhat.com, dsahern@kernel.org,
stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next v3 0/2] dpll: phase unit display and frequency monitoring
Date: Thu, 07 May 2026 15:30:11 +0000 [thread overview]
Message-ID: <177816781160.4040424.13608923962799018672.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260504163014.416317-1-ivecera@redhat.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 4 May 2026 18:30:12 +0200 you wrote:
> This series improves dpll pin output formatting and adds support for
> the frequency monitoring feature.
>
> Patch 1 adds picosecond unit to phase-adjust-min, phase-adjust-max
> and phase-adjust attributes. It also introduces dpll_pr_phase_offset()
> helper that properly formats phase-offset as fractional picoseconds by
> dividing the raw kernel value by DPLL_PHASE_OFFSET_DIVIDER.
>
> [...]
Here is the summary with links:
- [iproute2-next,v3,1/2] dpll: add ps unit to phase-related pin attributes
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=410888eea295
- [iproute2-next,v3,2/2] dpll: add frequency monitoring support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=12954bc7d2c3
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-05-07 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 16:30 [PATCH iproute2-next v3 0/2] dpll: phase unit display and frequency monitoring Ivan Vecera
2026-05-04 16:30 ` [PATCH iproute2-next v3 1/2] dpll: add ps unit to phase-related pin attributes Ivan Vecera
2026-05-04 16:30 ` [PATCH iproute2-next v3 2/2] dpll: add frequency monitoring support Ivan Vecera
2026-05-07 15: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=177816781160.4040424.13608923962799018672.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=ivecera@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=poros@redhat.com \
--cc=stephen@networkplumber.org \
/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