[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lecbq24v.ffs@tglx>
Date: Mon, 09 Oct 2023 16:52:32 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Xabier Marquiegui <reibax@...il.com>, netdev@...r.kernel.org
Cc: richardcochran@...il.com, jstultz@...gle.com, horms@...nel.org,
chrony-dev@...ony.tuxfamily.org, mlichvar@...hat.com, reibax@...il.com,
ntp-lists@...tcorallo.com, vinicius.gomes@...el.com, davem@...emloft.net,
rrameshbabu@...dia.com, shuah@...nel.org
Subject: Re: [PATCH net-next v5 1/6] posix-clock: introduce
posix_clock_context concept
On Mon, Oct 09 2023 at 00:49, 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
"This patch .."
We already know that this is a patch.
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
>
> +struct posix_clock_context {
> + struct posix_clock *clk;
> + void *private_clkdata;
> +};
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#struct-declarations-and-initializers
Thanks,
tglx
Powered by blists - more mailing lists