tb_cfg_request_alloc(9)

💖 tb_cfg_request_alloc(9) 💖

Okay bestie, welcome to this Kernel API Manual page — it’s giving “small but mighty” ✨ and we’re gonna get through it together.

🌸 NAME 🌸

tb_cfg_request_alloc — allocates a new config request. That’s the whole vibe. 💅

✨ SYNOPSIS ✨

struct tb_cfg_request * tb_cfg_request_alloc (void );

🎀 ARGUMENTS 🎀

• void — no arguments. Zero. None. Nada. The function said “I need nothing from you, bestie” 🫶

🦋 DESCRIPTION 🦋

Okay so this thing is a refcounted object — when you are done with this, call tb_cfg_request_put to it. Not me reminding you, but also literally me reminding you 😭💖

⭐ RETURN ⭐

On success: a struct tb_cfg_request. Otherwise: NULL. That’s it, that’s the tea ☕✨

👑 SEE ALSO 👑

The whole crew, no cap:

• Kernel file ./drivers/thunderbolt/ctl.c
• struct tb_ctl(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_notification(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)

Later bestie! 💖 This page is from ./drivers/thunderbolt, dated October 2026, and its name is tb_cfg_request_alloc(9). Slay and goodbye 💅✨