dmi_walk(9)

💅 dmi_walk(9) — like, the kernel API manual bestie 💅

okay so this is dmi_walk(9) from the Kernel API Manual and honestly? it's giving "short but iconic." let's get into it ✨

---

🌸 NAME 🌸

dmi_walk — walk the DMI table and get called back for every record 🫶

like. you show up, you stroll through the DMI table, and for every single record the kernel hits you up on your callback. that's the whole vibe.

---

🎀 SYNOPSIS 🎀

int dmi_walk (void (*decode)(const struct dmi_header *, void *) , void
*private_data );

look at her. one function, two args, zero drama. 💅

---

🦋 ARGUMENTS 🦋

• decode — the callback function 💖 this is the one that gets called back for every record on the walk, so make it count bestie.
• private_data — private data that gets passed straight to the callback function. it's your data, she's just holding it for you 🎀

---

⭐ DESCRIPTION ⭐

so what does she actually do? she returns 0 on success 💚 — slay, we love a clean return.

but if DMI is not selected or not present, you get -ENXIO 😭 and if DMI walking fails, you get a different negative error code. so yeah, negative numbers = something's off, check yourself before you wreck yourself fr fr.

no cap: 0 means we ate. anything negative means the walk didn't go how we wanted 🙈

---

🌈 SEE ALSO 🌈

okay this is the friend group, they all come as a package iykyk 👑

• Kernel file ./drivers/firmware/dmi_scan.c
• dmi_setup(9)
• dmi_matches(9)
• dmi_is_end_of_table(9)
• dmi_check_system(9)
• dmi_first_match(9)
• dmi_get_system_info(9)
• dmi_name_in_serial(9)
• dmi_name_in_vendors(9)
• dmi_find_device(9)
• dmi_get_date(9)
• dmi_get_bios_year(9)
• dmi_match(9)
• dmi_memdev_type(9)
• dmi_memdev_handle(9)

---

and that's the page bestie 🫶 brought to you by ./drivers/firmware, dated October 2026, and she's literally called dmi_walk(9). periodt. 💜