batadv_hardif_neigh_put(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… batadv_hardif_neigh_put β€” the Kernel API Manual page you didn't know you needed πŸŽ€

okay so bestie, real talk: this is a page from the Kernel API Manual about batadv_hardif_neigh_put, and it is exactly what it sounds like β€” a refcounter glow-down. One put, and if nobody else is holding on? She's gone. Released. Free. ✨


🌸 NAME 🌸

batadv_hardif_neigh_put β€” decrement the hardif neighbors refcounter and possibly release it

like, the refcounter goes down by one, and maybe the whole thing gets freed? the "possibly" is doing so much work there, ngl πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

void batadv_hardif_neigh_put (struct batadv_hardif_neigh_node
*hardif_neigh );

returns void, takes one pointer, doesn't ask questions. lowkey iconic behavior honestly πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • hardif_neigh β€” the hardif neigh neighbor to free 🫢 like, this is the one getting her refcount decremented (and, you know, the one that'll be released if it's her time)

⭐ SEE ALSO ⭐

okay the reading list, and it is giving kernel file: ./net/batman-adv/originator.h πŸ“š plus the whole put-put-put friend group:

go read them, they're all matching-set energy πŸ’–


ngl a "put" function is serious business β€” you're handing back a reference, and if it's the last one, the thing goes bye-bye. so like… keep your refcounts balanced, bestie, that's the vibe check πŸ˜­πŸ™ˆ

and that's the page!! 🧚 source/version: ./net/batman-adv, dated October 2026 β€” mwah, slay, no cap, batadv_hardif_neigh_put(9) out πŸ’…πŸ’œ

πŸ“¦ where this page comes from