From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
jiri@resnulli.us, corbet@lwn.net, davem@davemloft.net,
pabeni@redhat.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, linux-doc@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next v4 0/5] dpll: add phase-offset and phase-adjust
Date: Tue, 10 Oct 2023 19:34:40 -0700 [thread overview]
Message-ID: <20231010193440.76f93d5c@kernel.org> (raw)
In-Reply-To: <20231009222616.12163-1-arkadiusz.kubalewski@intel.com>
On Tue, 10 Oct 2023 00:26:11 +0200 Arkadiusz Kubalewski wrote:
> Improve monitoring and control over dpll devices.
> Allow user to receive measurement of phase difference between signals
> on pin and dpll (phase-offset).
> Allow user to receive and control adjustable value of pin's signal
> phase (phase-adjust).
Does not apply, please rebase / repost.
next prev parent reply other threads:[~2023-10-11 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 22:26 [PATCH net-next v4 0/5] dpll: add phase-offset and phase-adjust Arkadiusz Kubalewski
2023-10-09 22:26 ` [PATCH net-next v4 1/5] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
2023-10-09 22:26 ` [PATCH net-next v4 2/5] dpll: spec: add support for pin-dpll " Arkadiusz Kubalewski
2023-10-09 22:26 ` [PATCH net-next v4 3/5] dpll: netlink/core: " Arkadiusz Kubalewski
2023-10-09 22:26 ` [PATCH net-next v4 4/5] ice: dpll: implement phase related callbacks Arkadiusz Kubalewski
2023-10-09 22:26 ` [PATCH net-next v4 5/5] dpll: netlink/core: change pin frequency set behavior Arkadiusz Kubalewski
2023-10-10 7:44 ` [PATCH net-next v4 0/5] dpll: add phase-offset and phase-adjust Jiri Pirko
2023-10-10 9:59 ` Vadim Fedorenko
2023-10-11 2:34 ` Jakub Kicinski [this message]
2023-10-11 10:19 ` Kubalewski, Arkadiusz
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=20231010193440.76f93d5c@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).