lpfc_sli_co...x_opcode_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ lpfc_sli_config_mbox_opcode_get(9) πŸ¦‹

okay so bestie, this page is from the Kernel API Manual β€” section 9, kernel API girlie β€” and the header is the whole truncated lpfc_sli_co...x_opcode_get(9) situation. The actual function is lpfc_sli_config_mbox_opcode_get. She's long, she's iconic, and she gets an opcode out of an mbox command. πŸ’…


πŸ’– NAME πŸ’–

lpfc_sli_config_mbox_opcode_get β€” Get opcode from a sli_config mbox cmd

✨ SYNOPSIS ✨

uint8_t lpfc_sli_config_mbox_opcode_get (struct lpfc_hba *phba ,
LPFC_MBOXQ_t *mbox );

πŸŽ€ ARGUMENTS πŸŽ€

  • phba β€” pointer to the lpfc_hba data structure. Literally the HBA's main-character data.
  • mbox β€” pointer to the lpfc mbox command queue entry.

🌸 DESCRIPTION 🌸

This routine gets the opcode from a SLI4 specific SLI_CONFIG mailbox command. No cap. That's the whole assignment, and she ate. ✨

If the mailbox command is not MBX_SLI4_CONFIG (0x9B), or if the sub-header is not present, then opcode LPFC_MBOX_OPCODE_NA (0x0) is returned. So yeah, bestie: no matching command or no sub-header, and you get 0x0 back. That's the vibe check, and it failed. 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/scsi/lpfc/lpfc_mbox.c. Plus the whole (9) friend group, fr fr:


xoxo bestie β€” this page comes from ./drivers/scsi/lpfc, dated October 2026, and it's the lpfc_sli_co...x_opcode_get(9) page. πŸ«ΆπŸ’–

πŸ“¦ where this page comes from