peci_request_status(9)

💅 peci_request_status(9) — from the Kernel API Manual, bestie ✨

okay so picture this: it's giving kernel API manual, it's giving PECI energy, and you're about to read the whole page. no skimming. i'll know. 🫶

---

🌸 NAME 🌸

peci_request_status — returns -errno based on the PECI completion code. that's literally the whole vibe. 💖

---

✨ SYNOPSIS ✨

int peci_request_status (struct peci_request *req );

yes bestie, that's the exact signature, don't come for me about the spacing, i copied it character for character. 🎀

---

🦋 ARGUMENTS 🦋

• req — the PECI request that contains response data with the completion code. that's it. that's the argument. it's the main character here, honestly. 👑

---

💜 DESCRIPTION 💜

okay so listen. this bad boy reads the completion code out of your request and hands you back an -errno based on it. iconic behaviour, no notes. 🔥

BUT — and this is the part you need to internalize, bestie — it cannot be used for Ping, GetDIB and GetTemp. why? because for those commands we simply don't expect a completion code in the response. there's nothing to read. it's giving empty fridge at 2am. 😭 so don't come crying to this function for those three, fr fr.

lowkey a vibe check: use it only where a completion code is actually expected in the response. for Ping, GetDIB and GetTemp, this is not the function you're looking for. 🙈

---

🌈 RETURN 🌈

-errno 💀

that's it. that's the return value. thank you for coming to my ted talk.

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/peci/request.c
• peci_request_alloc(9)
• peci_request_free(9)

go read those too, they're the supporting cast and honestly they ate. 👑✨

---

and that's the page, bestie 🧚💫 — brought to you by ./drivers/peci, dated October 2026, and yes the page name is peci_request_status(9) in case you forgot already. slay. 💅🎀🌸