ap_sm_recv(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ap_sm_recv(9) — the Kernel API Manual, but make it cute

okay so bestie, welcome to ap_sm_recv ✨ this is a page from the Kernel API Manual, section 9 (that's the kernel-API section, iykyk), and it's short but it matters. Let's get into it 🫶

🌸 NAME 🌸

ap_sm_recv — receive pending reply messages from an AP queue, but do not change the state of the device 💖

like. it grabs the replies. it does not touch the device's state. that's the whole vibe check and it passes 🎀

🦋 SYNOPSIS 🦋

struct ap_queue_status ap_sm_recv (struct ap_queue *aq );

yep that's it, one function, one argument, returns a struct ap_queue_status. no cap. 🌈

⭐ ARGUMENTS ⭐

  • aq — pointer to the AP queue 👑 nothing more, nothing less, just a pointer to the queue you're working with.

💜 DESCRIPTION 💜

calls it, and it returns one of these three bad boys: AP_SM_WAIT_NONE, AP_SM_WAIT_AGAIN, or AP_SM_WAIT_INTERRUPT 💅

that's literally the whole description, bestie — those are the return values, those are the options, and that's the tea 🍓

ok real talk: the manpage does not say which one you'll get or when. it just says these are the three possible returns. don't go inventing extra behaviour, that's not the move 🙈

🔥 SEE ALSO 🔥

the source file lives at ./drivers/s390/crypto/ap_queue.c in the kernel tree (under ./drivers/s390/crypto), and the squad of related manpages is:

like, go read all of them, they're the friend group and they all ate 💀👑

and that's the page!! mwah 💋

sign-off time 🎀 this one comes to you from the kernel source tree path ./drivers/s390/crypto, dated October 2026, and the page itself is ap_sm_recv(9) from the Kernel API Manual. go forth and receive those pending replies, bestie — but remember, leave the device state exactly where you found it 🦋✨

📦 where this page comes from