scsi_dev_inf...st_add_keyed(9)

💅 scsi_dev_info_list_add_keyed — NAME ✨

ok so bestie, this is the Kernel API Manual page for scsi_dev_info_list_add_keyed — and yes the header got cut off to scsi_dev_inf...st_add_keyed(9) like it's hiding its full name from us 😭 but we know who she is. She adds one dev_info list entry. That's her whole thing. And she ate.

---

🌸 SYNOPSIS 🌸

int scsi_dev_info_list_add_keyed (int compatible , char *vendor , char *model ,
                                  char *strflags , blist_flags_t flags ,
                                  enum scsi_devinfo_key key );

like… six arguments, no cap. she's high maintenance but worth it 💖

---

🎀 ARGUMENTS 🎀

• compatible — if true, you null terminate short strings. otherwise you space pad. literally that's the whole vibe check 🦋
• vendor — the vendor string, iykyk
• model — the model (product) string ✨
• strflags — an integer string
• flags — if strflags is NULL, use this flag value instead. so it's giving backup plan 💅
• key — specifies which list to use 👑

---

🦋 DESCRIPTION 🦋

okay so what she does: create and add one dev_info entry for vendor, model, strflags or flag, in the list specified by key. periodt.

if compatible is set, she adds to the tail of the list, does not space pad, and sets devinfo->compatible. slay 🌈

also important bestie: the scsi_static_device_list entries are added with compatible 1 and clfags NULL. that's just how she was raised 🫶

---

🔥 RETURN 🔥

• 0 — OK, we're so back 💜
• -error — on failure 💀

---

⭐ SEE ALSO ⭐

Kernel file ./drivers/scsi/scsi_devinfo.c plus her whole friend group:

• scsi_dev_info_list_add(9)
• scsi_dev_info_list_find(9)
• scsi_dev_info_list_add_str(9)
• scsi_get_device_flags(9)
• scsi_get_device_flags_keyed(9)
• scsi_exit_devinfo(9)
• scsi_dev_info_add_list(9)
• scsi_dev_info_remove_list(9)
• scsi_init_devinfo(9)

---

and that's the page, bestie 🎀 mwah 💋 — brought to you by ./drivers/scsi, October 2026, the one and only scsi_dev_inf...st_add_keyed(9) era ✨👑🦋