From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: remove legacy way to get/set HW timestamp config
Date: Thu, 15 Jan 2026 12:31:05 +0000 [thread overview]
Message-ID: <c548e847-ec4a-4aeb-99c0-c48342a21a11@linux.dev> (raw)
In-Reply-To: <20260115125815.299accc6@kmaincent-XPS-13-7390>
On 15/01/2026 11:58, Kory Maincent wrote:
> On Wed, 14 Jan 2026 22:44:13 +0000
> Vadim Fedorenko <vadim.fedorenko@linux.dev> wrote:
>
>> With all drivers converted to use ndo_hwstamp callbacks the legacy way
>> can be removed, marking ioctl interface as deprecated.
>
> Thanks for all this work converting drivers to ndo_hwtstamp!
>
> Maybe you can also remove this:
> https://elixir.bootlin.com/linux/v6.19-rc5/source/drivers/infiniband/ulp/ipoib/ipoib_main.c#L1834
Hmm... looks like left-over from the drivers cleaning part. I'll remove
it in next version.
>
> And in the driver development part of the documentation to avoid any new driver
> with it:
> https://elixir.bootlin.com/linux/v6.19-rc5/source/Documentation/networking/timestamping.rst#L630
Good point, I'll adjust it in v2!
Thanks!
>
> Regards,
prev parent reply other threads:[~2026-01-15 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 22:44 [PATCH net-next 1/2] net: remove legacy way to get/set HW timestamp config Vadim Fedorenko
2026-01-14 22:44 ` [PATCH net-next 2/2] selftests: drv-net: extend HW timestamp test with ioctl Vadim Fedorenko
2026-01-15 12:03 ` Kory Maincent
2026-01-16 4:10 ` Jakub Kicinski
2026-01-16 6:12 ` Vadim Fedorenko
2026-01-15 11:58 ` [PATCH net-next 1/2] net: remove legacy way to get/set HW timestamp config Kory Maincent
2026-01-15 12:31 ` Vadim Fedorenko [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=c548e847-ec4a-4aeb-99c0-c48342a21a11@linux.dev \
--to=vadim.fedorenko@linux.dev \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shuah@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.