[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQtCis59KXvcQSqO@hoboy.vegasvil.org>
Date: Wed, 5 Nov 2025 04:26:50 -0800
From: Richard Cochran <richardcochran@...il.com>
To: Tim Hostetler <thostet@...gle.com>
Cc: netdev@...r.kernel.org, andrew+netdev@...n.ch, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
linux-kernel@...r.kernel.org, Kuniyuki Iwashima <kuniyu@...gle.com>,
Harshitha Ramamurthy <hramamurthy@...gle.com>,
Vadim Fedorenko <vadim.fedorenko@...ux.dev>
Subject: Re: [PATCH net-next v2] ptp: Return -EINVAL on ptp_clock_register if
required ops are NULL
On Tue, Nov 04, 2025 at 02:59:15PM -0800, Tim Hostetler wrote:
> ptp_clock should never be registered unless it stubs one of gettimex64()
> or gettime64() and settime64(). WARN_ON_ONCE and error out if either set
> of function pointers is null.
>
> For consistency, n_alarm validation is also folded into the
> WARN_ON_ONCE.
>
> Suggested-by: Kuniyuki Iwashima <kuniyu@...gle.com>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@...gle.com>
> Reviewed-by: Harshitha Ramamurthy <hramamurthy@...gle.com>
> Reviewed-by: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
> Signed-off-by: Tim Hostetler <thostet@...gle.com>
Acked-by: Richard Cochran <richardcochran@...il.com>
Powered by blists - more mailing lists