clamp_t(9)

💅 clamp_t(9) — the group chat version

okay so bestie, this is a page straight out of the Kernel API Manual (yes, the clamp_t(9) one — you found it, proud of you 🫶), and I'm gonna walk you through it like we're texting at 2am.

---

✨ NAME ✨

clamp_t — return a value clamped to a given range using a given type 🎀

like... it clamps. with a type. that's the whole vibe.

---

🌸 SYNOPSIS 🌸

clamp_t (type , val , lo , hi );

four little arguments, one iconic macro. no cap. ⭐

---

🦋 ARGUMENTS 🦋

• type — the type of variable to use 💜 like, what flavour of number are we working with here
• val — current value 🔥 the one that needs to get put in its place
• lo — minimum allowable value 🍓 the floor, literally
• hi — maximum allowable value 👑 the ceiling, the limit, the final boss

---

💀 DESCRIPTION 💀

So here's the tea: this macro does no typechecking 😭 like zero, none, it does not check your vibes at the door. It just uses temporary variables of type type to make all the comparisons. That's it. That's the whole description. It's giving "small but mighty" energy. 🙈

ngl this is the part where I remind you: no typechecking means no typechecking. fr fr. the macro trusts you completely and that's a lot of pressure. 💅

---

🔥 SEE ALSO 🔥

The kernel file ./include/linux/minmax.h (yes, that's where the family lives 🧚) and honestly the whole minmax friend group ate:

min(9), max(9), umin(9), umax(9), min3(9), max3(9), min_t(9), max_t(9), min_not_zero(9), clamp(9), clamp_val(9), min_array(9), max_array(9), in_range(9), swap(9)

collect them all bestie, they're all in there 💖✨

---

mwah, that's the page! 🌈 This little love letter comes to you from ./include/linux, dated October 2026 — clamp responsibly, and remember: the typechecking was inside you all along (jk it wasn't, please be careful 💀💅).