nvmem_register_notifier(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– nvmem_register_notifier(9) β€” Kernel API Manual, bestie edition πŸ’–

okay so you're in the Kernel API Manual and the main character is nvmem_register_notifier(9) ✨


🌸 NAME 🌸

nvmem_register_notifier β€” register a notifier block for nvmem events. That's the whole vibe: you hand over a notifier block, and it gets called on nvmem events. πŸ’…

✨ SYNOPSIS ✨

int nvmem_register_notifier (struct notifier_block *nb );

πŸŽ€ ARGUMENTS πŸŽ€

  • nb β€” the notifier block to be called on nvmem events. bestie, this is the one that gets pinged 🫢

πŸ’« RETURN πŸ’«

0 on success, negative error number on failure. no cap: success is literally 0, and failure hands you a negative error number 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/nvmem/core.c is the hotspot, and the whole squad is: nvmem_add_one_cell(9), nvmem_add_cells(9), nvmem_unregister_notifier(9), nvmem_register(9), nvmem_unregister(9), devm_nvmem_register(9), of_nvmem_device_get(9), nvmem_device_get(9), nvmem_device_find(9), devm_nvmem_device_put(9), nvmem_device_put(9), devm_nvmem_device_get(9), of_nvmem_cell_get(9), nvmem_cell_get(9), devm_nvmem_cell_get(9), devm_nvmem_cell_put(9), nvmem_cell_put(9), nvmem_cell_read(9), nvmem_cell_write(9), nvmem_cell_read_u8(9), nvmem_cell_read_u16(9), nvmem_cell_read_u32(9), nvmem_cell_read_u64(9), nvmem_cell_read_variable_le_u32(9), nvmem_cell_read_variable_le_u64(9), nvmem_device_cell_read(9), nvmem_device_cell_write(9), nvmem_device_read(9), nvmem_device_write(9), nvmem_add_cell_lookups(9), nvmem_del_cell_lookups(9), nvmem_dev_name(9), nvmem_dev_size(9).

mwah πŸ’‹ β€” cute sign-off from the ./drivers/nvmem crew, dated October 2026. πŸ’–

πŸ“¦ where this page comes from