slim_xfer_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… slim_xfer_msg(9) β€” Kernel API Manual, but make it cute ✨

okay bestie, you found the slim_xfer_msg(9) page in the Kernel API Manual 🌸 it's short, it's useful, and yes the spelling of one word is staying exactly as the source gave it. let's go 🫢


✨ NAME ✨

slim_xfer_msg β€” Transfer a value info message on slim device πŸ’–

πŸŽ€ SYNOPSIS πŸŽ€

int slim_xfer_msg (struct slim_device *sbdev , struct slim_val_inf *msg
       , u8 mc );

🌸 ARGUMENTS 🌸

  • sbdev β€” the slim device to which this msg has to be transferred πŸ¦‹
  • msg β€” value info message pointer, periodt ✨
  • mc β€” message code of the message πŸ’…

🫢 DESCRIPTION 🫢

Called by drivers which want to transfer a vlaue or info elements. not me pointing at vlaue β€” that is literally the source spelling, and we are keeping every detail, bestie 😭

😭 RETURN 😭

  • -ETIMEDOUT β€” if transmission of this message timed out πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/slimbus/messaging.c, plus these icons: slim_msg_response(9), slim_alloc_txn_tid(9), slim_free_txn_tid(9), slim_do_transfer(9), slim_read(9), slim_readb(9), slim_write(9), slim_writeb(9) 🌈


xoxo, source/version vibes from ./drivers/slimbus, dated October 2026, and this page is literally slim_xfer_msg(9) β€” bye bestie πŸ’…πŸŽ€

πŸ“¦ where this page comes from