161bc525bb
RUN seems to be used primarily for historical reasons over the more immediate IMPORT command. As a side-effect, RUN also runs *after* all the rules have been processed which is not really what we want here - we expect the device to be updated immediately. Other rules that rely on accurate evdev axes should be able to assume the axes are already present. So let's use IMPORT here. For consistency, the second two rules are split across multiple lines as well. |
||
|---|---|---|
| .. | ||
| 50-udev-default.rules.in | ||
| 60-block.rules | ||
| 60-cdrom_id.rules | ||
| 60-drm.rules | ||
| 60-evdev.rules | ||
| 60-fido-id.rules | ||
| 60-input-id.rules | ||
| 60-persistent-alsa.rules | ||
| 60-persistent-input.rules | ||
| 60-persistent-storage-tape.rules | ||
| 60-persistent-storage.rules | ||
| 60-persistent-v4l.rules | ||
| 60-sensor.rules | ||
| 60-serial.rules | ||
| 61-autosuspend-manual.rules | ||
| 64-btrfs.rules.in | ||
| 70-joystick.rules | ||
| 70-mouse.rules | ||
| 70-touchpad.rules | ||
| 75-net-description.rules | ||
| 75-probe_mtd.rules | ||
| 78-sound-card.rules | ||
| 80-drivers.rules | ||
| 80-net-setup-link.rules | ||
| 99-systemd.rules.in | ||
| meson.build | ||