From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: donald.hunter@gmail.com, 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,
Milena Olech <milena.olech@intel.com>,
Jiri Pirko <jiri@nvidia.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v5 1/3] dpll: add reference-sync netlink attribute
Date: Wed, 11 Jun 2025 16:54:15 -0700 [thread overview]
Message-ID: <20250611165415.3c9ed314@kernel.org> (raw)
In-Reply-To: <20250610040436.1669826-2-arkadiusz.kubalewski@intel.com>
On Tue, 10 Jun 2025 06:04:34 +0200 Arkadiusz Kubalewski 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
^^^^
DPLL ?
> +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.
Looks like there is a conflict between this series and patches sent
by Tony the day before. You'll have to rebase.
--
pw-bot: cr
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: donald.hunter@gmail.com, 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,
Milena Olech <milena.olech@intel.com>,
Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next v5 1/3] dpll: add reference-sync netlink attribute
Date: Wed, 11 Jun 2025 16:54:15 -0700 [thread overview]
Message-ID: <20250611165415.3c9ed314@kernel.org> (raw)
In-Reply-To: <20250610040436.1669826-2-arkadiusz.kubalewski@intel.com>
On Tue, 10 Jun 2025 06:04:34 +0200 Arkadiusz Kubalewski 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
^^^^
DPLL ?
> +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.
Looks like there is a conflict between this series and patches sent
by Tony the day before. You'll have to rebase.
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-11 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 4:04 [Intel-wired-lan] [PATCH net-next v5 0/3] dpll: add Reference SYNC feature Arkadiusz Kubalewski
2025-06-10 4:04 ` Arkadiusz Kubalewski
2025-06-10 4:04 ` [Intel-wired-lan] [PATCH net-next v5 1/3] dpll: add reference-sync netlink attribute Arkadiusz Kubalewski
2025-06-10 4:04 ` Arkadiusz Kubalewski
2025-06-11 23:54 ` Jakub Kicinski [this message]
2025-06-11 23:54 ` Jakub Kicinski
2025-06-13 20:16 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2025-06-13 20:16 ` Kubalewski, Arkadiusz
2025-06-10 4:04 ` [Intel-wired-lan] [PATCH net-next v5 2/3] dpll: add reference sync get/set Arkadiusz Kubalewski
2025-06-10 4:04 ` Arkadiusz Kubalewski
2025-06-10 4:04 ` [Intel-wired-lan] [PATCH net-next v5 3/3] ice: add ref-sync dpll pins Arkadiusz Kubalewski
2025-06-10 4:04 ` Arkadiusz Kubalewski
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=20250611165415.3c9ed314@kernel.org \
--to=kuba@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@nvidia.com \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=milena.olech@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.