From: Rahul Rameshbabu <rrameshbabu@nvidia•com>
To: Vadim Fedorenko <vadim.fedorenko@linux•dev>
Cc: netdev@vger•kernel.org, Saeed Mahameed <saeed@kernel•org>,
Gal Pressman <gal@nvidia•com>, Tariq Toukan <tariqt@nvidia•com>,
"David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
Richard Cochran <richardcochran@gmail•com>,
Jacob Keller <jacob.e.keller@intel•com>,
Jonathan Lemon <jonathan.lemon@gmail•com>
Subject: Re: [PATCH net-next 9/9] ptp: ocp: Add .getmaxphase ptp_clock_info callback
Date: Thu, 11 May 2023 13:35:21 -0700 [thread overview]
Message-ID: <87jzxezjw6.fsf@nvidia.com> (raw)
In-Reply-To: <e479b601-a242-8ef2-ade4-3fe477a196fc@linux.dev> (Vadim Fedorenko's message of "Thu, 11 May 2023 12:12:20 +0100")
On Thu, 11 May, 2023 12:12:20 +0100 Vadim Fedorenko <vadim.fedorenko@linux•dev> wrote:
> On 10/05/2023 21:53, Rahul Rameshbabu wrote:
>> Add a function that advertises a maximum offset of zero supported by
>> ptp_clock_info .adjphase in the OCP null ptp implementation.
>>
>> Cc: Richard Cochran <richardcochran@gmail•com> > Cc: Jonathan Lemon <jonathan.lemon@gmail•com>
>
> Neither Jonathan, nor myself are in the actual Cc list.
>
Accidentally had --suppress-cc in the invocation when this patch series
was sent and figured it would not be worth a RESEND since a v2 would
likely be needed. Will check that the v2 properly has the needed CCs for
each patch in the series.
-- Rahul Rameshbabu
next prev parent reply other threads:[~2023-05-11 20:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:52 [PATCH net-next 0/9] ptp .adjphase cleanups Rahul Rameshbabu
2023-05-10 20:52 ` [PATCH net-next 1/9] ptp: Clarify ptp_clock_info .adjphase expects an internal servo to be used Rahul Rameshbabu
2023-05-11 2:09 ` Richard Cochran
2023-05-11 20:20 ` Rahul Rameshbabu
2023-05-12 0:51 ` Richard Cochran
2023-05-22 17:03 ` Rahul Rameshbabu
2023-05-22 20:07 ` Richard Cochran
2023-05-10 20:52 ` [PATCH net-next 2/9] docs: ptp.rst: Add information about NVIDIA Mellanox devices Rahul Rameshbabu
2023-05-11 2:10 ` Richard Cochran
2023-05-10 20:53 ` [PATCH net-next 3/9] testptp: Remove magic numbers related to nanosecond to second conversion Rahul Rameshbabu
2023-05-11 2:14 ` Richard Cochran
2023-05-10 20:53 ` [PATCH net-next 4/9] testptp: Add support for testing ptp_clock_info .adjphase callback Rahul Rameshbabu
2023-05-11 2:15 ` Richard Cochran
2023-05-10 20:53 ` [PATCH net-next 5/9] ptp: Add .getmaxphase callback to ptp_clock_info Rahul Rameshbabu
2023-05-11 2:20 ` Richard Cochran
2023-05-10 20:53 ` [PATCH net-next 6/9] net/mlx5: Add .getmaxphase ptp_clock_info callback Rahul Rameshbabu
2023-05-11 2:20 ` Richard Cochran
2023-05-10 20:53 ` [PATCH net-next 7/9] ptp: ptp_clockmatrix: " Rahul Rameshbabu
2023-05-10 20:53 ` [PATCH net-next 8/9] ptp: idt82p33: " Rahul Rameshbabu
2023-05-10 20:53 ` [PATCH net-next 9/9] ptp: ocp: " Rahul Rameshbabu
2023-05-11 11:12 ` Vadim Fedorenko
2023-05-11 20:35 ` Rahul Rameshbabu [this message]
2023-05-11 2:23 ` [PATCH net-next 0/9] ptp .adjphase cleanups Richard Cochran
2023-05-11 20:26 ` Rahul Rameshbabu
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=87jzxezjw6.fsf@nvidia.com \
--to=rrameshbabu@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=gal@nvidia$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=jonathan.lemon@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=richardcochran@gmail$(echo .)com \
--cc=saeed@kernel$(echo .)org \
--cc=tariqt@nvidia$(echo .)com \
--cc=vadim.fedorenko@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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