devm_nvmem_device_put(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_nvmem_device_put β€” kernel API manual, but make it make sense

okay so bestie, this is devm_nvmem_device_put(9) from the Kernel API Manual, and it's honestly such a short little icon. its whole job? putting back an nvmem device you already got. that's it. that's the function. πŸŽ€


✨ NAME ✨

devm_nvmem_device_put β€” put already got nvmem device

like, you grabbed it, and now you're putting it back. balanced. symmetrical. we love a full circle moment. πŸ¦‹


🌸 SYNOPSIS 🌸

void devm_nvmem_device_put (struct device *dev , struct nvmem_device
*nvmem );

no return value, no drama β€” it's void, she simply does the thing and leaves. πŸ‘‘


πŸ’– ARGUMENTS πŸ’–

  • dev β€” the Device that uses the nvmem device. the main character of the hardware world, fr fr. 🌟
  • nvmem β€” pointer to nvmem device allocated by devm_nvmem_cell_get, that needs to be released. so like, if you got it from devm_nvmem_cell_get, this is the one you hand back. don't be out here releasing random pointers, bestie. πŸ™ˆ
lowkey important: that nvmem pointer has to come from devm_nvmem_cell_get β€” that's the origin story the docs specify. iykyk. πŸ’…

🫢 SEE ALSO 🫢

okay this is the part where the manpage flexes its entire friend group. every single one of these, no skips, no cuts:

the way this list just keeps going… she has range, she has connections, she has a whole ecosystem. 🌈


okay that's the whole page, not a single detail dropped, we ate and left no crumbs πŸ’…βœ¨

this masterpiece lives in ./drivers/nvmem, dated October 2026, and it's devm_nvmem_device_put(9) forever and always. mwah. πŸ“πŸ’œ

πŸ“¦ where this page comes from