hvc_iucv_msg_pending(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ hvc_iucv_msg_pending(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’– β€” this one's a lil kernel function page and it's honestly so specific and I'm obsessed. let's get into it 🫢


🌸 NAME 🌸

hvc_iucv_msg_pending β€” the IUCV handler that deals with an incoming IUCV message. it's giving "front desk receptionist for messages" energy ngl πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

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

so yeah, it returns void (no return value, she just does her thing ✨) and takes two args. slay.


πŸŽ€ ARGUMENTS πŸŽ€

  • path β€” the pending path, and it's a struct iucv_path. literally the path in question πŸ’«
  • msg β€” a pointer to the IUCV message. the message in question πŸ“¨

⭐ DESCRIPTION ⭐

so what does she do? the function takes an incoming message and puts it on the input queue so it can be processed later β€” by hvc_iucv_get_chars / hvc_iucv_write, iykyk πŸ‘‘

BUT β€” and this is the important part, bestie β€” if the tty has not yet been opened, the message gets rejected. no tty open? no message for you πŸ™ˆ periodt.

Locking: struct hvc_iucv_private->lock πŸ”’ (that's the lock involved, keep that in mind fr fr)


πŸ’œ SEE ALSO πŸ’œ

like, that's the whole squad, all 30-ish of them, no cap 🌈


πŸ’€ friendly reminder: if the tty isn't open yet, the message is rejected. don't come for her, she's just following the rules.

k that's the page!! this one came from ./drivers/tty/hvc and it's dated October 2026 β€” mwah, bye bestie πŸ’‹πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from