isci_io_request_build(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… isci_io_request_build β€” a Kernel API Manual moment ✨

okay so bestie, welcome to the kernel API manual for isci_io_request_build(9) β€” yes that's the real name, it's giving "I was named by a committee" but we move πŸŽ€


✨ NAME ✨

isci_io_request_build β€” this function builds the io request object. that's it, that's the whole job 🫢


🌸 SYNOPSIS 🌸

enum sci_status isci_io_request_build (struct isci_host *ihost , struct
       isci_request *request , struct isci_remote_device *idev );

like, three args, one return type, very demure, very mindful πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ihost β€” this parameter specifies the ISCI host object. she's the main character of this whole situation fr πŸ‘‘
  • request β€” this parameter points to the isci_request object allocated in the request construct function. so like, somebody else already did the allocating, we're just here to build it ✨
  • idev β€” this parameter is the handle for the sci core's remote device object that is the destination for this request. it's literally where the request is going, iykyk 🎯

πŸ’– DESCRIPTION πŸ’–

returns SCI_SUCCESS on successfull completion, or a specific failure code. that's literally the entire description bestie, no cap 😭 β€” note the original spelling "successfull", we don't fix that, we respect it 🫑

⚠️ heads up: the value it gives back is SCI_SUCCESS when it all goes right, and otherwise it's a specific failure code β€” so check that return value, don't just vibe and ignore it πŸ™ˆ

🌈 SEE ALSO 🌈

kernel file ./drivers/scsi/isci/request.c β€” the whole squad lives here πŸ’œ

that's the friend group, go say hi, they all ate πŸ”₯


and that's the page πŸŽ€ mwah πŸ’‹

🧚 sign-off: this one's filed under ./drivers/scsi/isci, stamped October 2026, and yes the page name is still isci_io_request_build(9) because we don't deadname a manpage πŸ’…β­
πŸ“¦ where this page comes from