author: Willem de Bruijn <willemb@google.com> 2021-12-20 09:46:08 -0500
committer: Jakub Kicinski <kuba@kernel.org> 2021-12-20 18:47:11 -0800
commit: a9725e1d3962ad00288c4ae6d9b518afc51b2adc
parent: 8f905c0e7354ef261360fb7535ea079b1082c105
Commit Summary:
Diffstat:
1 file changed, 2 insertions, 2 deletions
diff --git a/Documentation/networking/timestamping.rst b/Documentation/networking/timestamping.rst
index 80b13353254a..f5809206eb93 100644
--- a/Documentation/networking/timestamping.rst
+++ b/Documentation/networking/timestamping.rst
@@ -582,8 +582,8 @@ Time stamps for outgoing packets are to be generated as follows:
and hardware timestamping is not possible (SKBTX_IN_PROGRESS not set).
- As soon as the driver has sent the packet and/or obtained a
hardware time stamp for it, it passes the time stamp back by
- calling skb_hwtstamp_tx() with the original skb, the raw
- hardware time stamp. skb_hwtstamp_tx() clones the original skb and
+ calling skb_tstamp_tx() with the original skb, the raw
+ hardware time stamp. skb_tstamp_tx() clones the original skb and
adds the timestamps, therefore the original skb has to be freed now.
If obtaining the hardware time stamp somehow fails, then the driver
should not fall back to software time stamping. The rationale is that