From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, vadim.fedorenko@linux.dev,
arkadiusz.kubalewski@intel.com, saeedm@nvidia.com,
leon@kernel.org, michal.michalik@intel.com,
rrameshbabu@nvidia.com
Subject: Re: [patch net-next 0/3] dpll: expose fractional frequency offset value to user
Date: Thu, 4 Jan 2024 16:09:20 -0800 [thread overview]
Message-ID: <20240104160920.4c9855fd@kernel.org> (raw)
In-Reply-To: <20240103132838.1501801-1-jiri@resnulli.us>
On Wed, 3 Jan 2024 14:28:35 +0100 Jiri Pirko wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Allow to expose pin fractional frequency offset value over new DPLL
> generic netlink attribute. Add an op to get the value from the driver.
> Implement this new op in mlx5 driver.
Arkadiusz, Vadim, acks?
--
pw-bot: needs-ack
next prev parent reply other threads:[~2024-01-05 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 13:28 [patch net-next 0/3] dpll: expose fractional frequency offset value to user Jiri Pirko
2024-01-03 13:28 ` [patch net-next 1/3] " Jiri Pirko
2024-01-05 13:32 ` Kubalewski, Arkadiusz
2024-01-05 14:21 ` Jakub Kicinski
2024-01-05 14:57 ` Kubalewski, Arkadiusz
2024-01-03 13:28 ` [patch net-next 2/3] net/mlx5: DPLL, Use struct to get values from mlx5_dpll_synce_status_get() Jiri Pirko
2024-01-05 13:31 ` Kubalewski, Arkadiusz
2024-01-03 13:28 ` [patch net-next 3/3] net/mlx5: DPLL, Implement fractional frequency offset get pin op Jiri Pirko
2024-01-05 13:32 ` Kubalewski, Arkadiusz
2024-01-05 0:09 ` Jakub Kicinski [this message]
2024-01-05 11:44 ` [patch net-next 0/3] dpll: expose fractional frequency offset value to user Vadim Fedorenko
2024-01-05 17:53 ` Jiri Pirko
2024-01-05 14:56 ` Kubalewski, Arkadiusz
2024-01-05 16:10 ` patchwork-bot+netdevbpf
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=20240104160920.4c9855fd@kernel.org \
--to=kuba@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=michal.michalik@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedm@nvidia.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).