From: Simon Horman <horms@kernel.org>
To: Xabier Marquiegui <reibax@gmail.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
tglx@linutronix.de, jstultz@google.com,
chrony-dev@chrony.tuxfamily.org, mlichvar@redhat.com,
ntp-lists@mattcorallo.com, vinicius.gomes@intel.com,
alex.maftei@amd.com, davem@davemloft.net, rrameshbabu@nvidia.com,
shuah@kernel.org
Subject: Re: [PATCH net-next v4 1/6] posix-clock: introduce posix_clock_context concept
Date: Fri, 6 Oct 2023 13:02:15 +0200 [thread overview]
Message-ID: <ZR/pN0Ll5VVNpL4m@kernel.org> (raw)
In-Reply-To: <35e1e4f96e8ad58b4ee6a7fd46424f4cd6294353.1696511486.git.reibax@gmail.com>
On Thu, Oct 05, 2023 at 03:53:11PM +0200, Xabier Marquiegui wrote:
> Add the necessary structure to support custom private-data per
> posix-clock user.
>
> The previous implementation of posix-clock assumed all file open
> instances need access to the same clock structure on private_data.
>
> The need for individual data structures per file open instance has been
> identified when developing support for multiple timestamp event queue
> users for ptp_clock.
>
> This patch introduces a generic posix_clock_context data structure as a
> solution to that, and simmilar problems.
nit: similar
next prev parent reply other threads:[~2023-10-06 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 13:53 [PATCH net-next v4 0/6] ptp: Support for multiple filtered timestamp event queue readers Xabier Marquiegui
2023-10-05 13:53 ` [PATCH net-next v4 1/6] posix-clock: introduce posix_clock_context concept Xabier Marquiegui
2023-10-06 11:02 ` Simon Horman [this message]
2023-10-05 13:53 ` [PATCH net-next v4 2/6] ptp: Replace timestamp event queue with linked list Xabier Marquiegui
2023-10-05 13:53 ` [PATCH net-next v4 3/6] ptp: support multiple timestamp event readers Xabier Marquiegui
2023-10-05 13:53 ` [PATCH net-next v4 4/6] ptp: support event queue reader channel masks Xabier Marquiegui
2023-10-06 11:01 ` Simon Horman
2023-10-06 22:05 ` Vinicius Costa Gomes
2023-10-07 3:53 ` Richard Cochran
2023-10-06 23:35 ` Xabier Marquiegui
2023-10-07 0:35 ` Vinicius Costa Gomes
2023-10-05 13:53 ` [PATCH net-next v4 5/6] ptp: add debugfs interface to see applied " Xabier Marquiegui
2023-10-05 13:53 ` [PATCH net-next v4 6/6] ptp: add testptp mask test Xabier Marquiegui
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=ZR/pN0Ll5VVNpL4m@kernel.org \
--to=horms@kernel.org \
--cc=alex.maftei@amd.com \
--cc=chrony-dev@chrony.tuxfamily.org \
--cc=davem@davemloft.net \
--cc=jstultz@google.com \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ntp-lists@mattcorallo.com \
--cc=reibax@gmail.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=vinicius.gomes@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.