From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Piotr Wejman <piotrwejman90@gmail.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
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>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH] net: e1000e: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
Date: Tue, 4 Feb 2025 14:00:03 +0000 [thread overview]
Message-ID: <16199c68-3a65-456f-8d52-9a98be3d73f6@linux.dev> (raw)
In-Reply-To: <32579b22-a213-4e97-a816-66d0bb301f92@molgen.mpg.de>
On 03/02/2025 16:41, Paul Menzel wrote:
> Dear Piotr,
>
>
> Thank you for your patch.
>
> Am 02.02.25 um 18:08 schrieb Piotr Wejman:
>> Update the driver to the new hw timestamping API.
>
> Could you please elaborate. Maybe a pointer to the new API, and what
> commit added it, and what tests were done, and/or are needed?
The new API was added in 66f7223039c0 ("net: add NDOs for configuring
hardware timestamping") back in 2023, the old ioctl interface is in
deprecated state now.
>
>> Signed-off-by: Piotr Wejman <piotrwejman90@gmail.com>
>> ---
>> drivers/net/ethernet/intel/e1000e/e1000.h | 2 +-
>> drivers/net/ethernet/intel/e1000e/netdev.c | 52 ++++++++--------------
>> 2 files changed, 20 insertions(+), 34 deletions(-)
>
>
> Kind regards,
>
> Paul
next prev parent reply other threads:[~2025-02-04 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 17:08 [Intel-wired-lan] [PATCH] net: e1000e: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set() Piotr Wejman
2025-02-02 17:08 ` Piotr Wejman
2025-02-03 16:41 ` [Intel-wired-lan] " Paul Menzel
2025-02-04 14:00 ` Vadim Fedorenko [this message]
2025-02-04 15:16 ` Lifshits, Vitaly
2025-02-04 15:20 ` Vadim Fedorenko
2025-02-04 15:20 ` Vadim Fedorenko
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=16199c68-3a65-456f-8d52-9a98be3d73f6@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piotrwejman90@gmail.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.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 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.