qed_sp_destroy_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 qed_sp_destroy_request β€” NAME 🌸

ok so bestie, gather round: qed_sp_destroy_request is the function that returns a SPQ entry to the pool, and it also frees the entry if allocated. πŸŽ€

and like, the important part β€” the part you literally cannot skip β€” is when you call it: it should be called on in error flows after initializing the SPQ entry and before posting it. that's the whole vibe check. error path, after init, before post. periodt. πŸ’…

this page lives in the Kernel API Manual, iykyk.


✨ SYNOPSIS ✨

void qed_sp_destroy_request (struct qed_hwfn *p_hwfn , struct
qed_spq_entry *p_ent );

yeah she takes two args and gives you nothing back. void city. πŸ¦‹


🫢 ARGUMENTS 🫢

  • p_hwfn β€” the HW device data. like, the hardware handler situation. that one. πŸ”₯
  • p_ent β€” the Ent. yes, that's genuinely all the original says. "Ent." iconic minimalism, no notes. πŸ™ˆ

⭐ RETURN ⭐

Void. that's it. nothing comes back. she simply does the thing and leaves. πŸ’€


🧚 SEE ALSO 🧚

first up, the literal file, no cap:

  • Kernel file ./drivers/net/ethernet/qlogic/qed/qed_sp.h

and then the whole bestie squad of related calls, in order, every single one of them πŸ‘‘:

🌈 friendly reminder bestie: this one is an error-flow friend. after initializing the SPQ entry, before posting it. don't be out here calling her at random times, ok? 😭

and that's the whole page, mwah πŸ’– this gem ships out of ./drivers/net/ethernet/qlogic/qed, dated October 2026, and it's literally titled qed_sp_destroy_request(9) β€” slay, go free those entries, ily, bye πŸ“βœ¨

πŸ“¦ where this page comes from