From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kory.maincent@bootlin.com,
richardcochran@gmail.com, horms@kernel.org, shuah@kernel.org,
sdf@fomichev.me, tariqt@nvidia.com, leon@kernel.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net: remove legacy way to get/set HW timestamp config
Date: Wed, 21 Jan 2026 02:30:24 +0000 [thread overview]
Message-ID: <176896262485.696500.7276448637891401906.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260116062121.1230184-1-vadim.fedorenko@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Jan 2026 06:21:20 +0000 you wrote:
> With all drivers converted to use ndo_hwstamp callbacks the legacy way
> can be removed, marking ioctl interface as deprecated.
>
> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> ---
> v1 -> v2:
> * added cleanup in Infiniband
> * adjusted documentation to remove mentions of legacy way
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: remove legacy way to get/set HW timestamp config
https://git.kernel.org/netdev/net-next/c/5062245a5a7f
- [net-next,v2,2/2] selftests: drv-net: extend HW timestamp test with ioctl
https://git.kernel.org/netdev/net-next/c/49743f27268f
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-21 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 6:21 [PATCH net-next v2 1/2] net: remove legacy way to get/set HW timestamp config Vadim Fedorenko
2026-01-16 6:21 ` [PATCH net-next v2 2/2] selftests: drv-net: extend HW timestamp test with ioctl Vadim Fedorenko
2026-01-19 15:36 ` [PATCH net-next v2 1/2] net: remove legacy way to get/set HW timestamp config Kory Maincent
2026-01-21 2:30 ` 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=176896262485.696500.7276448637891401906.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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