fc_rtv_fill(9)

📦 version 7.3.1, in nixpkgs unstable

✨ fc_rtv_fill(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 this one's a tiny lil' page from the kernel's networking corner — she's short, she's sweet, and honestly she's giving "I'm in the group chat but I only sent one emoji" energy.

🌸 NAME 🌸

fc_rtv_fill — fill in an RTV (read timeout value) request frame. that's it. that's the whole job. no cap 🫶

🦋 SYNOPSIS 🦋

void fc_rtv_fill (struct fc_lport *lport , struct fc_frame *fp );

the way that signature just sits there — void return, so she's not giving you anything back, she's a do-the-thing-and-dip kinda function 💅

🎀 ARGUMENTS 🎀

  • lport — -- undescribed -- 🙈 yeah. the doc gave us literally nothing on this one. it's a struct fc_lport *, that's all we know, so we're not gonna pretend we know more than the manual does, fr fr.
  • fp — -- undescribed -- 😭 same situation. struct fc_frame *, and the manpage just politely declines to elaborate. iconic behaviour honestly. not me making up facts — never 💀.
bestie note: both of these are marked -- undescribed -- in the original. do not come for me asking what they do, the page itself isn't telling. lowkey mysterious of her 🌈

💜 SEE ALSO 💜

she hangs out in the kernel file ./drivers/scsi/libfc/fc_encode.h, and here's her whole friend group — the other _fill girlies ✨ ngl they all got the same job, different frames:

that's thirteen siblings btw 🔥 whole squad of fill functions, and fc_rtv_fill is right there in the family photo 💖

⭐ reminder: this page has no DESCRIPTION, no OPTIONS, no return-value section, and no errors listed — so if you were waiting for those, she simply didn't write them. iykyk 😌

mwah 💋 this one comes to you from the source tree at ./drivers/scsi/libfc and it's dated October 2026 — that's the whole footer, no version string, no copyright line, nothing else hiding down there. slay, go encode a read timeout value frame, you got this 🧚💜

📦 where this page comes from