kobject/hotplug split
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | kobject/hotplug split - kobject add/removelib/ | +3 | 0 replies | |
| 2/6 | kobject/hotplug split - class coredrivers/ | +2 | 0 replies | |
| 3/6 | kobject/hotplug split - block corefs/ | +2 | 0 replies | |
| 4/6 | kobject/hotplug split - devices coredrivers/ | +3 | 0 replies | |
| 5/6 | kobject/hotplug split - usb crisdrivers/ | +1 | 0 replies | |
| 6/6 | kobject/hotplug split - net bridgenet/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] kobject/hotplug split
This splits the implicit generation of hotplug events from kobject_add() and kobject_del(), to give the driver core control over the time the event is created.
The kobject_register() and unregister functions still have the same behavior and emit the events by themselves.
The class, block and device core is changed now to emit the hotplug event _after_ the "dev" file, the "device" symlink and the default attributes are created. This will save udev from spinning in a stat() loop to wait for the files to appear, which is expensive if we have a lot of concurrent events.