From: sashiko-bot@kernel.org
To: "Steffen Trumtrar" <s.trumtrar@pengutronix.de>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net-next v5 1/9] net: ethtool: tsconfig: allow hardware timestamping without a PHC
Date: Fri, 13 Nov 2026 11:20:22 +0000 [thread overview]
Message-ID: <sashiko-outbox-212701@kernel.org> (raw)
In-Reply-To: <20261112-v6-7-topic-virtio-net-ptp-v5-1-7ab67b572f4f@pengutronix.de>
> A driver can do hardware timestamping without a PTP hardware clock; its
> get_ts_info() then reports hardware timestamping with phc_index -1.
> ngbe and txgbe (libwx) do so when no PTP clock is registered, e.g. with
> CONFIG_PTP_1588_CLOCK=n, and dpaa without a ptimer-handle.
>
> SIOCGHWTSTAMP and SIOCSHWTSTAMP work for such a device, but
> tsconfig_prepare_data() refuses it with -ENODEV:
>
> - TSCONFIG_GET fails.
> - TSCONFIG_SET passes the new config to ndo_hwtstamp_set() first and
> fails only when building the reply, so user space gets an error
> although the config was applied.
> - In a dump only -EOPNOTSUPP is skipped; the error ends the dump, and
> the devices after this one are not listed.
>
> The reply already leaves out ETHTOOL_A_TSCONFIG_HWTSTAMP_PROVIDER when
> the index is -1. Let tsconfig_prepare_data() take that path instead of
> failing.
>
> Fixes: 6e9e2eed4f39 ("net: ethtool: Add support for tsconfig command to get/set hwtstamp config")
>
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-v6-7-topic-virtio-net-ptp-v5-0-7ab67b572f4f@pengutronix.de?part=1
next prev parent reply other threads:[~2026-11-13 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 11:19 [PATCH net-next v5 0/9] virtio-net: add receive timestamp support Steffen Trumtrar
2026-11-12 11:19 ` [PATCH net-next v5 1/9] net: ethtool: tsconfig: allow hardware timestamping without a PHC Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot [this message]
2026-11-12 11:19 ` [PATCH net-next v5 2/9] virtio-net: zero the whole tx header Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 3/9] virtio-net: copy the XDP rx hash before the program runs Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 4/9] virtio-net: move virtio_net_common_hdr to virtio_net.h Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 5/9] virtio-net: support receive timestamp Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 6/9] virtio-net: assert header sizes Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 7/9] vhost-net: support VIRTIO_NET_F_RX_TSTAMP Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 8/9] virtio-net: add XDP rx timestamp metadata Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 9/9] tun: add rx timestamp to the vnet header Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:26 ` [PATCH net-next v5 0/9] virtio-net: add receive timestamp support netdev-bot+sinfo
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=sashiko-outbox-212701@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=s.trumtrar@pengutronix.de \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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.