rio_del_mport_pw_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🫢 rio_del_mport_pw_handler(9) β€” remove that port-write handler, bestie 🫢

okay so this is the Kernel API Manual page for rio_del_mport_pw_handler(9), and it's lowkey a cleanup queen: it removes a port-write message handler from the list of mport specific pw handlers. Slay. ✨


🌸 NAME 🌸

rio_del_mport_pw_handler β€” removes a port-write message handler from the list of mport specific pw handlers. That's the whole vibe: handler goes bye-bye from the mport-specific pw handler list. πŸ’…


✨ SYNOPSIS ✨

here's the signature, character-for-character, no cap:

int rio_del_mport_pw_handler (struct rio_mport *mport , void *context ,
       int (*pwcback)(struct rio_mport *mport, void *context, union rio_pw_msg
       *msg, int step) );

πŸŽ€ ARGUMENTS πŸŽ€

  • mport β€” the RIO master port to bind the portwrite callback. yes bestie, that's what it says.
  • context β€” the registered handler specific context to pass on event.
  • pwcback β€” the registered callback function. its full signature is the int (*pwcback)(...) situation up in the synopsis, iykyk. πŸ¦‹

πŸ’… DESCRIPTION πŸ’…

Returns 0 if the request has been satisfied. that's the return contract, fr fr β€” request satisfied? 0. periodt. 🫢


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/rapidio/rio.c is the main-character file here, and these are all the linked manual pages, no omissions, no cap:


okay bye bestie πŸ’– β€” source/version/date moment: this cutie lives in ./drivers/rapidio, is dated October 2026, and it's literally rio_del_mport_pw_handler(9) in the Kernel API Manual. πŸŽ€

πŸ“¦ where this page comes from