[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d94137e3-0404-4475-b03c-a80172d6618e@linux.dev>
Date: Wed, 24 Sep 2025 18:11:39 +0100
From: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Michael Chan <michael.chan@...adcom.com>,
Richard Cochran <richardcochran@...il.com>, Tariq Toukan
<tariqt@...dia.com>, Pavan Chebbi <pavan.chebbi@...adcom.com>,
Andrew Lunn <andrew+netdev@...n.ch>, Mark Bloch <mbloch@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [PATCH net-next v2 0/4] convert 3 drivers to ndo_hwtstamp API
On 23/09/2025 18:33, Vadim Fedorenko wrote:
> Convert tg3, bnxt_en and mlx5 to use ndo_hwtstamp API. These 3 drivers
> were chosen because I have access to the HW and is able to test the
> changes. Also there is a selftest provided to validated that the driver
> correctly sets up timestamp configuration, according to what is exposed
> as supported by the hardware. Selftest allows driver to fallback to some
> wider scope of RX timestamping, i.e. it allows the driver to set up
> ptpv2-event filter when ptpv2-l2-event is requested.
Jakub, I had an offlist discussion with Carolina, they have similar
patch with additional cleanup in the internal review now. And it looks
like my patch for mlx5 may be a bit out of the style. Can you please
drop patch 3/4 out of the series and apply the rest? I'm OK to let
nVidia folks to clean up mlx5 properly.
Powered by blists - more mailing lists