cpufreq_cpu_put(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cpufreq_cpu_put(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so real talk, this one is from the Kernel API Manual and it's literally the polite goodbye of the cpufreq world. You grabbed a policy with cpufreq_cpu_get, you did your little thing, and now you gotta give it back. Rude not to. πŸ™ˆ


✨ NAME ✨

cpufreq_cpu_put β€” decrement that kobject usage counter for the cpufreq policy, bestie. It's giving "return what you borrowed" energy and honestly? Iconic. 🫢


🌸 SYNOPSIS 🌸

void cpufreq_cpu_put (struct cpufreq_policy *policy );

That's it. That's the whole vibe check. No return value, no drama, just vibes and a pointer. πŸ’œ


πŸ¦‹ ARGUMENTS πŸ¦‹

  • policy β€” the cpufreq policy that cpufreq_cpu_get handed you. Like, specifically the one you got from cpufreq_cpu_get. Don't be out here passing random policies, that's not the move. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is a whole friend group and you're gonna meet all of them. no cap, every single one:

Like I said. Entire friend group. All of them are (9) and all of them are slaying in their own way. πŸ’…βœ¨


ngl if you call cpufreq_cpu_get and then forget to call cpufreq_cpu_put, the counter just sits there. Forever. Haunting you. Main character behaviour but make it a leak. 🫠 So put it back, bestie.

πŸ’– that's the page!! shoutout to the source tree at ./drivers/cpufreq, dated October 2026 β€” mwah, love that for us πŸŽ€πŸ’–

πŸ“¦ where this page comes from