hvc_iucv_msg_complete(9)

📦 version 7.3.1, in nixpkgs unstable

✨ hvc_iucv_msg_complete ✨

okay bestie, so this is a page from the Kernel API Manual and it's literally about hvc_iucv_msg_complete — yeah, the name's a mouthful, iykyk 💅 it's the IUCV handler that takes care of message completion.

🌸 NAME 🌸

hvc_iucv_msg_complete — the IUCV handler that handles processing when a message finishes, no cap 🎀

🦋 SYNOPSIS 🦋

void hvc_iucv_msg_complete (struct iucv_path *path , struct iucv_message
*msg );

like, it returns void and it takes two args, that's it, periodt ✨

💖 ARGUMENTS 💖

  • path — the pending path, and yes it's a struct iucv_path 🫶
  • msg — a pointer to the IUCV message 👑

💅 DESCRIPTION 💅

so this function gets called when delivering a message is done, and its whole job is to remove that message from the outqueue. iconic behavior honestly 🌈

and you can find extra delivery info in msg->audit, which is giving very much detective energy 🔥 — here's the tea:

  • rejected messages show up as 0x040000 (IPADRJCT) 😭
  • purged messages show up as 0x010000 (IPADPGNR) 💀

Locking: struct hvc_iucv_private->lock 🔒 bestie, do not forget the lock, fr fr

⭐ SEE ALSO ⭐

so there's a whole friend group here, the kernel file ./drivers/tty/hvc/hvc_iucv.c plus all of these cuties 🧚:

bestie pls actually go read the file at ./drivers/tty/hvc/hvc_iucv.c if you wanna see the whole vibe in context 🫶

and that's the page!! it lives under ./drivers/tty/hvc, dated October 2026, and it's the hvc_iucv_msg_complete(9) manual page — slay, you're welcome, go be a main character in kernel space 👑✨🦋

📦 where this page comes from