linux-kernel - Re: [PATCH net-next 0/3] dpaa_eth conversion to ndo_hwtstamp_get() and ndo_hwtstamp

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7395888c-d674-44aa-9220-dda90d7f6b96@linux.dev>
Date: Thu, 8 May 2025 21:39:23 +0100
From: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
To: Vladimir Oltean <vladimir.oltean@....com>, netdev@...r.kernel.org
Cc: Köry Maincent <kory.maincent@...tlin.com>,
 Madalin Bucur <madalin.bucur@....com>, Andrew Lunn <andrew@...n.ch>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 Simon Horman <horms@...nel.org>, Richard Cochran <richardcochran@...il.com>,
 Russell King <linux@...linux.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] dpaa_eth conversion to ndo_hwtstamp_get()
 and ndo_hwtstamp_set()

On 08/05/2025 13:47, Vladimir Oltean wrote:
> This is part of the effort to finalize the conversion of drivers to the
> dedicated hardware timestamping API.
> 
> In the case of the DPAA1 Ethernet driver, a bit more care is needed,
> because dpaa_ioctl() looks a bit strange. It handles the "set" IOCTL but
> not the "get", and even the phylink_mii_ioctl() portion could do with
> some cleanup.
> 
> Vladimir Oltean (3):
>    net: dpaa_eth: convert to ndo_hwtstamp_set()
>    net: dpaa_eth: add ndo_hwtstamp_get() implementation
>    net: dpaa_eth: simplify dpaa_ioctl()
> 
>   .../net/ethernet/freescale/dpaa/dpaa_eth.c    | 41 ++++++++++---------
>   1 file changed, 21 insertions(+), 20 deletions(-)
> 
For the series:
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@...ux.dev>