fcoe_ctlr_d...devloss_work(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fcoe_ctlr_d...devloss_work(9)

okay so bestie, welcome to the Kernel API Manual ✨ β€” yes, that's the manual name, and yes, this page is a whole mood. Sit down, grab a strawberry πŸ“, and let's talk about scheduling work on a FIP ctlr's devloss workqueue.


πŸŽ€ NAME πŸŽ€

fcoe_ctlr_device_queue_devloss_work β€” literally the function that schedules work for a FIP ctlr's devloss workqueue. that's it. that's the job. she's an icon, she's a queen, she queues work. πŸ‘‘


✨ SYNOPSIS ✨

int fcoe_ctlr_device_queue_devloss_work (struct fcoe_ctlr_device *ctlr ,
struct delayed_work *work , unsigned long delay );

it returns an int, and honestly we love a boy who tells you where he stands 😌


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ctlr β€” Pointer to the FIP ctlr who owns the devloss workqueue. she owns it. main character energy fr fr πŸ‘‘
  • work β€” work to queue for execution. the actual task, the errand, the little guy going off to do the thing 🫢
  • delay β€” jiffies to delay the work queuing. yes, jiffies. not seconds, not vibes β€” jiffies ⏳

πŸ’– DESCRIPTION πŸ’–

Return value: 1 on success / 0 already queued / < 0 for error.

that's the whole description bestie, no cap 😭 like it's giving "minimalist" and honestly? respect. so:

  • 1 = slayed, it worked πŸ’…
  • 0 = it was already queued, no double-queueing happening here πŸ™ˆ
  • < 0 = error, we don't talk about it πŸ’€

🌈 SEE ALSO 🌈

the whole friend group is here πŸ«‚ go say hi to all of them.


okay that's the page!! this one lives in ./drivers/scsi/fcoe and it's dated October 2026 🌸 so yeah, bookmark her, cite her in your essay, put her on your fridge. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from