diff options
author | Thomas Haller <thaller@redhat.com> | 2015-08-06 13:39:33 +0200 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2015-11-24 14:43:08 +0100 |
commit | b6b41ffcb3da51dea0c98307b804e533ef426485 (patch) | |
tree | 7c565e1f0845a81ae30d66f024971f189750ac5d /data | |
parent | 3ebf08e736df7bf97c2390ca2f708092d49dca52 (diff) | |
download | NetworkManager-dcbw/devices-for-all-7.tar.gz |
device: modify handling master devicedcbw/devices-for-all-7
I found the handling of the master-device very confusing because it was
unclear who sets priv->master, and when it should be set.
Now:
- priv->master should be always set when a device is added to the
master and vice-versa.
- priv->master gets now only cleared by nm_device_slave_release_from_master().
It only gets set by device_recheck_slave_status() and master_ready() --
the latter two immediately do a nm_device_master_add_slave() afterwards.
- priv->is_enslaved should be only set/cleared by
nm_device_slave_notify_*(). It can only be true, when
priv->master is set too.
Add assertions for that.
Diffstat (limited to 'data')
0 files changed, 0 insertions, 0 deletions