fcoe_ctlr_device_queue_work(9)

💅 fcoe_ctlr_device_queue_work(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this little page is all about fcoe_ctlr_device_queue_work(9), and yes we're gonna get into it.

✨ NAME ✨

fcoe_ctlr_device_queue_work — schedule work for a FIP ctlr's workqueue 🫶

🌸 SYNOPSIS 🌸

int fcoe_ctlr_device_queue_work (struct fcoe_ctlr_device *ctlr , struct
work_struct *work );

like, that's the whole signature, no cap 💅

🎀 ARGUMENTS 🎀

• ctlr — pointer to the FIP ctlr who owns the devloss workqueue 👑 (yes, owns, main character energy fr)
• work — the work to queue for execution ⚙️

🦋 DESCRIPTION 🦋

okay so the return value is literally the whole vibe check here:

• 1 on success 🎉
• 0 already queued 🙈
• < 0 for error 😭

that's it, that's the function. short and iconic, periodt.

🌈 SEE ALSO 🌈

• Kernel file ./drivers/scsi/fcoe/fcoe_sysfs.c
• fcoe_ctlr_device_release(9)
• fcoe_fcf_device_release(9)
• fcoe_ctlr_device_flush_work(9)
• fcoe_ctlr_device_flush_devloss(9)
• fcoe_ctlr_device_queue_devloss_work(9)
• fcoe_ctlr_device_add(9)
• fcoe_ctlr_device_delete(9)
• fcoe_fcf_device_final_delete(9)
• fip_timeout_deleted_fcf(9)
• fcoe_fcf_device_delete(9)
• fcoe_fcf_device_add(9)

---

ngl bestie, if you're poking around ./drivers/scsi/fcoe you should probably read those before you break something 💀

k that's the page!! mwah 🫶

— signed, sealed, delivered by the ./drivers/scsi/fcoe source tree, dated October 2026, and yes it's still called fcoe_ctlr_device_queue_work(9) in case you forgot already 🎀✨