gsm_data_kick(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… gsm_data_kick β€” poke the queue

okay so this is gsm_data_kick(9) from the Kernel API Manual, and bestie, it is exactly what it sounds like: it's the little "hey, go go go" tap on the shoulder for the queue 🫢


✨ NAME ✨

gsm_data_kick β€” poke the queue πŸ‘‰πŸ“¦


🌸 SYNOPSIS 🌸

int gsm_data_kick (struct gsm_mux *gsm );

πŸŽ€ ARGUMENTS πŸŽ€

  • gsm β€” the GSM Mux πŸ’– (this is your main character struct, the one getting kicked)

πŸ¦‹ DESCRIPTION πŸ¦‹

so the tty device literally just called us up to be like "hey, room appeared in the transmit queue" πŸ“žβœ¨ and this function is our response: ram more data into the pipe if we have any. that's it, that's the whole vibe.

but β€” and this is the important part, no cap β€” if we've been flow-stopped by a CMD_FCOFF, then we can only send messages on DLCI0 until CMD_FCON. so like, yeah, the pipe's open but the rules still apply πŸ™ˆ

⚠️ the caller must hold the gsm tx lock. not optional. not later. before you call. periodt πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/tty/n_gsm.c β€” and honestly the whole friend group is here, say hi to everybody πŸ‘‹


and that's the whole page, bestie β€” go kick some queues πŸ’œ

this lil drop came to you from ./drivers/tty, dated October 2026, and it slayed βœ¨πŸŽ€ see u in the next one πŸ¦‹

πŸ“¦ where this page comes from