gsmld_flush_buffer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… gsmld_flush_buffer(9) β€” kernel API manual, but make it make sense

okay so bestie, we're in the kernel API manual today and this page is about gsmld_flush_buffer. yes that's a mouthful, no you don't have to say it out loud. it's a tiny function with one job and honestly? it does it flawlessly. πŸŽ€


✨ NAME ✨

gsmld_flush_buffer β€” clean input queue

like, it empties the input queue. that's the whole personality. 🧹✨


🌸 SYNOPSIS 🌸

void gsmld_flush_buffer (struct tty_struct *tty );

returns nothing (void, icon behavior), takes one arg, moves on with its life πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • tty β€” the terminal device. that's it, that's the argument. it's the tty you're flushing, bestie 🫢

πŸ’– DESCRIPTION πŸ’–

so what it does: it flushes the input buffer. periodt. 🧚

when does it get called? two moments, and both are extremely "we're wrapping up here" energy:

  • when the line discipline is being closed 😭
  • when the tty layer wants the buffer flushed (eg at hangup) πŸ’€

like it's giving cleanup crew, it's giving "everyone out of the pool." no data left behind. πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/tty/n_gsm.c β€” and bestie, the friend group is LARGE. iykyk. every single one of these is invited to the function party:


ngl this whole page is like four lines of facts, but the SEE ALSO section ate and left no crumbs πŸ’…

and that's the whole page, bestie! 🫢

sign-off time πŸŽ€ this little gem lives in ./drivers/tty, dated October 2026, and it was brought to you by the gsmld_flush_buffer(9) manual page itself β€” go drink some water and flush your own buffers πŸ’–βœ¨

πŸ“¦ where this page comes from