ptp_get_vclocks_index(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ptp_get_vclocks_index(9) β€” from the Kernel API Manual, bestie 🫢

okay so real talk, we're in the Kernel API Manual today and this page is literally called ptp_get_vclocks_index. yes it's a mouthful, no you don't have to say it out loud at parties. it's giving "tiny function, big responsibilities" energy and honestly? we love her for it. 🌸


✨ NAME ✨

ptp_get_vclocks_index β€” grabs, like, all the vclocks index on pclock. and heads up bestie, the caller is responsible to free the memory of vclock_index (yes, YOU, the caller β€” no one else is doing it for you πŸ’€).


πŸ¦‹ SYNOPSIS πŸ¦‹

int ptp_get_vclocks_index (int pclock_index , int **vclock_index );

πŸŽ€ ARGUMENTS πŸŽ€

  • pclock_index β€” the phc index of the ptp pclock. that's it, that's the girl. 🌈
  • vclock_index β€” a pointer to pointer of vclock index. double pointer behavior, double pointer drama, we stan. ✨

πŸ‘‘ DESCRIPTION πŸ‘‘

it returns the number of vclocks. that's the whole description. short, sweet, main character energy fr fr. πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

so here's the whole friend group, no cap β€” starting with the Kernel file ./include/linux/ptp_clock_kernel.h and then every single one of these:

(and yes, ptp_clock_event(9) shows up in that list β€” twice-ish energy is just part of the source material, we don't rewrite the guest list πŸ’€)


🫢 friendly reminder from your favorite kernel bestie: vclock_index memory? yours to free. not mine. not the kernel's. yours. don't leave her hanging.

and that's the whole page!! this one came from ./include/linux, dated October 2026, in the Kernel API Manual. mwah, go free that memory, ily, bye πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from