fcoe_fdmi_info(9)

💅 fcoe_fdmi_info — from the Kernel API Manual, bestie ✨

okay so we're doing a <pink>kernel API</pink> page today, specifically fcoe_fdmi_info(9) from the Kernel API Manual, and honestly? it's a short one. a little snack. a mini cupcake of a function. but it still matters, so let's get into it 🍓

---

🌸 NAME 🌸

fcoe_fdmi_info — get <purple>FDMI</purple> related info from the net device for <cyan>SW FCoE</cyan> 💫

like, that's the whole job. it goes and grabs FDMI stuff off the net device so the software FCoE side knows what's up. iykyk.

---

🎀 SYNOPSIS 🎀

void fcoe_fdmi_info (struct fc_lport *lport , struct net_device *netdev );

it returns <italic>void</italic> bestie. nothing comes back. it just does the thing and leaves. main character energy fr fr 👑

---

🦋 ARGUMENTS 🦋

• lport — the local port that's associated with the net device. your <lavender>fc_lport</lavender> babe, the one holding the mutex we're about to gossip about.
• netdev — the associated net device. the matching struct net_device, hand in hand with lport like they're matching Halloween costumes 🫶

---

✨ DESCRIPTION ✨

okay here's the one rule, and it's giving <red>strict</red>:

you must call this <hotpink>after</hotpink> fcoe_shost_config — no cap, not before, not "eh it'll probably be fine" before. because this function <yellow>uses the local port mutex</yellow>, and if you roll up too early you're gonna have a bad time 😭

so: fcoe_shost_config first, then fcoe_fdmi_info. order matters. it's a whole sequence. respect the sequence 💅

not me warning you again: after fcoe_shost_config. that's the vibe check. pass it or don't call this at all 🙈

---

🌈 SEE ALSO 🌈

where to look next, all the lore, the whole friend group — kernel file ./drivers/scsi/fcoe/fcoe.c plus fcoe_interface_setup(9), fcoe_interface_create(9), fcoe_interface_remove(9), fcoe_interface_cleanup(9), fcoe_fip_recv(9), fcoe_fip_vlan_recv(9), fcoe_port_send(9), fcoe_fip_send(9), fcoe_update_src_mac(9), fcoe_get_src_mac(9), fcoe_lport_config(9), fcoe_netdev_config(9), fcoe_shost_config(9), fcoe_oem_match(9), fcoe_em_config(9), fcoe_if_destroy(9), fcoe_ddp_setup(9), fcoe_ddp_target(9), fcoe_ddp_done(9), fcoe_if_create(9), fcoe_if_init(9), fcoe_if_exit(9), fcoe_rcv(9), fcoe_alloc_paged_crc_eof(9), fcoe_xmit(9), fcoe_filter_frames(9), fcoe_recv_frame(9), fcoe_receive_work(9), fcoe_dev_setup(9), fcoe_dev_cleanup(9), fcoe_device_notification(9), fcoe_disable(9), fcoe_enable(9), fcoe_ctlr_enabled(9), fcoe_ctlr_mode(9), fcoe_destroy(9), fcoe_destroy_work(9), fcoe_match(9), fcoe_dcb_create(9), _fcoe_create(9), fcoe_create(9), fcoe_ctlr_alloc(9), fcoe_link_ok(9), fcoe_percpu_clean(9), fcoe_reset(9), fcoe_hostlist_lookup_port(9), fcoe_hostlist_lookup(9), fcoe_hostlist_add(9), fcoe_hostlist_del(9), fcoe_init(9), fcoe_exit(9), fcoe_flogi_resp(9), fcoe_logo_resp(9), fcoe_vport_create(9), fcoe_vport_destroy(9), fcoe_vport_remove(9), fcoe_vport_disable(9), fcoe_set_vport_symbolic_name(9), fcoe_set_port_id(9).

that's a lot of friends but every single one of them is invited to the party 🎉

---

and that's the page!! it lives over in ./drivers/scsi/fcoe, it's stamped <mint>October 2026</mint>, and its name is fcoe_fdmi_info(9) — read it, love it, call it after fcoe_shost_config 💖🦋✨