batadv_v_hardif_neigh_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… batadv_v_hardif_neigh_init(9) β€” like, the Kernel API Manual bestie ✨

okay so this is a page from the Kernel API Manual, and the function's whole name is batadv_v_hardif_neigh_init. say it with me now 🫢


✨ NAME ✨

batadv_v_hardif_neigh_init β€” bestie, this is the one that initialises the B.A.T.M.A.N. V state of a hard interface neighbour πŸ’–


🌸 SYNOPSIS 🌸

void batadv_v_hardif_neigh_init (struct batadv_hardif_neigh_node
*hardif_neigh );

so it returns void, meaning it gives you nothing back β€” it's giving "I did the work, don't ask for a receipt" energy πŸ’€ and it takes exactly one thing, no more no less:


πŸŽ€ ARGUMENTS πŸŽ€

  • hardif_neigh β€” the hard interface neighbour that needs to get initialised. that's it. that's the whole vibe check. it's a struct batadv_hardif_neigh_node *, and you're handing it over so the function can set up its B.A.T.M.A.N. V state. no cap, that's the entire job 🌈

πŸ”₯ SEE ALSO πŸ”₯

okay this is the part where the manpage just goes absolutely feral with the cross-references and honestly? iconic. it points you at the Kernel file ./net/batman-adv/bat_v.c and then a whole dossier of siblings πŸ‘‘

like, read the whole family, iykyk 😭 they're all in the same file and they all matter, so don't skip a single one πŸ’œ


lowkey reminder bestie: that's the entire page. one function, one argument, zero surprises. slay 🌸

and that's the tea πŸ“ β€” page source is ./net/batman-adv, dated October 2026, and the vibe was batadv_v_hardif_neigh_init(9) all along. bye bestie, happy initialising πŸ§šπŸ’…

πŸ“¦ where this page comes from