From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, donald.hunter@gmail.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, jstancek@redhat.com, sdf@fomichev.me
Subject: Re: [PATCH net] tools/net/ynl: ethtool: fix crash when Hardware Clock info is missing
Date: Fri, 09 May 2025 23:30:34 +0000 [thread overview]
Message-ID: <174683343499.3841790.4154973310756554641.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250508035414.82974-1-liuhangbin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 May 2025 03:54:14 +0000 you wrote:
> Fix a crash in the ethtool YNL implementation when Hardware Clock information
> is not present in the response. This ensures graceful handling of devices or
> drivers that do not provide this optional field. e.g.
>
> Traceback (most recent call last):
> File "/net/tools/net/ynl/pyynl/./ethtool.py", line 438, in <module>
> main()
> ~~~~^^
> File "/net/tools/net/ynl/pyynl/./ethtool.py", line 341, in main
> print(f'PTP Hardware Clock: {tsinfo["phc-index"]}')
> ~~~~~~^^^^^^^^^^^^^
> KeyError: 'phc-index'
>
> [...]
Here is the summary with links:
- [net] tools/net/ynl: ethtool: fix crash when Hardware Clock info is missing
https://git.kernel.org/netdev/net/c/45375814eb3f
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:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 3:54 [PATCH net] tools/net/ynl: ethtool: fix crash when Hardware Clock info is missing Hangbin Liu
2025-05-08 16:13 ` Stanislav Fomichev
2025-05-09 23:30 ` 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=174683343499.3841790.4154973310756554641.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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).