mux_control_deselect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mux_control_deselect β€” bestie, it's time to let go

Okay so this is a page from the Kernel API Manual, and it's about the part where you stop hogging the multiplexer. Yes, the goodbye. The release. The "okay ily bye" moment 🫢


✨ NAME ✨

mux_control_deselect β€” Deselect the previously selected multiplexer state.


πŸŽ€ SYNOPSIS πŸŽ€

int mux_control_deselect(struct mux_control *mux);

🌸 ARGUMENTS 🌸

  • mux β€” the mux-control you're deselecting. That's the one. Say bye to it πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the rule, and it's not a vibe, it's a requirement, no cap: for every single successful call you make to either mux_control_select or mux_control_try_select, you owe exactly one call to mux_control_deselect. Every. Single. One. It's giving "you took it out of the box, you put it back" energy ✨

Like, the select and the deselect are a matched set, iykyk. Don't leave it unbalanced, that's not the move πŸ™ˆ


πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰
  • a negative errno on error 😭

And here's the tea: an error can only occur if the mux has an idle state. That's the only door it can come through, literally.

⚠️ Big important thing though, bestie: even if an error happens, the mux-control is still unlocked and is thus free for the next access. So like, the error isn't holding the mux hostage or anything. It's free. It's fine. We move πŸ’…

🌈 SEE ALSO 🌈

The whole friend group πŸ’– β€” go say hi:


Periodt. That's the whole page, and it lives in ./drivers/mux, dated October 2026, under the Kernel API Manual banner 🌸 Go forth and deselect responsibly, bestie β€” one deselect per successful select, always, fr fr πŸ’œπŸ‘‘

πŸ“¦ where this page comes from