pldmfw_op_pci_match_record(9)

✨ pldmfw_op_pci_match_record ✨

okay bestie, welcome to the pldmfw_op_pci_match_record page from the Kernel API Manual 💅 this one's short and sweet, so buckle up 🎀

---

🌸 NAME 🌸

pldmfw_op_pci_match_record — check if a PCI device matches the record 👀

---

🦋 SYNOPSIS 🦋

bool pldmfw_op_pci_match_record (struct pldmfw *context , struct
       pldmfw_record *record );

---

💖 ARGUMENTS 💖

• context — the PLDM fw update structure, the main character of this whole operation ✨
• record — list of records extracted from the PLDM image 🎀

---

💫 DESCRIPTION 💫

So here's the vibe: this function determines whether the PCI device associated with this device matches the record data you provided. like, does this record belong to this device or not, yk? 🫶

How does it do it? it searches the descriptor TLVs and extracts the relevant descriptor data into a pldm_pci_record_id, and then that gets compared against the PCI device ID information 🔥 literally just matching vibes but with actual ID data, no cap.

---

👑 RETURN 👑

true if the device matches the record, false otherwise 🌈 iconic binary behavior honestly.

ngl bestie, remember it's a bool — no fancy error codes here, just yes or no 💀

---

🌸 SEE ALSO 🌸

Kernel file ./lib/pldmfw/pldmfw.c plus the whole friend group 💜:

• pldm_check_fw_space(9)
• pldm_move_fw_offset(9)
• pldm_parse_header(9)
• pldm_check_desc_tlv_len(9)
• pldm_parse_desc_tlvs(9)
• pldm_parse_one_record(9)
• pldm_parse_records(9)
• pldm_parse_components(9)
• pldm_verify_header_crc(9)
• pldmfw_free_priv(9)
• pldm_parse_image(9)
• pldm_find_matching_record(9)
• pldm_send_package_data(9)
• pldm_send_component_tables(9)
• pldm_flash_components(9)
• pldm_finalize_update(9)
• pldmfw_flash_image(9)

---

and that's the whole page, bestie 🧚 this one lives in ./lib/pldmfw and the date on it is October 2026 — go off, you understood it fr fr 💅✨🍓