| commit | 3f8698d4d3f72252980575fb8d7b4cafeb5dd0a2 | |
| author | Kristen Carlson Accardi <kristen.c.accardi@intel.com> | |
| Wed, 23 May 2007 21:12:29 +0000 (23 14:12 -0700) | ||
| committer | Len Brown <len.brown@intel.com> | |
| Sat, 2 Jun 2007 04:37:54 +0000 (2 00:37 -0400) | ||
| tree | 5d7e3d7be6c4306026172a5cd7e7f8d82b828361 | treesnapshot (tar.gz zip) |
| parent | 1f9767df1346c9ce09d6e51b9f34b851e3d94fad | commitdiff |
ACPI: bay: send envp with uevent
Make the bay driver send env information on bay events.
Upon any bay event, we will send the string "BAY_EVENT=%d" along with the
KOBJ_CHANGE, and report the event number. What the event number means will
be platform specific. Event 3 is always an eject request, but an insert
may be either event 1, or it may be event 0. Event 1 may also be a
remove request. It would be best if you check the number of your event
with udevmonitor before writing any udev scripts for inserting and
removing drive bays.
Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Stephan Berberig <s.berberig@arcor.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
Make the bay driver send env information on bay events.
Upon any bay event, we will send the string "BAY_EVENT=%d" along with the
KOBJ_CHANGE, and report the event number. What the event number means will
be platform specific. Event 3 is always an eject request, but an insert
may be either event 1, or it may be event 0. Event 1 may also be a
remove request. It would be best if you check the number of your event
with udevmonitor before writing any udev scripts for inserting and
removing drive bays.
Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Stephan Berberig <s.berberig@arcor.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
| drivers/acpi/bay.c | diffblobblamehistory |