fc_elsct_send(9)

💅 fc_elsct_send 💅

Ok so bestie, welcome to the fc_elsct_send page — that's fc_elsct_send(9) if we're being formal, and it lives in the Kernel API Manual. This is the whole vibe: send an ELS or CT frame. That's it, that's the function, and honestly? Iconic. No cap. ✨

---

✨ NAME ✨

fc_elsct_send — literally just sends an ELS or CT frame 🎀

---

🌸 SYNOPSIS 🌸

struct fc_seq * fc_elsct_send (struct fc_lport *lport , u32 did , struct
fc_frame *fp , unsigned int op , void (*resp)(struct fc_seq *, struct
fc_frame *, void *) , void *arg , u32 timer_msec );

Look at her. Seven arguments. Main character energy fr fr. 🫶

---

🦋 ARGUMENTS 🦋

• lport — the local port you're sending the frame on, like, your home base 💖
• did — the destination ID for the frame, aka where it's going 👑
• fp — the frame to be sent, the actual precious cargo 🎀
• op — the operational code
• resp — the callback routine when the response is received, so you're not just sitting there refreshing, iykyk 📞
• arg — the argument to pass to the response callback routine
• timer_msec — the timeout period for the frame (in msecs), because we do NOT wait forever in this house ⏰

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/scsi/libfc/fc_elsct.c

Also go read fc_elsct_init(9) and fc_els_resp_type(9) — they're in the same friend group, you'll love them 💜

---

🌈 Go forth and send those frames bestie, and remember: pass your arg to the callback or the callback will simply not know what you meant. No notes. 💅

---

And that's the tea 🍓 — brought to you from ./drivers/scsi/libfc, stamped October 2026, page fc_elsct_send(9). Mwah 💋