fc_els_fill(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 fc_els_fill(9) 🦋

okay bestie, you've opened the Kernel API Manual page for fc_els_fill(9), and it's giving short, mysterious, lowkey iconic. We're keeping every fact exactly where it belongs — the vibe is new, the details are not. ✨

💖 NAME 💖

fc_els_fill — fill in an ELS request frame 💅

✨ SYNOPSIS ✨

int fc_els_fill (struct fc_lport *lport , u32 did , struct fc_frame *fp
       , unsigned int op , enum fc_rctl *r_ctl , enum fc_fh_type *fh_type );

🎀 ARGUMENTS 🎀

Okay so the original ARGUMENTS section is literally six lines of -- undescribed --, and I am not gonna invent lore just to make it cute. Here's the whole cast, exactly as the page gives it:

  • lport — -- undescribed -- (mystery main character energy 🕵️‍♀️)
  • did — -- undescribed -- (the manpage said nothing, so neither will I 🙈)
  • fp — -- undescribed -- (another little enigma 🎀)
  • op — -- undescribed -- (no cap, that's the whole description 💀)
  • r_ctl — -- undescribed -- (still a mystery, bestie 🦋)
  • fh_type — -- undescribed -- (and that's the last one, periodt 💜)
bestie, this is not me being lazy — every single argument on the original page is literally marked -- undescribed --. We respect the mystery. 🫶

🌈 SEE ALSO 🌈

Kernel file: ./drivers/scsi/libfc/fc_encode.h — and the whole function squad is right here:

signing off from ./drivers/scsi/libfc with an October 2026 timestamp, still repping fc_els_fill(9) — bye bestie, mwah 💜🫶 periodt.

📦 where this page comes from