diff options
| author | Thomas Haller <thaller@redhat.com> | 2016-02-12 10:05:44 +0100 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2016-02-15 17:19:23 +0100 |
| commit | 149d49dbba226fcc98036a76dd1e61b97a0d6ed0 (patch) | |
| tree | 63520f372490707e5b16aff72d3d60d6955e0d18 /NetworkManager.pc.in | |
| parent | 55aa95909c09671c63a41b4f6a3a51ecc5c50d72 (diff) | |
| download | NetworkManager-lr/default-unmanaged-bgo746566.tar.gz | |
fixup! device: remove default-unmanaged and refactor unmanaged flagslr/default-unmanaged-bgo746566
https://bugzilla.gnome.org/show_bug.cgi?id=746566#c27
Also now in _set_state_full() the code allows re-entering the
UNAVAILABLE state for all cases, where previously it was just for
missing firmware. What is that necessary? The only reason it's
necessary for missing firmware is that devices are typically opened
during UNAVAILABLE and that's where the firmware error would happen
(ENOENT from IFF_UP), and to get that to happen again we need to redo
the IFF_UP when firmware directory changes. But why would we re-enter
UNAVAILABLE from normal cases?
Diffstat (limited to 'NetworkManager.pc.in')
0 files changed, 0 insertions, 0 deletions