lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20230216094718.63b3244a@kmaincent-XPS-13-7390> Date: Thu, 16 Feb 2023 09:47:18 +0100 From: Köry Maincent <kory.maincent@...tlin.com> To: Jonathan Lemon <jlemon@...gsvamp.com> Cc: Jonathan Lemon <jonathan.lemon@...il.com>, Richard Cochran <richardcochran@...il.com>, Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org, Maxime Chevallier <maxime.chevallier@...tlin.com>, Thomas Petazzoni <thomas.petazzoni@...tlin.com> Subject: Re: net: phy: broadcom: error in rxtstamp callback? Hello Jonathan, On Wed, 15 Feb 2023 11:39:02 -0800 Jonathan Lemon <jlemon@...gsvamp.com> wrote: > The code is correct - see Documentation/networking/timestamping.rst > > The function returns true/false to indicate whether a deferral is needed > in order to receive the timestamp. For this chip, a deferral is never > required - the timestamp is inline if it is present. Alright, thanks for your reply. Regards,
Powered by blists - more mailing lists