qed_qm_init_pf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qed_qm_init_pf β€” the Sparkle Edition

bestie, welcome to the qed_qm_init_pf(9) page from the Kernel API Manual ✨ this one lives in the qlogic qed corner of the kernel and it's honestly short and sweet, so let's get into it πŸŽ€

🌸 NAME 🌸

qed_qm_init_pf β€” initializes the QM PF phase, per path πŸ’« (yes the original header spells it "Initailze", we love a typo era, but the job is the same: init the QM PF phase, per path, no cap)


✨ SYNOPSIS ✨

void qed_qm_init_pf (struct qed_hwfn *p_hwfn , struct qed_ptt *p_ptt ,
bool is_pf_loading );

So she takes three things and gives you back literally nothing. Iconic behavior honestly πŸ’…

🫢 ARGUMENTS 🫢

  • p_hwfn β€” the HW device data, aka the whole hardware function vibe check πŸ–₯️✨
  • p_ptt β€” P_ptt. That's it. That's the description. We respect the minimalism πŸŽ€
  • is_pf_loading β€” is the PF pending? πŸ‘€ yes/no, is it still loading bestie

⭐ RETURN ⭐

Void. β€” nothing comes back. Not a value, not a struct, not even a little guy. She's void, she's mysterious, she's giving main character energy πŸ¦‹

ngl, a void return means if you were hoping to check a status code, this is not the function for you 😭 the info goes in through the arguments and that's the whole story.

🧚 SEE ALSO 🧚

Kernel file ./drivers/net/ethernet/qlogic/qed/qed_cxt.h 🌈 and literally all her friends:

go read those too, they ate πŸ”₯


and that's the page, bestie 🫢 she's from ./drivers/net/ethernet/qlogic/qed, dated October 2026, and she is, was, and always will be qed_qm_init_pf(9) πŸ’– periodt πŸŽ€

πŸ“¦ where this page comes from