diff options
author | Thomas Haller <thaller@redhat.com> | 2021-02-03 14:48:01 +0100 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2021-02-03 14:58:00 +0100 |
commit | 97ed143e04e74323a59a0f24a965d36341233670 (patch) | |
tree | 268dc65fb04dc8448515119fb7398e3b5ca3ed9c /src/core/supplicant/nm-supplicant-config.c | |
parent | 41a28ca9c3bc58ff49b7a1cd7634c1da29df9db9 (diff) | |
download | NetworkManager-97ed143e04e74323a59a0f24a965d36341233670.tar.gz |
udev/trivial: rename nm_udev_client_unref() to nm_udev_client_destory()
NMUdevClient does not actually implement ref-counting, because it's not
used. Still, the destroy function was named nm_udev_client_unref(),
because theoretically then we could later, as the need arises, make
the type ref-counted. Then unref function already had the right name.
However, NMUdevClient also has a callback function that emits monitor
events. Again for simplicity, this callback function cannot be reset, it
can only be set once (in the constructor) and can also not be unset nor
disabled.
When the user of NMUdevClient is done with the instance and calls
"unref", then it must be sure that the callback is no longer invoked
afterwards. In practice that is already the case, but "unref" makes it
sound as if somebody else could also still hold a reference -- in which
case the user would have to first unset/disable the callback.
Rename the function to "destroy()", so that it's clear that the instance
is gone afterwards and that the callback will not be invoked anymore.
Diffstat (limited to 'src/core/supplicant/nm-supplicant-config.c')
0 files changed, 0 insertions, 0 deletions