ne_retrieve_reply(9)

💖 ne_retrieve_reply(9) — kernel API manual, but make it make sense 💖

okay bestie, welcome to ne_retrieve_reply(9), a page from the Kernel API Manual and honestly? it's a little one-trick pony but it eats. the whole vibe is: grab the reply that the PCI device sent back. that's it. that's the function. 🎀

---

✨ NAME ✨

ne_retrieve_reply — Retrieve reply from the PCI device. literally just go get the reply, no cap.

---

🌸 SYNOPSIS 🌸

void ne_retrieve_reply (struct pci_dev *pdev , struct
ne_pci_dev_cmd_reply *cmd_reply , size_t cmd_reply_size );

it returns void, so like… don't sit there waiting for a return value, she gives you nothing back. 🫶

---

🦋 ARGUMENTS 🦋

• pdev — the PCI device you're receiving the reply from. this is your main character, the one doing the talking. 👑
• cmd_reply — the command reply payload. this is where the goods land, bestie. 💅
• cmd_reply_size — the size of the command reply payload. yes you have to tell her how big it is, she's not psychic. 😭

---

⭐ CONTEXT ⭐

Process context, babes. and this is the important bit so listen up: this function is called with the ne_pci_dev mutex held. 🔥

like, held-held. already locked before you get here. don't be out here doing your own locking, that's not the vibe check you want to fail. 💀

---

🌈 SEE ALSO 🌈

go touch some related grass, all of these are literally right there:

• Kernel file ./drivers/virt/nitro_enclaves/ne_pci_dev.c Nitro Enclaves (NE) PCI device driver.(9)
• NE_DEFAULT_TIMEOUT_MSECS(9)
• ne_submit_request(9)
• ne_wait_for_reply(9)
• ne_reply_handler(9)
• ne_event_work_handler(9)
• ne_event_handler(9)
• ne_setup_msix(9)
• ne_teardown_msix(9)
• ne_pci_dev_enable(9)
• ne_pci_dev_disable(9)
• ne_pci_probe(9)
• ne_pci_remove(9)
• ne_pci_shutdown(9)

---

okay that's the whole page, you're officially educated 🧚💜

sign-off time: this little masterpiece lives in ./drivers/virt/nitro_enclaves, it's dated October 2026, and it answers to the name ne_retrieve_reply(9). periodt. 💖✨