From: patchwork-bot+netdevbpf@kernel.org
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
vadim.fedorenko@linux.dev, jiri@resnulli.us,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, aleksandr.loktionov@intel.com,
corbet@lwn.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/3] dpll: add Reference SYNC feature
Date: Fri, 27 Jun 2025 23:50:10 +0000 [thread overview]
Message-ID: <175106821026.2091805.3166945763972558199.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250626135219.1769350-1-arkadiusz.kubalewski@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Jun 2025 15:52:16 +0200 you wrote:
> The device may support the Reference SYNC feature, which allows the
> combination of two inputs into a input pair. In this configuration,
> clock signals from both inputs are used to synchronize the DPLL device.
> The higher frequency signal is utilized for the loop bandwidth of the DPLL,
> while the lower frequency signal is used to syntonize the output signal of
> the DPLL device. This feature enables the provision of a high-quality loop
> bandwidth signal from an external source.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/3] dpll: add reference-sync netlink attribute
https://git.kernel.org/netdev/net-next/c/7f15ee35972d
- [net-next,v7,2/3] dpll: add reference sync get/set
https://git.kernel.org/netdev/net-next/c/58256a26bfb3
- [net-next,v7,3/3] ice: add ref-sync dpll pins
https://git.kernel.org/netdev/net-next/c/5bcea241335b
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:[~2025-06-27 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 13:52 [PATCH net-next v7 0/3] dpll: add Reference SYNC feature Arkadiusz Kubalewski
2025-06-26 13:52 ` [PATCH net-next v7 1/3] dpll: add reference-sync netlink attribute Arkadiusz Kubalewski
2025-06-26 13:52 ` [PATCH net-next v7 2/3] dpll: add reference sync get/set Arkadiusz Kubalewski
2025-06-26 13:52 ` [PATCH net-next v7 3/3] ice: add ref-sync dpll pins Arkadiusz Kubalewski
2025-06-27 23:40 ` [PATCH net-next v7 0/3] dpll: add Reference SYNC feature Jakub Kicinski
2025-06-27 23:50 ` 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=175106821026.2091805.3166945763972558199.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).