netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@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: Fri, 05 Jan 2024 16:10:27 +0000	[thread overview]
Message-ID: <170447102715.8824.5095352127275403572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240103132838.1501801-1-jiri@resnulli.us>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  3 Jan 2024 14:28:35 +0100 you 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.
> 
> Jiri Pirko (3):
>   dpll: expose fractional frequency offset value to user
>   net/mlx5: DPLL, Use struct to get values from
>     mlx5_dpll_synce_status_get()
>   net/mlx5: DPLL, Implement fractional frequency offset get pin op
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] dpll: expose fractional frequency offset value to user
    https://git.kernel.org/netdev/net-next/c/8a6286c1804e
  - [net-next,2/3] net/mlx5: DPLL, Use struct to get values from mlx5_dpll_synce_status_get()
    https://git.kernel.org/netdev/net-next/c/e6d86938a40a
  - [net-next,3/3] net/mlx5: DPLL, Implement fractional frequency offset get pin op
    https://git.kernel.org/netdev/net-next/c/f035dca34ede

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-05 16:10 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 ` [patch net-next 0/3] dpll: expose fractional frequency offset value to user Jakub Kicinski
2024-01-05 11:44 ` Vadim Fedorenko
2024-01-05 17:53   ` Jiri Pirko
2024-01-05 14:56 ` Kubalewski, Arkadiusz
2024-01-05 16:10 ` 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=170447102715.8824.5095352127275403572.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --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).