summaryrefslogtreecommitdiffstats
path: root/sound/oss/dmasound
diff options
context:
space:
mode:
authorLee, Chun-Yi <joeyli.kernel@gmail.com>2018-03-20 13:51:26 +0800
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-03-20 10:33:51 +0100
commit27664c581866c950f31ac007ea2c63fc6e2b29d5 (patch)
treeb77099b760f5eac0df4b821cea45ba136f729a06 /sound/oss/dmasound
parentc698ca5278934c0ae32297a8725ced2e27585d7f (diff)
downloadlinux-stable-27664c581866c950f31ac007ea2c63fc6e2b29d5.tar.gz
linux-stable-27664c581866c950f31ac007ea2c63fc6e2b29d5.tar.bz2
linux-stable-27664c581866c950f31ac007ea2c63fc6e2b29d5.zip
ACPI / scan: Send change uevent with offine environmental data
In current design of ACPI container offline, Kernel emits KOBJ_CHANGE uevent to user space to indidate that the ejection of the container was triggered by platform. (caa73ea15 patch) A pure KOBJ_CHANGE uevent is not enough for user space to identify the purpose. For example, a "udevadm trigger" command can also be used to emit change event to all udev rules. A udev rule can not identify that the event is from kernel for offline or from udevadm for other purpose. Then the offline action in udev rule may also be triggered by udevadm tool. So, similar to the change uevent of dock, kernel sends the KOBJ_CHANGE uevent with a offline environmental data to indicate purpose. It's useful by udev rule for using ENV{EVENT} filter. Acked-by: Michal Hocko <mhocko@suse.com> Tested-by: Michal Hocko <mhocko@suse.com> Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'sound/oss/dmasound')
0 files changed, 0 insertions, 0 deletions