fc_destroy_exch_mgr(9)
π fc_destroy_exch_mgr(9) β the Kernel API Manual, bestie edition
okay so this is a page from the Kernel API Manual (fc_destroy_exch_mgr(9), yeah that's the whole title, she's got main character energy in the function-name department) and honestly? she's short. she's concise. she ate and left zero crumbs. let's get into it β¨
π¦ NAME
fc_destroy_exch_mgr β literally destroys an exchange manager. that's it. that's the whole vibe check. π
π SYNOPSIS
void fc_destroy_exch_mgr (void );
no cap, that's the entire signature. void in, void out, nothing returned, nothing taken. iconic minimalism π«Ά
πΈ ARGUMENTS
voidβ no arguments. zero. nada. she takes nothing from nobody π
π₯ SEE ALSO
okay this is the part where the page goes absolutely feral β like, "not me listing every single friend I've ever had" energy. bestie, the cross-references are LONG and we are NOT skipping a single one. every name below is exactly as written, no edits, no merges π
First up, the source file itself:
- Kernel file
./drivers/scsi/libfc/fc_exch.c
then the structs:
struct fc_exch_pool(9)struct fc_exch_mgr(9)struct fc_exch_mgr_anchor(9)
then this whole crew, in this exact order:
fc_exch_name_lookup(9)fc_exch_rctl_name(9)fc_exch_hold(9)fc_exch_setup_hdr(9)fc_exch_release(9)fc_exch_timer_cancel(9)fc_exch_timer_set_locked(9)fc_exch_timer_set(9)fc_exch_done_locked(9)fc_exch_ptr_get(9)fc_exch_ptr_set(9)fc_exch_delete(9)fc_seq_send(9)fc_seq_alloc(9)fc_seq_start_next_locked(9)fc_seq_start_next(9)fc_exch_abort_locked(9)fc_seq_exch_abort(9)fc_invoke_resp(9)fc_exch_timeout(9)fc_exch_em_alloc(9)fc_exch_alloc(9)fc_exch_find(9)fc_exch_done(9)fc_exch_resp(9)fc_seq_lookup_recip(9)fc_seq_lookup_orig(9)fc_exch_set_addr(9)fc_seq_els_rsp_send(9)fc_seq_send_last(9)fc_seq_send_ack(9)fc_exch_send_ba_rjt(9)fc_exch_recv_abts(9)fc_seq_assign(9)fc_seq_release(9)fc_exch_recv_req(9)fc_exch_recv_seq_resp(9)fc_exch_recv_resp(9)fc_exch_abts_resp(9)fc_exch_recv_bls(9)fc_seq_ls_acc(9)fc_seq_ls_rjt(9)fc_exch_reset(9)fc_exch_pool_reset(9)fc_exch_mgr_reset(9)fc_exch_lookup(9)fc_exch_els_rec(9)fc_exch_rrq_resp(9)fc_exch_seq_send(9)fc_exch_rrq(9)fc_exch_els_rrq(9)fc_exch_update_stats(9)fc_exch_mgr_add(9)fc_exch_mgr_destroy(9)fc_exch_mgr_del(9)fc_exch_mgr_list_clone(9)fc_exch_mgr_alloc(9)fc_exch_mgr_free(9)fc_find_ema(9)fc_exch_recv(9)fc_exch_init(9)fc_setup_exch_mgr(9)
likeβ¦ sixty-something siblings. the whole family reunion. iykyk π
lowkey a vibe check: this page really is just the NAME, the SYNOPSIS, the ARGUMENTS and that absolute wall of SEE ALSO. no DESCRIPTION, no OPTIONS, no RETURN VALUE, no ERRORS, no BUGS, no AUTHOR, no COPYRIGHT, no LICENSE section on this one β so there's nothing more to spill. go read fc_exch_mgr_free(9) and the rest if you want lore π
and that's the post, bestie π this page lives in ./drivers/scsi/libfc and it's dated October 2026 β so jot that down, timestamped and slaying, fc_destroy_exch_mgr(9) signing off βπ¦β¨
π¦ 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