gsmld_flush_buffer(9)
π 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:
gsm_fcs_add(9),gsm_fcs_add_block(9),gsm_read_ea(9),gsm_read_ea_val(9)gsm_encode_modem(9),gsm_encode_params(9),gsm_register_devices(9),gsm_unregister_devices(9)gsm_print_packet(9),gsm_stuff_frame(9),gsm_send(9),gsm_dlci_clear_queues(9)gsm_response(9),gsm_command(9),gsm_data_alloc(9),gsm_send_packet(9)gsm_is_flow_ctrl_msg(9),gsm_data_kick(9),__gsm_data_queue(9),gsm_data_queue(9)gsm_dlci_data_output(9),gsm_dlci_data_output_framed(9),gsm_dlci_modem_output(9)gsm_dlci_data_sweep(9),gsm_dlci_data_kick(9)gsm_control_command(9),gsm_control_reply(9),gsm_process_modem(9),gsm_process_negotiation(9)gsm_control_modem(9),gsm_control_negotiation(9),gsm_control_rls(9),gsm_control_message(9)gsm_control_response(9),gsm_control_keep_alive(9),gsm_control_transmit(9),gsm_control_retransmit(9)gsm_control_send(9),gsm_control_wait(9)gsm_dlci_close(9),gsm_dlci_open(9),gsm_dlci_negotiate(9),gsm_dlci_t1(9)gsm_dlci_begin_open(9),gsm_dlci_set_opening(9),gsm_dlci_set_wait_config(9),gsm_dlci_begin_close(9)gsm_dlci_data(9),gsm_dlci_command(9),gsm_kick_timer(9),gsm_dlci_copy_config_values(9)gsm_dlci_config(9),gsm_dlci_alloc(9),gsm_dlci_free(9),gsm_dlci_release(9)gsm_queue(9),gsm0_receive_state_check_and_fix(9),gsm0_receive(9),gsm1_receive_state_check_and_fix(9)gsm1_receive(9),gsm_error(9),gsm_cleanup_mux(9),gsm_activate_mux(9)gsm_free_mux(9),gsm_free_muxr(9),gsm_alloc_mux(9),gsmld_output(9)gsmld_write_trigger(9),gsmld_write_task(9),gsmld_attach_gsm(9),gsmld_detach_gsm(9)gsmld_close(9),gsmld_open(9),gsmld_write_wakeup(9),gsmld_read(9)gsmld_write(9),gsmld_poll(9)gsm_modem_upd_via_data(9),gsm_modem_upd_via_msc(9),gsm_modem_update(9),gsm_wait_modem_change(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms