tb_cfg_ack_notification(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ tb_cfg_ack_notification(9) ✨

okay bestie, this is from the Kernel API Manual and it's literally the page for tb_cfg_ack_notification 🫢

πŸ’– NAME πŸ’–

tb_cfg_ack_notification β€” Ack notification ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

int tb_cfg_ack_notification (struct tb_ctl *ctl , u64 route , const
       struct cfg_error_pkg *error );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctl β€” Control channel to use
  • route β€” Router that originated the event
  • error β€” Pointer to the notification package

🌸 DESCRIPTION 🌸

Call this as a response for a non-plug notification to ack it. That's the whole vibe πŸ’…

⭐ RETURN ⭐

0 on success, negative errno otherwise.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/thunderbolt/ctl.c, struct tb_ctl(9), tb_cfg_request_alloc(9), tb_cfg_request_get(9), tb_cfg_request_put(9), tb_cfg_request(9), tb_cfg_request_cancel(9), tb_cfg_request_sync(9), tb_ctl_alloc(9), tb_ctl_free(9), tb_ctl_start(9), tb_ctl_stop(9), tb_cfg_ack_plug(9), tb_cfg_reset(9), tb_cfg_read_raw(9), tb_cfg_write_raw(9), tb_cfg_get_upstream_port(9)


xoxo, from the ./drivers/thunderbolt source tree, dated October 2026 β€” slay and read ur man pages πŸ’œβœ¨

πŸ“¦ where this page comes from