Since the patch-set that included [1] there has been a policy of using
the term member for bonds, LACP, and bundle contexts.  This is
consistent with the more recently adopted policy of using the inclusive
naming word list v1 [2, 3].

This patch-set addresses several instances where the term member should be used
in vswitch.xml. It does not address all instances of alternative wording
that require code updates, which can addressed as follow-up activity.

[1] 91fc374a9c5a ("Eliminate use of term "slave" in bond, LACP, and bundle 
contexts.")
[2] df5e5cf4318a ("Documentation: Add section on inclusive language.")
[3] https://inclusivenaming.org/word-lists/

---
Simon Horman (2):
      vswitch.xml: Use member wording for bonds.
      vswitch.xml: Rename bond_active_member.

 vswitchd/bridge.c          | 6 +++---
 vswitchd/vswitch.ovsschema | 6 +++---
 vswitchd/vswitch.xml       | 6 +++---
 3 files changed, 9 insertions(+), 9 deletions(-)

base-commit: 6bdca15791ce53e15101c436d8524f2944336031

_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to