From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: kory.maincent@bootlin.com, andrew@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net] net: ethtool: handle EOPNOTSUPP from ethtool get_ts_info() method
Date: Sat, 13 Sep 2025 00:40:05 +0000 [thread overview]
Message-ID: <175772400550.3115588.6343280449330593634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1uwiW3-00000004jRF-3CnC@rmk-PC.armlinux.org.uk>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 11 Sep 2025 15:43:15 +0100 you wrote:
> Network drivers sometimes return -EOPNOTSUPP from their get_ts_info()
> method, and this should not cause the reporting of PHY timestamping
> information to be prohibited. Handle this error code, and also
> arrange for ethtool_net_get_ts_info_by_phc() to return -EOPNOTSUPP
> when the method is not implemented.
>
> This allows e.g. PHYs connected to DSA switches which support
> timestamping to report their timestamping capabilities.
>
> [...]
Here is the summary with links:
- [net] net: ethtool: handle EOPNOTSUPP from ethtool get_ts_info() method
https://git.kernel.org/netdev/net/c/201825fb4278
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-13 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 14:43 [PATCH net] net: ethtool: handle EOPNOTSUPP from ethtool get_ts_info() method Russell King (Oracle)
2025-09-11 21:37 ` Kory Maincent
2025-09-13 0:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-09 14:07 Russell King (Oracle)
2025-09-11 16:56 ` Simon Horman
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=175772400550.3115588.6343280449330593634.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=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).