tb_cfg_request_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tb_cfg_request_get β€” Kernel API Manual ✨

Okay bestie, listen up, because this one is short but it matters. This is tb_cfg_request_get, straight out of the kernel API manual, and yeah β€” it's a one-liner function, but it's carrying the whole refcount economy on its back. πŸ‘‘


🌸 NAME 🌸

tb_cfg_request_get β€” increase the refcount of a request. That's it. That's the whole job. She's an icon, she's a legend, she does one thing and she does it flawlessly. ✨


πŸŽ€ SYNOPSIS πŸŽ€

void tb_cfg_request_get (struct tb_cfg_request *req);

Notice the void?? Nothing comes back. No return value. No exit status. She just does the thing and leaves. main character energy, honestly. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • req β€” the request whose refcount gets increased. That's the one. Hand her the request, she bumps the count, everyone goes home happy. 🫢
Ngl, that's the only argument. One param. Zero drama. Refcount goes up, no cap. πŸ”₯

🌈 SEE ALSO 🌈

If you're the kind of girl who reads the whole friend group's lore (and you should), here's the whole squad β€” all of these live in the kernel file ./drivers/thunderbolt/ctl.c:

Like, go read them. It's giving "required reading for the Thunderbolt girlies." πŸ“šβœ¨


πŸ’€ Real talk though: if you're calling this, make sure you know who's holding what β€” refcounts are serious business even when the manpage is one sentence long.

That's the whole page, bestie, we ate and left no crumbs πŸ“ β€” brought to you by the kernel docs living in ./drivers/thunderbolt, dated October 2026, in the Kernel API Manual. Mwah. πŸ’–

πŸ“¦ where this page comes from