tb_domain_ap...e_switch_key(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

ok so tb_domain_approve_switch_key — it approves a switch and adds the key, bestie ✨

this is the <pink>tb_domain_ap...e_switch_key(9)</pink> page from the Kernel API Manual, and we're gonna get through it together, no cap 🫶

🦋 SYNOPSIS 🦋

int tb_domain_approve_switch_key (struct tb *tb , struct tb_switch *sw );

like, it returns an int, and it takes two things. that's the whole vibe check 💅

🌸 ARGUMENTS 🌸

  • tb — the Domain the switch belongs to 👑 (it's the bigger picture, the container, the main character)
  • sw — the Switch to approve ⭐ (this is the one getting the glow-up)

🎀 DESCRIPTION 🎀

okay so listen 👀 — for switches that support secure connect, this function does two things, in order, and the order matters fr fr:

  1. it first adds the key to the switch NVM using connection manager specific means 🔑
  2. if adding the key is successful, the switch is approved and connected ✅

the way that it's literally a "add the key, then approve" pipeline... iconic. it's giving two-step slay. but note the conditional, bestie: no successful key-add, no approval — periodt 💀

🌈 RETURN 🌈

  • 0 on success 🥳
  • negative errno in case of failure 😭

that's it. that's the return. simple, clean, no notes.

🧚 SEE ALSO 🧚

Kernel file ./drivers/thunderbolt/domain.c 📁

and the whole friend group, in this exact order:

lowkey a whole squad of thunderbolt domain functions, and every single one of them is invited to the group chat 💜

and that's the page! sign-off time 🫶 this one lives in ./drivers/thunderbolt, dated October 2026, and it's the tb_domain_ap...e_switch_key(9) manual page — go forth and approve those switches, bestie 💅✨🎀

📦 where this page comes from