From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: andrew+netdev@lunn.ch, linux@armlinux.org.uk,
hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
andrew@lunn.ch, horms@kernel.org, vladimir.oltean@nxp.com,
jacob.e.keller@intel.com, kory.maincent@bootlin.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/4] support for hwtstamp_get in phy - part 2
Date: Fri, 09 Jan 2026 04:20:11 +0000 [thread overview]
Message-ID: <176793241154.98179.1678070764645293160.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260106160723.3925872-1-vadim.fedorenko@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2026-01-09 4:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 16:07 [PATCH net-next v3 0/4] support for hwtstamp_get in phy - part 2 Vadim Fedorenko
2026-01-06 16:07 ` [PATCH net-next v3 1/4] net: phy: micrel: improve HW timestamping config logic Vadim Fedorenko
2026-01-06 17:54 ` Kory Maincent
2026-01-06 16:07 ` [PATCH net-next v3 2/4] net: phy: micrel: add HW timestamp configuration reporting Vadim Fedorenko
2026-01-06 16:07 ` [PATCH net-next v3 3/4] net: phy: microchip_rds_ptp: improve HW ts config logic Vadim Fedorenko
2026-01-06 17:58 ` Kory Maincent
2026-01-06 16:07 ` [PATCH net-next v3 4/4] net: phy: microchip_rds_ptp: add HW timestamp configuration reporting Vadim Fedorenko
2026-01-09 4:20 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176793241154.98179.1678070764645293160.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox