From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: netdev@vger.kernel.org
Cc: Gal Pressman <gal@nvidia.com>, Saeed Mahameed <saeed@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v3 0/9] ptp .adjphase cleanups
Date: Mon, 12 Jun 2023 14:25:42 -0700 [thread overview]
Message-ID: <87a5x4e5k9.fsf@nvidia.com> (raw)
In-Reply-To: <20230612211500.309075-1-rrameshbabu@nvidia.com> (Rahul Rameshbabu's message of "Mon, 12 Jun 2023 14:14:51 -0700")
On Mon, 12 Jun, 2023 14:14:51 -0700 Rahul Rameshbabu <rrameshbabu@nvidia.com> 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.
>
> Link: https://lore.kernel.org/netdev/13b7315446390d3a78d8f508937354f12778b68e.camel@redhat.com/
> v2->v1:
> * Removes arbitrary rule that the PHC servo must restore the frequency
> to the value used in the last .adjfine call if any other PHC
> operation is used after a .adjphase operation.
> * Removes a macro introduced in v1 for adding PTP sysfs device
> attribute nodes using a callback for populating the data.
>
> Link: https://lore.kernel.org/netdev/20230523205440.326934-1-rrameshbabu@nvidia.com/
> Link: https://lore.kernel.org/netdev/20230510205306.136766-1-rrameshbabu@nvidia.com/
> Link: https://lore.kernel.org/netdev/20230120160609.19160723@kernel.org/
>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Richard Cochran <richardcochran@gmail.com>
Sorry that this submission did not correctly target the net-next tree in
the subject. I have been submitting to other subsystems and forgot to
target the correct tree in the subject of this patch series.
-- Rahul Rameshbabu
next prev parent reply other threads:[~2023-06-12 21:25 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 ` Rahul Rameshbabu [this message]
2023-06-20 8:10 ` [PATCH v3 0/9] ptp .adjphase cleanups 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=87a5x4e5k9.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--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=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).