[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176793241154.98179.1678070764645293160.git-patchwork-notify@kernel.org>
Date: Fri, 09 Jan 2026 04:20:11 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
Cc: andrew+netdev@...n.ch, linux@...linux.org.uk, hkallweit1@...il.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
richardcochran@...il.com, andrew@...n.ch, horms@...nel.org,
vladimir.oltean@....com, jacob.e.keller@...el.com, kory.maincent@...tlin.com,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/4] support for hwtstamp_get in phy - part 2
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 6 Jan 2026 16:07:19 +0000 you wrote:
> There are 2 drivers which had some inconsistency in HW timestamping
> configuration logic. Improve both of them and add hwtstamp_get()
> callback.
>
> v2 -> v3:
> * fix the copy-paste check of rx_filter instead of tx_type
> * add tx_type check for lan8841
> link to v2: https://lore.kernel.org/netdev/f9919964-236c-4f2e-a7ec-9fe7969aaa55@linux.dev/
> v1 -> v2:
> * add checks and return error in case of unsupported TX tiemstamps
> * get function for lan8814 and lan8841 are the same - keep only one
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] net: phy: micrel: improve HW timestamping config logic
https://git.kernel.org/netdev/net-next/c/88c7ed2fb071
- [net-next,v3,2/4] net: phy: micrel: add HW timestamp configuration reporting
https://git.kernel.org/netdev/net-next/c/32d83db3aaf6
- [net-next,v3,3/4] net: phy: microchip_rds_ptp: improve HW ts config logic
https://git.kernel.org/netdev/net-next/c/ffde97f8ff6a
- [net-next,v3,4/4] net: phy: microchip_rds_ptp: add HW timestamp configuration reporting
https://git.kernel.org/netdev/net-next/c/f529893f404b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists