lpfc_nvme_abort_fcreq_cmpl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lpfc_nvme_abort_fcreq_cmpl(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for lpfc_nvme_abort_fcreq_cmpl(9) β€” yes that whole mouthful is the name, and yes we're gonna get through it together 🫢

✨ NAME ✨

lpfc_nvme_abort_fcreq_cmpl β€” complete an NVME FCP abort request. That's the mission, that's the vibe, periodt πŸ’…

🌸 SYNOPSIS 🌸

void lpfc_nvme_abort_fcreq_cmpl (struct lpfc_hba *phba , struct
       lpfc_iocbq *cmdiocb , struct lpfc_iocbq *rspiocb );

πŸ’– ARGUMENTS πŸ’–

  • phba β€” pointer to the HBA context object. Your adapter context bestie, holding it down πŸŽ€
  • cmdiocb β€” pointer to the command iocb object. The command iocb pointer, no cap ✨
  • rspiocb β€” pointer to the response iocb object. The response iocb pointer, literally right there πŸ¦‹

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so real talk: if an NVME FCP IO got aborted, this is the callback function that picks it up. That's the whole assignment. It's giving β€œabort request completion callback” energy, and it's not trying to be anything else πŸ’€

Return value: None. No value, no drama, just None 🌸

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/scsi/lpfc/lpfc_nvme.c πŸ‘€

okay bye bestie! 🫢 this page is from the Kernel API Manual, source path ./drivers/scsi/lpfc, dated October 2026, and its page title is lpfc_nvme_abort_fcreq_cmpl(9) β€” mwah πŸ’‹

πŸ“¦ where this page comes from