All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	Jacob Keller <jacob.e.keller@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Richard Cochran <richardcochran@gmail.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 5/5] i40e: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
Date: Fri, 16 May 2025 13:27:11 +0100	[thread overview]
Message-ID: <20250516122711.GD3339421@horms.kernel.org> (raw)
In-Reply-To: <20250513101132.328235-6-vladimir.oltean@nxp.com>

On Tue, May 13, 2025 at 01:11:32PM +0300, Vladimir Oltean wrote:
> New timestamping API was introduced in commit 66f7223039c0 ("net: add
> NDOs for configuring hardware timestamping") from kernel v6.6.
> 
> It is time to convert the Intel i40e driver to the new API, so that
> timestamping configuration can be removed from the ndo_eth_ioctl() path
> completely.
> 
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>

Reviewed-by: Simon Horman <horms@kernel.org>


WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	Jacob Keller <jacob.e.keller@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH iwl-next 5/5] i40e: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
Date: Fri, 16 May 2025 13:27:11 +0100	[thread overview]
Message-ID: <20250516122711.GD3339421@horms.kernel.org> (raw)
In-Reply-To: <20250513101132.328235-6-vladimir.oltean@nxp.com>

On Tue, May 13, 2025 at 01:11:32PM +0300, Vladimir Oltean wrote:
> New timestamping API was introduced in commit 66f7223039c0 ("net: add
> NDOs for configuring hardware timestamping") from kernel v6.6.
> 
> It is time to convert the Intel i40e driver to the new API, so that
> timestamping configuration can be removed from the ndo_eth_ioctl() path
> completely.
> 
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2025-05-16 12:27 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 10:11 [Intel-wired-lan] [PATCH iwl-next 0/5] Intel driver conversion to new hardware timestamping API Vladimir Oltean
2025-05-13 10:11 ` Vladimir Oltean
2025-05-13 10:11 ` [Intel-wired-lan] [PATCH iwl-next 1/5] ice: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set() Vladimir Oltean
2025-05-13 10:11   ` Vladimir Oltean
2025-05-13 22:26   ` [Intel-wired-lan] " Jacob Keller
2025-05-13 22:26     ` Jacob Keller
2025-05-16 12:25   ` [Intel-wired-lan] " Simon Horman
2025-05-16 12:25     ` Simon Horman
2025-06-04 13:39   ` [Intel-wired-lan] " Rinitha, SX
2025-06-04 13:39     ` Rinitha, SX
2025-05-13 10:11 ` [Intel-wired-lan] [PATCH iwl-next 2/5] igc: " Vladimir Oltean
2025-05-13 10:11   ` Vladimir Oltean
2025-05-16 12:26   ` [Intel-wired-lan] " Simon Horman
2025-05-16 12:26     ` Simon Horman
2025-05-26  9:21     ` [Intel-wired-lan] " Lifshits, Vitaly
2025-05-29  7:15   ` Mor Bar-Gabay
2025-05-13 10:11 ` [Intel-wired-lan] [PATCH iwl-next 3/5] igb: " Vladimir Oltean
2025-05-13 10:11   ` Vladimir Oltean
2025-05-16 12:26   ` [Intel-wired-lan] " Simon Horman
2025-05-16 12:26     ` Simon Horman
2025-06-10  6:27   ` [Intel-wired-lan] " Rinitha, SX
2025-06-10  6:27     ` Rinitha, SX
2025-05-13 10:11 ` [Intel-wired-lan] [PATCH iwl-next 4/5] ixgbe: " Vladimir Oltean
2025-05-13 10:11   ` Vladimir Oltean
2025-05-16 12:26   ` [Intel-wired-lan] " Simon Horman
2025-05-16 12:26     ` Simon Horman
2025-06-30 18:56   ` [Intel-wired-lan] " Jacob Keller
2025-06-30 18:56     ` Jacob Keller
2025-06-30 20:47     ` [Intel-wired-lan] " Jacob Keller
2025-06-30 20:47       ` Jacob Keller
2025-06-30 20:56       ` [Intel-wired-lan] " Vladimir Oltean
2025-06-30 20:56         ` Vladimir Oltean
2025-06-30 20:58         ` [Intel-wired-lan] " Nguyen, Anthony L
2025-06-30 20:58           ` Nguyen, Anthony L
2025-06-30 21:05         ` [Intel-wired-lan] " Jacob Keller
2025-06-30 21:05           ` Jacob Keller
2025-07-02 17:56   ` [Intel-wired-lan] " Rinitha, SX
2025-07-02 17:56     ` Rinitha, SX
2025-05-13 10:11 ` [Intel-wired-lan] [PATCH iwl-next 5/5] i40e: " Vladimir Oltean
2025-05-13 10:11   ` Vladimir Oltean
2025-05-16 12:27   ` Simon Horman [this message]
2025-05-16 12:27     ` Simon Horman
2025-06-04 13:33   ` [Intel-wired-lan] " Rinitha, SX
2025-06-04 13:33     ` Rinitha, SX
2025-05-14 10:03 ` [Intel-wired-lan] [PATCH iwl-next 0/5] Intel driver conversion to new hardware timestamping API Vadim Fedorenko
2025-05-14 10:03   ` Vadim Fedorenko
2025-05-14 12:17 ` [Intel-wired-lan] " Olech, Milena
2025-05-14 12:17   ` Olech, Milena

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=20250516122711.GD3339421@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=vinicius.gomes@intel.com \
    --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 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.