reset_contr...k_get_shared(9)

📦 version 7.3.1, in nixpkgs unstable

💅 reset_control_bulk_get_shared — Kernel API Manual, bestie edition

okay so you're in the Kernel API Manual ✨ and this page is about reset_control_bulk_get_shared(9). Yes the header truncates it as reset_contr...k_get_shared(9), that's just the terminal being dramatic, don't panic 🫶

🌸 NAME 🌸

reset_control_bulk_get_shared — lookup and obtain shared references to multiple reset controllers. plural. a whole squad of them. not just one. 💅

✨ SYNOPSIS ✨

int reset_control_bulk_get_shared (struct device *dev , int num_rstcs ,
       struct reset_control_bulk_data *rstcs );

it returns an int — that's your vibe check at the end (spoiler: 0 = slay, anything else = 😭)

🎀 ARGUMENTS 🎀

  • dev — the device to be reset by the controller. the main character, basically 👑
  • num_rstcs — number of entries in the rstcs array. gotta tell it how many besties are coming to the function 🧚
  • rstcs — array of struct reset_control_bulk_data with reset line names set. like, you set the names first, that's the assignment bestie 📝

🦋 DESCRIPTION 🦋

Fills the rstcs array with pointers to shared reset controls and returns 0, or an IS_ERR condition containing errno.

so like, it does the filling-in for you — very generous of it, honestly 🔥 — and then it tells you how it went. success = 0. failure = an IS_ERR condition holding errno, i.e. the function hands you an error and you should absolutely check for it and not just assume everything's fine 🙈

ngl, always check your return value. IS_ERR conditions are not a vibe to ignore 💀

💀 SEE ALSO 💀

the whole extended fam. every single one. no cap, I'm not skipping anybody 🫶

✨ that's the whole page bestie, you ate ✨

this lil guy lives in ./include/linux (that's where the source hangs out, iykyk) and the page is dated October 2026 🌈 so it's basically from the future. iconic. mwah 💋 🎀

📦 where this page comes from