udev-rules: Add rule for haptics on google-sargo
Not sure if this would be the right spot (as suggested in https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/3 )
Merge request reports
Activity
Thanks a lot for caring about this working out of the box. Could you use the same pattern as in !140 (merged) please:
- mention if the driver is mainline or not in the commit message
- add a comment about the device type in the udev rule
- Sort in the udev rule alphabetically by device vendor
(these rules didn't exist when you opened the MR, just want to make sure things don't spin out of control when we add more devices)
added 3 commits
-
43c469e7...fc7ec6e8 - 2 commits from branch
Librem5:main
- e2c5bce8 - udev-rules: Add rule for haptics on google-sargo
-
43c469e7...fc7ec6e8 - 2 commits from branch
To be honest I'm unsure if this driver is in mainline yet (and fetching the linux sources does not work particularly well during my travels with DB).
However, a naive grep for
drv.*2624
on codesearch did not yield results.Edit: The commit message has not been updated yet, but will do so once I've confirmed whether the driver is in mainline or not
Edited by Evangelos Ribeiro Tzarasadded 1 commit
- de4fbf63 - udev-rules: Add support for haptics on Google Sargo
Sorry for the delay.
v2: Adhere to style from !140 (merged) (including commit message)
added 1 commit
- 3d480aab - udev-rules: Add support for haptics on Google Sargo
added 3 commits
-
3d480aab...0646a930 - 2 commits from branch
Librem5:main
- 30bafbfe - udev-rules: Add support for haptics on Google Sargo
-
3d480aab...0646a930 - 2 commits from branch
enabled an automatic merge when the pipeline for 30bafbfe succeeds
mentioned in commit fe6e0a85