[systemd-devel] udev_device_get_driver implementation

Sayeed hyder csayeedh at gmail.com
Wed Apr 24 15:38:02 UTC 2019


I was looking at the udev_device_get_driver implementation. It first gets
the sys path and then appends "driver", and calls readlink to get the
driver information. Does it work for all cases? While working on a project,
I found that following the sys path, there is no "driver", but it should be
"device/driver" i.e. if I append "device/driver" instead of "driver" only,
I can use readlink to get the driver information.

Can anybody explain whether this was missing in the implementation or am I
missing something?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20190424/11deee0d/attachment.html>

More information about the systemd-devel mailing list