lpfc_delete_device_data(9)
π lpfc_delete_device_data(9) β like, the kernel API manual page, bestie β¨
okay so welcome to lpfc_delete_device_data, a little function from the kernel API manual, section 9 of the man pages. yes we're in the kernel docs today, put your hair up, we're going in π
β¨ NAME β¨
lpfc_delete_device_data β frees a device data structure for OAS π¦
πΈ SYNOPSIS πΈ
void lpfc_delete_device_data (struct lpfc_hba *phba , struct
lpfc_device_data *lun_info );
that's the whole signature, no cap. it returns void, so likeβ¦ it gives you nothing back and honestly that's iconic of it π
π«Ά ARGUMENTS π«Ά
phbaβ pointer to the host bus adapter structure. that's your HBA, the main character of this whole operation πlun_infoβ pointer to the device data structure you want to free. this is the one getting yeeted πͺ¦
π DESCRIPTION π
so what does this routine actually do? it frees the previously allocated device data structure that you passed in. that's it. that's the whole vibe. you hand it lun_info, it does the freeing thing, done, no notes π§
literally its entire personality is "give me the thing, I release the thing." lowkey elegant tbh β
π SEE ALSO π
kernel file: ./drivers/scsi/lpfc/lpfc_scsi.c π
and here's the whole friend group, in order, all section 9, all accounted for β nobody left behind fr fr π«Ά
lpfc_sli4_set_rsp_sgl_last(9)lpfc_rampdown_queue_depth(9)lpfc_ramp_down_queue_handler(9)lpfc_scsi_dev_block(9)lpfc_new_scsi_buf_s3(9)lpfc_sli4_vport_delete_fcp_xri_aborted(9)lpfc_sli4_io_xri_aborted(9)lpfc_get_scsi_buf_s3(9)lpfc_get_scsi_buf_s4(9)lpfc_get_scsi_buf(9)lpfc_release_scsi_buf_s3(9)lpfc_release_scsi_buf_s4(9)lpfc_release_scsi_buf(9)lpfc_fcpcmd_to_iocb(9)lpfc_scsi_prep_dma_buf_s3(9)lpfc_bg_err_inject(9)lpfc_sc_to_bg_opcodes(9)lpfc_bg_err_opcodes(9)lpfc_bg_setup_bpl(9)lpfc_bg_setup_bpl_prot(9)lpfc_bg_setup_sgl(9)lpfc_bg_setup_sgl_prot(9)lpfc_prot_group_type(9)lpfc_bg_scsi_adjust_dl(9)lpfc_bg_scsi_prep_dma_buf_s3(9)lpfc_scsi_prep_dma_buf_s4(9)lpfc_bg_scsi_prep_dma_buf_s4(9)lpfc_scsi_prep_dma_buf(9)lpfc_bg_scsi_prep_dma_buf(9)lpfc_scsi_prep_cmnd_buf(9)lpfc_send_scsi_error_event(9)lpfc_scsi_unprep_dma_buf(9)lpfc_unblock_requests(9)lpfc_block_requests(9)lpfc_update_cmf_cmpl(9)lpfc_update_cmf_cmd(9)lpfc_handle_fcp_err(9)lpfc_fcp_io_cmd_wqe_cmpl(9)lpfc_scsi_cmd_iocb_cmpl(9)lpfc_scsi_prep_cmnd_buf_s3(9)lpfc_scsi_prep_cmnd_buf_s4(9)lpfc_scsi_prep_cmnd(9)lpfc_scsi_prep_task_mgmt_cmd_s3(9)lpfc_scsi_prep_task_mgmt_cmd_s4(9)lpfc_scsi_api_table_setup(9)lpfc_tskmgmt_def_cmpl(9)lpfc_check_pci_resettable(9)lpfc_info(9)lpfc_poll_rearm_timer(9)lpfc_poll_start_timer(9)lpfc_poll_timeout(9)lpfc_queuecommand(9)lpfc_abort_handler(9)lpfc_check_fcp_rsp(9)lpfc_send_taskmgmt(9)lpfc_chk_tgt_mapped(9)lpfc_reset_flush_io_context(9)lpfc_device_reset_handler(9)lpfc_target_reset_handler(9)lpfc_host_reset_handler(9)lpfc_sdev_init(9)lpfc_sdev_configure(9)lpfc_sdev_destroy(9)lpfc_create_device_data(9)__lpfc_get_device_data(9)lpfc_find_next_oas_lun(9)lpfc_enable_oas_lun(9)lpfc_disable_oas_lun(9)
ok and one lil heads up before you go: if you're out here guessing how any of these behave beyond what's written above, don't β this page only tells you what it tells you, bestie π
okay that's the whole page, mwah π and for the cute sign-off: this lil beauty lives at ./drivers/scsi/lpfc, it's dated October 2026, and yes babes, the page footer really does say lpfc_delete_device_data(9) β slay, we're done here πβ¨π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms