48feb3c419508487becfb9ea3afcc54c3eac6d80 appears to flag a device as detached if an acpi eject request is received. In 2.6.24 and earlier, an eject request merely sent an event to userland which could then cleanly unmount the device and let the user know when it was safe to remove the drive. Removing the device would then send another acpi request that triggered the actual hotplug and bus rescan. This seems like a regression - it's no longer possible to ensure that a bay device is cleanly unmounted. Was this really the desired behaviour? It should be noted that not all hardware sends the eject request at all (Thinkpads do, but Dell and HP laptops don't), so we can't depend on receiving this when dealing with a bay event. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
