From: Genes Lists <lists@sapience.com>
To: Yao Zi <ziyao@disroot.org>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Richard Cochran <richardcochran@gmail.com>,
Johannes Berg <johannes.berg@intel.com>,
Anjaneyulu <pagadala.yesu.anjaneyulu@intel.com>,
Daniel Gabay <daniel.gabay@intel.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Mingcong Bai <jeffbai@aosc.io>,
Kexy Biscuit <kexybiscuit@aosc.io>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH iwlwifi-fixes] wifi: iwlwifi: Implement settime64 as stub for MVM/MLD PTP
Date: Sun, 07 Dec 2025 12:58:21 -0500 [thread overview]
Message-ID: <2cc00d49014047ec83df3d4d4815b240949ffffa.camel@sapience.com> (raw)
In-Reply-To: <20251204123204.9316-1-ziyao@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-07 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 12:32 Yao Zi
2025-12-05 22:26 ` Nathan Chancellor
2025-12-06 15:01 ` Simon Horman
2025-12-07 17:58 ` Genes Lists [this message]
2025-12-08 11:23 ` Damian Tometzki
2025-12-13 8:41 ` Oliver Hartkopp
2025-12-13 21:19 ` Korenblit, Miriam Rachel
2025-12-14 10:12 ` David Wang
2025-12-15 3:42 ` Yao Zi
2025-12-15 4:20 ` David Wang
2025-12-15 17:41 ` Yao Zi
2025-12-22 10:43 ` Paolo Abeni
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=2cc00d49014047ec83df3d4d4815b240949ffffa.camel@sapience.com \
--to=lists@sapience.com \
--cc=daniel.gabay@intel.com \
--cc=jeffbai@aosc.io \
--cc=johannes.berg@intel.com \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pagadala.yesu.anjaneyulu@intel.com \
--cc=richardcochran@gmail.com \
--cc=ziyao@disroot.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome