build_changeset(9)
Okay bestie, this is build_changeset(9) from the Kernel API Manual, and yes, we're doing kernel overlay changesets today. π
β¨
πΈ NAME πΈ
build_changeset is here to populate the overlay changeset in @ovcs from @ovcs->fragments. That's the assignment, no cap. π«Ά
β¨ SYNOPSIS β¨
int build_changeset (struct overlay_changeset *ovcs );
π ARGUMENTS π
ovcsβ Overlay changeset. It's the struct we're passing in, bestie; that's the whole argument. π
π¦ DESCRIPTION π¦
Create changeset ovcs->cset so it contains the nodes and properties of the overlay device tree fragments in ovcs->fragments[]. Like, that's literally the mission. π
If an error occurs, any portions of the changeset that were successfully created will remain in ovcs->cset β no magical cleanup, they stay. π
π₯ RETURN π₯
0β success, slay. π-ENOMEMβ memory allocation failure. π-EINVALβ invalid overlay inovcs->fragments[]. π©
π SEE ALSO π
Go peek at these, iykyk:
- Kernel file
./drivers/of/overlay.c struct target(9)struct fragment(9)struct overlay_changeset(9)of_overlay_notifier_register(9)of_overlay_notifier_unregister(9)add_changeset_property(9)add_changeset_node(9)build_changeset_next_level(9)changeset_dup_entry_check(9)init_overlay_changeset(9)of_overlay_fdt_apply(9)of_overlay_remove(9)of_overlay_remove_all(9)
Final vibe check: this iconic page is from ./drivers/of, dated October 2026, and it's literally build_changeset(9). Periodt. π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms