[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250827193105.47aaa17b@kernel.org>
Date: Wed, 27 Aug 2025 19:31:05 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Gatien Chevallier <gatien.chevallier@...s.st.com>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Maxime Coquelin <mcoquelin.stm32@...il.com>, Alexandre
Torgue <alexandre.torgue@...s.st.com>, Richard Cochran
<richardcochran@...il.com>, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
<netdev@...r.kernel.org>, <linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>
Subject: Re: [PATCH net-next v3 1/2] drivers: net: stmmac: handle start time
set in the past for flexible PPS
On Wed, 27 Aug 2025 13:04:58 +0200 Gatien Chevallier wrote:
> + curr_time = ns_to_timespec64(ns);
> + if (target_ns < ns + PTP_SAFE_TIME_OFFSET_NS) {
> + cfg->start = timespec64_add_safe(cfg->start, curr_time);
Is there a strong reason to use timespec64_add_safe()?
It's not exported to modules:
ERROR: modpost: "timespec64_add_safe" [drivers/net/ethernet/stmicro/stmmac/stmmac.ko] undefined!
--
pw-bot: cr
Powered by blists - more mailing lists