mpi3mr_bsg_verify_adapter(9)
π mpi3mr_bsg_verify_adapter(9) β Kernel API Manual, bestie edition π
okay so picture this: it's a kernel API manual page, it's called mpi3mr_bsg_verify_adapter(9), and it's here to answer exactly one question β is that adapter number actually a real one or are you out here making things up π let's get into it.
β¨ NAME β¨
mpi3mr_bsg_verify_adapter β literally just verifying that the adapter number is valid π«Ά
πΈ SYNOPSIS πΈ
struct mpi3mr_ioc * mpi3mr_bsg_verify_adapter (int ioc_number );
that's it. that's the whole vibe. one argument, one pointer back. iconic β¨
π¦ ARGUMENTS π¦
ioc_numberβ the adapter number, aka the number you're asking the driver to vibe-check for you π
π DESCRIPTION π
so what does it actually do? it returns the adapter instance pointer for the adapter number you handed it. like, you give it a number, it gives you the corresponding pointer. match made in heaven π
but here's the plot twist π if the adapter number does not match anything in the driver's adapter list β if you just made a number up, bestie β the driver returns NULL. no adapter for you. no cap.
π₯ RETURN π₯
the adapter instance reference π (or NULL if the number isn't in the driver's adapter list, as established π)
π SEE ALSO π
the kernel file it all lives in, first of all:
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_app.c
and now the whole friend group, everybody say hi π:
mpi3mr_alloc_trace_buffer(9)mpi3mr_alloc_diag_bufs(9)mpi3mr_issue_diag_buf_post(9)mpi3mr_post_diag_bufs(9)mpi3mr_issue_diag_buf_release(9)mpi3mr_process_trigger(9)mpi3mr_global_trigger(9)mpi3mr_scsisense_trigger(9)mpi3mr_event_trigger(9)mpi3mr_reply_trigger(9)mpi3mr_get_num_trigger(9)mpi3mr_refresh_trigger(9)mpi3mr_release_diag_bufs(9)mpi3mr_set_trigger_data_in_hdb(9)mpi3mr_set_trigger_data_in_all_hdb(9)mpi3mr_hdbstatuschg_evt_th(9)mpi3mr_diag_buffer_for_type(9)mpi3mr_bsg_pel_abort(9)mpi3mr_bsg_refresh_hdb_triggers(9)mpi3mr_bsg_upload_hdb(9)mpi3mr_bsg_repost_hdb(9)mpi3mr_bsg_query_hdb(9)mpi3mr_enable_logdata(9)mpi3mr_get_logdata(9)mpi3mr_bsg_pel_enable(9)mpi3mr_get_all_tgt_info(9)mpi3mr_get_change_count(9)mpi3mr_bsg_adp_reset(9)mpi3mr_bsg_populate_adpinfo(9)mpi3mr_bsg_process_drv_cmds(9)mpi3mr_total_num_ioctl_sges(9)mpi3mr_bsg_build_sgl(9)mpi3mr_get_nvme_data_fmt(9)mpi3mr_build_nvme_sgl(9)mpi3mr_build_nvme_prp(9)mpi3mr_map_data_buffer_dma(9)mpi3mr_bsg_process_mpt_cmds(9)mpi3mr_app_save_logdata_th(9)mpi3mr_bsg_request(9)mpi3mr_bsg_exit(9)mpi3mr_bsg_node_release(9)mpi3mr_bsg_init(9)version_fw_show(9)fw_queue_depth_show(9)op_req_q_count_show(9)reply_queue_count_show(9)reply_qfull_count_show(9)logging_level_show(9)logging_level_store(9)adp_state_show(9)fwfault_count_show(9)sas_address_show(9)device_handle_show(9)persistent_id_show(9)sas_ncq_prio_supported_show(9)sas_ncq_prio_enable_show(9)
okay that's the whole page, mwah π this one shipped from ./drivers/scsi/mpi3mr back in October 2026, and it's still signed mpi3mr_bsg_verify_adapter(9) β so go verify those adapter numbers, bestie, and stay hydrated ππ§π
π¦ 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