skb_complete_tx_timestamp(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 skb_complete_tx_timestamp(9) 🎀

okay so welcome to the Kernel API Manual, bestie 💖 — this is the page for skb_complete_tx_timestamp(9), and honestly? It's giving "small function, huge responsibility." Let's get into it ✨

✨ NAME ✨

skb_complete_tx_timestamp — deliver cloned skb with tx timestamps 🦋

🌸 SYNOPSIS 🌸

void skb_complete_tx_timestamp (struct sk_buff *skb , struct
skb_shared_hwtstamps *hwtstamps );

no cap, that's the whole signature 💅 it returns void, so don't go looking for a return value, she gives nothing back 🫶

💜 ARGUMENTS 💜

  • skb — clone of the original outgoing packet. like, a copy of the packet that already left, coming back for its timestamp moment 👑
  • hwtstamps — hardware time stamps. the actual clock info, literally the whole point of the function 🔥

🦋 DESCRIPTION 🦋

so here's the tea, bestie ☕ — PHY drivers may accept clones of transmitted packets for timestamping via their phy_driver.txtstamp method. icon behaviour, truly 🌈

and here's the part where you gotta pay attention: these drivers must call this function to return the skb back to the stack with a timestamp. not "should," not "if you feel like it" — must. it's the whole handoff, the skb comes home and the timestamp comes with it 🫶✨

ngl if you're a PHY driver holding onto a cloned skb and you never call this, you're literally ghosting the stack 😭 don't do that. call the function. return the skb. be a good main character 💅

🌟 SEE ALSO 🌟

Kernel file ./include/linux/skbuff.h — and lowkey the friend group here is massive, so buckle up 🎀

like I said. huge friend group. iykyk 💀🫶

that's the whole page bestie, go timestamp something and slay 💅✨

and that's a wrap on this one, babe 🎀 this page lives at ./include/linux, dated October 2026 — signed, sealed, delivered, periodt 👑💖

📦 where this page comes from