fcoe_ctlr_device_add(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fcoe_ctlr_device_add(9) — like, the Kernel API Manual page, bestie 🎀

Okay so picture this: it's a (9) man page straight out of the Kernel API Manual, and the star of the show is fcoe_ctlr_device_add. Buckle up, we're learning sysfs today ✨

🌸 NAME 🌸

fcoe_ctlr_device_add — Add a FIP ctlr to sysfs 🫶

✨ SYNOPSIS ✨

struct fcoe_ctlr_device * fcoe_ctlr_device_add (struct device *parent ,
struct fcoe_sysfs_function_template *f , int priv_size );

That's the whole signature, no cap 💖

🦋 ARGUMENTS 🦋

  • parent — The parent device to which the fcoe_ctlr instance should be attached. It's giving "who's your mom" energy, fr fr 👑
  • f — The LLD's FCoE sysfs function template pointer. Iconic little template, we love her 💅
  • priv_size — Size to be allocated with the fcoe_ctlr_device for the LLD. Extra room, extra slay 🎀

🌈 DESCRIPTION 🌈

So basically ✨ this routine allocates a FIP ctlr object with some additional memory for the LLD. Then the FIP ctlr is initialized, added to sysfs, and — the main character moment — attributes are added to it. Obsessed. It's a whole three-step glow-up: allocate → initialize → sysfs + attributes 💜

🔥 SEE ALSO 🔥

Kernel file ./drivers/scsi/fcoe/fcoe_sysfs.c — the mothership 🧚

💖 That's the whole page, bestie — go forth and add your FIP ctlr to sysfs. iykyk 😭

From ./drivers/scsi/fcoe, dated October 2026, and signed fcoe_ctlr_device_add(9) — catch you in the next man page, mwah 🫶💅✨

📦 where this page comes from