Re: [systemd-devel] udev_device_get_driver implementation

2019-04-24 Thread Greg KH
A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I inclu

Re: [systemd-devel] udev_device_get_driver implementation

2019-04-24 Thread Sayeed hyder
ll /sys/devices/LNXSYSTM:00/device:00/ACPI0012:00/ndbus0/region1/pfn1.1/block/pmem1/ total 0 -r--r--r-- 1 root root 4096 Apr 19 09:38 alignment_offset -rw-r--r-- 1 root root 4096 Apr 19 09:38 badblocks lrwxrwxrwx 1 root root0 Apr 19 09:38 bdi -> ../../../../../../../../virtual/bdi/259:3 -r--r-

Re: [systemd-devel] udev_device_get_driver implementation

2019-04-24 Thread Greg KH
On Wed, Apr 24, 2019 at 10:10:08AM -0700, Sayeed hyder wrote: > Forgot to hit "reply all" > > On Wed, Apr 24, 2019 at 9:52 AM Sayeed hyder wrote: > > > Hi Greg, > > > > Sure, this is what I get if I use the syspath from > > udev_device_get_syspath. As you can see, it is showing a symlink to a >

Re: [systemd-devel] udev_device_get_driver implementation

2019-04-24 Thread Sayeed hyder
Forgot to hit "reply all" On Wed, Apr 24, 2019 at 9:52 AM Sayeed hyder wrote: > Hi Greg, > > Sure, this is what I get if I use the syspath from > udev_device_get_syspath. As you can see, it is showing a symlink to a > device, and there is no driver. If it helps, it is a DAX mounted persistent >

Re: [systemd-devel] udev_device_get_driver implementation

2019-04-24 Thread Greg KH
On Wed, Apr 24, 2019 at 08:38:02AM -0700, Sayeed hyder wrote: > Hi, > > 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, >

[systemd-devel] udev_device_get_driver implementation

2019-04-24 Thread Sayeed hyder
Hi, 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 b