Driver core: Fix device_move() vs. dpm list ordering, v2
dpm_list currently relies on the fact that child devices will be registered after their parents to get a correct suspend order. Using device_move() however destroys this assumption, as an already registered device may be moved under a newly registered one. This patch adds a new argument to device_move(), allowing callers to specify how dpm_list should be adapted. Signed-off-by:Cornelia Huck <cornelia.huck@de.ibm.com> Acked-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
Showing
- drivers/base/core.c 18 additions, 1 deletiondrivers/base/core.c
- drivers/base/power/main.c 44 additions, 0 deletionsdrivers/base/power/main.c
- drivers/base/power/power.h 8 additions, 0 deletionsdrivers/base/power/power.h
- drivers/s390/cio/device.c 5 additions, 4 deletionsdrivers/s390/cio/device.c
- include/linux/device.h 2 additions, 1 deletioninclude/linux/device.h
- include/linux/pm.h 11 additions, 0 deletionsinclude/linux/pm.h
- net/bluetooth/hci_sysfs.c 1 addition, 1 deletionnet/bluetooth/hci_sysfs.c
- net/bluetooth/rfcomm/tty.c 3 additions, 2 deletionsnet/bluetooth/rfcomm/tty.c
Loading
Please register or sign in to comment