Rename the reverse_name to reverse_names in associations.
It will allow two different associations with the same name and
different reverse_names.
For example:
associations:
- name: forward_name
reverse_names:
- reverse_name_A
- reverse_name_B
required_endpoint_interfaces:
- endpoint
Will have two associations:
- [forward_name, reverse_name_A, endpoint]
- [forward_name, reverse_name_B, endpoint]
Change-Id: Ia01ae59b7dba1556e7c7f8e56ccede47d623c1a1
Signed-off-by: Zhenwei Chen <zhenweichen0207@gmail.com>
diff --git a/yaml/xyz/openbmc_project/Inventory/Item/PCIeSlot.interface.yaml b/yaml/xyz/openbmc_project/Inventory/Item/PCIeSlot.interface.yaml
index 5c0f0d5..224b2d6 100644
--- a/yaml/xyz/openbmc_project/Inventory/Item/PCIeSlot.interface.yaml
+++ b/yaml/xyz/openbmc_project/Inventory/Item/PCIeSlot.interface.yaml
@@ -104,6 +104,7 @@
Objects that implement PCIeSlot can optionally implement the
upstream_processor association to provide a link back to a PCIe host
bridge or on-processor PCIe root complexes.
- reverse_name: associated_pcie_slots
+ reverse_names:
+ - associated_pcie_slots
required_endpoint_interfaces:
- xyz.openbmc_project.Inventory.Item.Cpu