driver core: export MAJOR/MINOR to the hotplug env
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest7 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | class core: export MAJOR/MINOR to the hotplug envdrivers/ include/ | +30 | 0 replies | |
| 2/7 | block core: export MAJOR/MINOR to the hotplug envdrivers/ | +34 | 0 replies | |
| 3/7 | class_simple: pass dev_t to the class coredrivers/ | +2 | 0 replies | |
| 4/7 | usb: class driver pass dev_t to the class coredrivers/ | +1 | 0 replies | |
| 5/7 | i2c: class driver pass dev_t to the class coredrivers/ | +1 | 0 replies | |
| 6/7 | videodev: pass dev_t to the class coredrivers/ | +1 | 0 replies | |
| 7/7 | inifiniband: pass dev_t to class coredrivers/ | +1 | 1 reply |
Reviews trailers per patch
1 of 7 patches has a Reviewed-by or Acked-by.
| Patch | Roland Dreier |
|---|---|
| 1/7 | |
| 2/7 | |
| 3/7 | |
| 4/7 | |
| 5/7 | |
| 6/7 | |
| 7/7 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/7] driver core: export MAJOR/MINOR to the hotplug env
This patch sequence moves the creation of the sysfs "dev" file of the class devices into the driver core. The struct class_device contains a dev_t value now. If set, the driver core will create the "dev" file containing the major/minor numbers automatically.
The MAJOR/MINOR values are also exported to the hotplug environment. This makes it easy for userspace, especially udev to know if it should wait for a "dev" file to create a device node or if it can just ignore the event. We currently carry a compiled in blacklist around for that reason.
It would also be possible to run some "tiny udev" while sysfs is not available - just by reading the hotplug call or the netlink-uevent.
Thanks,
Kay