STRUCT OF_CHANGESET_ENTRY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct of_changeset_entry(9)

okay so this is the struct of_changeset_entry(9) page from the Kernel API Manual, and honestly? it's a little baddie of a struct that quietly holds everything together. let's get into it 🫢


✨ NAME ✨

struct of_changeset_entry β€” holds a changeset entry. that's it, that's the whole name, no notes πŸ’…


🌸 SYNOPSIS 🌸

struct of_changeset_entry {
    struct list_head node;
    unsigned long action;
    struct device_node *np;
    struct property *prop;
    struct property *old_prop;
};

πŸŽ€ Members πŸŽ€

  • node β€” the list_head for the log list. it's the little link that keeps this entry chained up with all its siblings.
  • action β€” the notifier action. this is what went down, recorded as an unsigned long.
  • np β€” pointer to the device node that got affected. main character node, honestly.
  • prop β€” pointer to the property that got affected.
  • old_prop β€” holds a pointer to the original property. yes bestie, we keep the receipt πŸ“

πŸ¦‹ Description πŸ¦‹

so every single modification of the device tree that happens during a changeset gets held in a list of of_changeset_entry structures. literally every one, no skipping.

and why do we do this? because that way we can recover from a partial application, or we can revert the changeset. it's giving "undo button but make it kernel-level" 😭✨

ngl this is the safety net of the whole operation β€” if the changeset goes sideways mid-apply, these entries are your way back.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/linux/of.h and friends β€” the whole squad, no cap:


and that's the whole page, bestie β€” stay iconic, keep your entries linked, and remember: always hold onto old_prop πŸ’œ

this cutie lives in ./include/linux, dated October 2026, and it goes by struct of_changeset_entry(9). mwah πŸ’‹

πŸ“¦ where this page comes from