fsm_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fsm_event(9) β€” the kernel API manual, bestie edition

okay so you found the fsm_event(9) page, iconic, welcome πŸ’– this is the little function that pokes a finite state machine and tells it "hey girl, something happened."


✨ NAME ✨

fsm_event β€” emits an event to a finite state machine πŸŽ€

✨ SYNOPSIS ✨

int fsm_event (fsm_instance *fi , int event , void *arg );

literally that's the whole signature, no cap. ✨

✨ ARGUMENTS ✨

  • fi β€” pointer to the FSM that should receive the event 🫢 she's the one getting the news.
  • event β€” the event to be delivered πŸ“¬ like a little group-chat message but for state machines.
  • arg β€” a generic argument, passed to the action function 🎁 it just gets handed straight over, no questions asked.

✨ DESCRIPTION ✨

so here's the vibe: if an action function is defined for the current state/event combination, that function is called with the provided arguments. that's it. that's the whole plot πŸ’… the state machine checks "do I have a handler for this exact state + event combo?" and if yes, it runs it with the args you gave.

✨ RETURN ✨

  • 0 β€” success, the action function was called πŸ”₯ ate and left no crumbs.
  • 1 β€” state/event out of range, or no action function defined 😭 so basically nothing got called.

✨ SEE ALSO ✨

the whole friend group, go say hi πŸ‘‘:


and that's the page, babe 🌈 this little gem lives in ./drivers/s390/net, dated October 2026, and it's the fsm_event(9) manual β€” so go forth, emit your events, and slay πŸ’œπŸ¦‹

πŸ“¦ where this page comes from