idpf_ptp_get...sync_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ idpf_ptp_get_tx_tstamp_async_handler πŸŽ€

okay so this is the page for idpf_ptp_get_tx_tstamp_async_handler, filed under idpf_ptp_get...sync_handler(9) in the Kernel API Manual β€” section 9, kernel API, you know the drill πŸ’…


✨ NAME ✨

idpf_ptp_get_tx_tstamp_async_handler β€” the async callback for getting Tx tstamps, bestie πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

void idpf_ptp_get_tx_tstamp_async_handler (void *ctx , struct kvec *mem , int status );

that's the whole vibe. void, three args, no notes ✨


🌸 ARGUMENTS 🌸

  • ctx β€” the adapter pointer 🫢
  • mem β€” the address and size of the response
  • status β€” the return value of the request

πŸ’œ DESCRIPTION πŸ’œ

so what it does: it reads the tstamps Tx tstamp values out of a received message and drops them directly into the skb. the way that's efficient?? iconic πŸ”₯

and how many timestamps are we reading? the virtchnl message decides that β€” it specifies the number, not us. periodt πŸ’…


⭐ RETURN ⭐

0 on success, -errno otherwise 😭 (yes the synopsis says void, and yes this page still lists a return. we're keeping it exactly as written, don't come for me πŸ™ˆ)


🌈 SEE ALSO 🌈

like a whole friend group of ptp functions, and honestly? obsessed 🧚


and that's the page!! source + version vibes: ./drivers/net/ethernet/intel/idpf, dated October 2026 β€” go off, kernel docs πŸ‘‘πŸ’–

πŸ“¦ where this page comes from