From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kory.maincent@bootlin.com,
ioana.ciornei@nxp.com, andrew@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, richardcochran@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: dpaa2-eth: convert to ndo_hwtstamp_set()
Date: Fri, 09 May 2025 23:50:44 +0000 [thread overview]
Message-ID: <174683464424.3845363.14669308209444032064.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250508134102.1747075-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 May 2025 16:41:01 +0300 you 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 DPAA2 Ethernet driver to the new API, so that the
> ndo_eth_ioctl() path can be removed completely.
>
> This driver only responds to SIOCSHWTSTAMP (not SIOCGHWTSTAMP) so
> convert just that.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dpaa2-eth: convert to ndo_hwtstamp_set()
https://git.kernel.org/netdev/net-next/c/b6e79c5da8c2
- [net-next,2/2] net: dpaa2-eth: add ndo_hwtstamp_get() implementation
https://git.kernel.org/netdev/net-next/c/d27c6e8975c6
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:[~2025-05-09 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 13:41 [PATCH net-next 1/2] net: dpaa2-eth: convert to ndo_hwtstamp_set() Vladimir Oltean
2025-05-08 13:41 ` [PATCH net-next 2/2] net: dpaa2-eth: add ndo_hwtstamp_get() implementation Vladimir Oltean
2025-05-08 20:41 ` Vadim Fedorenko
2025-05-08 20:41 ` [PATCH net-next 1/2] net: dpaa2-eth: convert to ndo_hwtstamp_set() Vadim Fedorenko
2025-05-09 23:50 ` 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=174683464424.3845363.14669308209444032064.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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.