[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2cc00d49014047ec83df3d4d4815b240949ffffa.camel@sapience.com>
Date: Sun, 07 Dec 2025 12:58:21 -0500
From: Genes Lists <lists@...ience.com>
To: Yao Zi <ziyao@...root.org>, Miri Korenblit
<miriam.rachel.korenblit@...el.com>, Richard Cochran
<richardcochran@...il.com>, Johannes Berg <johannes.berg@...el.com>,
Anjaneyulu <pagadala.yesu.anjaneyulu@...el.com>, Daniel Gabay
<daniel.gabay@...el.com>
Cc: linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Mingcong Bai <jeffbai@...c.io>, Kexy Biscuit
<kexybiscuit@...c.io>, Nathan Chancellor <nathan@...nel.org>
Subject: Re: [PATCH iwlwifi-fixes] wifi: iwlwifi: Implement settime64 as
stub for MVM/MLD PTP
On Thu, 2025-12-04 at 12:32 +0000, Yao Zi wrote:
> Since commit dfb073d32cac ("ptp: Return -EINVAL on ptp_clock_register
> if
> required ops are NULL"), PTP clock registered through
> ptp_clock_register
> is required to have ptp_clock_info.settime64 set, however, neither
> MVM
> nor MLD's PTP clock implementation sets it, resulting in warnings
> when
> the interface starts up, like
>
> WARNING: drivers/ptp/ptp_clock.c:325 at
> ptp_clock_register+0x2c8/0x6b8, CPU#1: wpa_supplicant/469
I do see this warning at boot (mainline kernel), but you noted, it all
works fine nonetheless.
I didn't see this in next or mainline yet.
Do you know when this might find it's way to mainline?
thanks
--
Gene
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists