[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230405120632.b7pfceyrtxwidyef@skbuf>
Date: Wed, 5 Apr 2023 15:06:32 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: Max Georgiev <glipus@...il.com>
Cc: Jakub Kicinski <kuba@...nel.org>, kory.maincent@...tlin.com,
netdev@...r.kernel.org, maxime.chevallier@...tlin.com,
Vadim Fedorenko <vadim.fedorenko@...ux.dev>,
Richard Cochran <richardcochran@...il.com>,
Gerhard Engleder <gerhard@...leder-embedded.com>
Subject: Re: [PATCH net-next RFC v2] Add NDOs for hardware timestamp get/set
On Wed, Apr 05, 2023 at 12:42:28AM -0600, Max Georgiev wrote:
> Thank you for the comments!
>
> I've sent out v3 of the RFC stack to let the comment flow, and to
> potentially unblock Köry.
> I've added patches to insert ifr pointer into struct
> kernel_hwtstamp_config as Jakub suggested, but no code is relying on
> this new field yet.
> I also added a patch which is supposed to fix the VLAN code path. I
> can implement ndo_hwtstamp_get/set in VLAN as well - please comment if
> it would be a good idea.
> I haven't fixed bond_eth_ioctl() yet - will add it in the next
> version. More driver conversion patches are planned as was discussed.
macvlan_eth_ioctl() needs changing too.
Powered by blists - more mailing lists