From: patchwork-bot+netdevbpf@kernel.org
To: Rahul Rameshbabu <rrameshbabu@nvidia.com>
Cc: netdev@vger.kernel.org, gal@nvidia.com, saeed@kernel.org,
tariqt@nvidia.com, kuba@kernel.org, richardcochran@gmail.com,
jacob.e.keller@intel.com, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [PATCH v3 0/9] ptp .adjphase cleanups
Date: Tue, 20 Jun 2023 08:10:22 +0000 [thread overview]
Message-ID: <168724862293.22435.9678368746487298920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230612211500.309075-1-rrameshbabu@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 12 Jun 2023 14:14:51 -0700 you wrote:
> The goal of this patch series is to improve documentation of .adjphase, add
> a new callback .getmaxphase to enable advertising the max phase offset a
> device PHC can support, and support invoking .adjphase from the testptp
> kselftest.
>
> Changes:
> v3->v2:
> * Add information about returning -ERANGE instead of clamping
> out-of-range offsets for driver implementations of .adjphase that
> previously clamped out-of-range offsets.
>
> [...]
Here is the summary with links:
- [v3,1/9] ptp: Clarify ptp_clock_info .adjphase expects an internal servo to be used
https://git.kernel.org/netdev/net-next/c/a05d070a6164
- [v3,2/9] docs: ptp.rst: Add information about NVIDIA Mellanox devices
https://git.kernel.org/netdev/net-next/c/fe3834cd0cf7
- [v3,3/9] testptp: Remove magic numbers related to nanosecond to second conversion
https://git.kernel.org/netdev/net-next/c/048f6d998eac
- [v3,4/9] testptp: Add support for testing ptp_clock_info .adjphase callback
https://git.kernel.org/netdev/net-next/c/3a9a9a613928
- [v3,5/9] ptp: Add .getmaxphase callback to ptp_clock_info
https://git.kernel.org/netdev/net-next/c/c3b60ab7a4df
- [v3,6/9] net/mlx5: Add .getmaxphase ptp_clock_info callback
https://git.kernel.org/netdev/net-next/c/67ac72a599d8
- [v3,7/9] ptp: ptp_clockmatrix: Add .getmaxphase ptp_clock_info callback
https://git.kernel.org/netdev/net-next/c/c066e74f34bc
- [v3,8/9] ptp: idt82p33: Add .getmaxphase ptp_clock_info callback
https://git.kernel.org/netdev/net-next/c/e156e4d2e43f
- [v3,9/9] ptp: ocp: Add .getmaxphase ptp_clock_info callback
https://git.kernel.org/netdev/net-next/c/d8ee5ca845b4
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:[~2023-06-20 8:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 21:14 [PATCH v3 0/9] ptp .adjphase cleanups Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 1/9] ptp: Clarify ptp_clock_info .adjphase expects an internal servo to be used Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 2/9] docs: ptp.rst: Add information about NVIDIA Mellanox devices Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 3/9] testptp: Remove magic numbers related to nanosecond to second conversion Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 4/9] testptp: Add support for testing ptp_clock_info .adjphase callback Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 5/9] ptp: Add .getmaxphase callback to ptp_clock_info Rahul Rameshbabu
2023-06-27 16:21 ` Nathan Chancellor
2023-06-27 17:08 ` Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 6/9] net/mlx5: Add .getmaxphase ptp_clock_info callback Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 7/9] ptp: ptp_clockmatrix: " Rahul Rameshbabu
2023-06-12 21:14 ` [PATCH v3 8/9] ptp: idt82p33: " Rahul Rameshbabu
2023-06-12 21:15 ` [PATCH v3 9/9] ptp: ocp: " Rahul Rameshbabu
2023-06-12 21:25 ` [PATCH v3 0/9] ptp .adjphase cleanups Rahul Rameshbabu
2023-06-20 8: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=168724862293.22435.9678368746487298920.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gal@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeed@kernel.org \
--cc=tariqt@nvidia.com \
/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).