tb_port_lane...ding_disable(9)

📦 version 7.3.1, in nixpkgs unstable

💅 tb_port_lane_bonding_disable — from the Kernel API Manual, bestie ✨

okay so first things first: this page lives in the Kernel API Manual (section 9, the kernel-functions one, iykyk) and it's all about one very specific little glow-down. let's get into it 🎀

🌸 NAME 🌸

tb_port_lane_bonding_disable — Disable bonding on port. that's it. that's the whole job. she unbonds. she separates. she lets the lanes live their truth 💔✨

🦋 SYNOPSIS 🦋

void tb_port_lane_bonding_disable (struct tb_port *port );

literally one argument, returns nothing (void), and honestly she's not here to give you feedback. no cap. 💀

🎀 ARGUMENTS 🎀

  • port — port to disable 🙈 that's the port whose bonding is getting turned off. that's the whole vibe check.

💖 DESCRIPTION 💖

so what actually happens? Disable bonding by setting the link width of the port and the other port in case of dual link port. yes bestie, the other port too — if you're running a dual link situation, both of them get the treatment. it's giving "we're doing this together or not at all" 🫶✨

no return value, no drama, no exit status. she just does the thing and dips 🌈

👑 SEE ALSO 👑

okay this part is a whole friend group, like genuinely the entire thunderbolt clique got invited. the kernel file in question is ./drivers/thunderbolt/switch.c, and then everybody else:

like I said. the whole group chat. 🔥

ngl, nothing here is dangerous or deprecated — she's just a tidy little void function doing lane-bonding breakup duty 💔 but like, read the neighbors too, they're all in the same file for a reason. 🧚

and that's the page, bestie! itty bitty sign-off for you: this one comes from the source dir ./drivers/thunderbolt and it's dated October 2026, filed under tb_port_lane...ding_disable(9) — yes the title is literally truncated like that in the header, don't come for me, I didn't name her 🙈💜 slay, go unbond some lanes 🦋✨

📦 where this page comes from