diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-07-20 09:17:33 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-07-20 09:17:33 +0200 |
commit | 891a15cab2d9df187bb55903223bc2a569cf9f5d (patch) | |
tree | e6e492bc79d2eea05f41e6639c0d8497cd529b45 | |
parent | 13317a22e5cf8f7c458616a971e60e84255bc364 (diff) |
man: document a tiny bit better what udev_device_get_is_initialized() actually returns
-rw-r--r-- | man/udev_device_get_syspath.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man/udev_device_get_syspath.xml b/man/udev_device_get_syspath.xml index b54749ed56..014f43b21c 100644 --- a/man/udev_device_get_syspath.xml +++ b/man/udev_device_get_syspath.xml @@ -184,10 +184,10 @@ to such a parent device. On failure, <constant>NULL</constant> is returned.</para> - <para>On success, <function>udev_device_get_is_initialized()</function> - returns either <constant>1</constant> or <constant>0</constant>, - depending on whether the passed device is initialized or not. On - failure, a negative error code is returned.</para> + <para>On success, <function>udev_device_get_is_initialized()</function> returns either <constant>1</constant> or + <constant>0</constant>, depending on whether the passed device has already been initialized by udev or not. On + failure, a negative error code is returned. Note that devices for which no udev rules are defined are never + reported initialized.</para> </refsect1> <refsect1> |