qed_vf_get_num_cids(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ qed_vf_get_num_cids β€” okay so this is a qed_vf_get_num_cids(9) situation, bestie

Man page energy, section 9, kernel API vibes. Strap in, this one's short and sweet πŸ“


✨ NAME ✨

qed_vf_get_num_cids β€” literally just gets the number of available connections [both Rx and Tx] for a VF. That's it. That's the whole gig πŸ’…


🌸 SYNOPSIS 🌸

void qed_vf_get_num_cids (struct qed_hwfn *p_hwfn , u8 *num_cids );

Look at her. Returns void. Doesn't even give you a status code. Iconic, unbothered, no notes πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • p_hwfn β€” the HW device data. Like, the hardware's whole personality file 🫢
  • num_cids β€” the allocated number of connections. It gets written into this pointer, so yeah, you're handing over a u8 * and trusting the ride πŸ™ˆ

⭐ RETURN ⭐

Void. Nothing. Zero. Nada. She does the work and dips, no receipts, no follow-up text πŸ’€ (the actual answer lands in num_cids, iykyk)


πŸ”₯ SEE ALSO πŸ”₯

Okay this list is a whole friend group, so let's do a vibe check on everybody πŸ‘―β€β™€οΈ

Thirty besties, and yes, the double-underscore girlies are in the chat too πŸ’–


Ngl there's no exit status, no signal, no env vars, no bugs section here β€” she's a void function in a header file, and the whole page is babygirl. Don't go looking for drama that isn't there 🌈

And that's the page, bestie! Sourced straight out of ./drivers/net/ethernet/qlogic/qed, stamped October 2026, living her best life in the Kernel API Manual, section qed_vf_get_num_cids(9). Slay, bye! πŸŽ€βœ¨

πŸ“¦ where this page comes from