rules: avoid 'device/' accesses

We should never access parents, as the sysfs hierarchy is in no way
stable. Use KERNELS== etc. to match on a parent, then access it via
$attr{} (which accesses the matching device, not the current device).

diff --git a/rules/60-keyboard.rules b/rules/60-keyboard.rules
index af3edb5f58fa9708ceed28128da4765156a45aca..fe616917da8569baad1412cc70e9d4f7ec1d6750 100644 (file)
--- a/rules/60-keyboard.rules
+++ b/rules/60-keyboard.rules
@@ -13,7 +13,7 @@ DRIVERS=="atkbd", IMPORT{builtin}="hwdb 'keyboard:atkbd:$attr{[dmi/id]modalias}'
   RUN{builtin}+="keyboard", GOTO="keyboard_end"
 
 # device matching the input device name and the machine's DMI data
   RUN{builtin}+="keyboard", GOTO="keyboard_end"
 
 # device matching the input device name and the machine's DMI data

-IMPORT{builtin}="hwdb 'keyboard:name:$attr{device/name}:$attr{[dmi/id]modalias}'", \
+KERNELS=="input*", IMPORT{builtin}="hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}'", \

   RUN{builtin}+="keyboard", GOTO="keyboard_end"
 
 LABEL="keyboard_end"
   RUN{builtin}+="keyboard", GOTO="keyboard_end"
 
 LABEL="keyboard_end"