batadv_hard_if_event_meshif(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… batadv_hard_if_event_meshif(9) β€” the mesh-interface event handler bestie

okay so real talk, this is a page from the kernel API manual, aka the batman-adv docs, and we're talking about batadv_hard_if_event_meshif(9). Yes it's a mouthful, yes you'll get it, i believe in you 🫢


✨ NAME ✨

batadv_hard_if_event_meshif β€” it handles events for mesh interfaces. that's it, that's the vibe. when a mesh interface has Something Happen To It, this is the function that shows up to deal with it πŸ’…


🌸 SYNOPSIS 🌸

int batadv_hard_if_event_meshif (unsigned long event , struct net_device *net_dev );

like, two things go in, an int comes out. main character energy fr πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • event β€” the NETDEV_* event that needs handling. yes, the * is doing a lot of work there, it's a whole family of events and this is whichever one just happened ✨
  • net_dev β€” the net_device that generated the event. the little guy who caused all this drama 😭

⭐ RETURN ⭐

it gives you back a NOTIFY_* result. no cap, that's the whole return story πŸ’–


πŸ¦‹ SEE ALSO πŸ¦‹

okay bestie, buckle up, because this list is long β€” it's giving "the whole friend group showed up to the function." these are all in the kernel file ./net/batman-adv/hard-interface.c, and every single one of them is a (9) page:

like?? that's thirty-five of them?? she knows everyone at this party πŸ‘‘ iykyk πŸ’€


a lil heads up: this page comes from ./net/batman-adv and it's dated October 2026. so yes, future-dated docs are a thing and we're just living in it 🧚

anyway that's the whole page, you ate that, go read the other thirty-five now πŸ“ bye bestie!! πŸ’œ

πŸ“¦ where this page comes from