Author(s):	Benjamin Tissoires
Location	Room 8
Date	jan Fri 17	Days Raw Files
Start	14:25	First Raw Start	error-in-template
Duration	0:45:0	Offset	None
End	15:10	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/78/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf How_to_make_kernel_and_user_space_CI_for_input_devices.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Making sure that a commit in the kernel doesn't break a mouse, a touchpad or a space bar is hard. Ideally, we need to run this commit, and all versions of it against every possible device. Rinse wash repeat for the user-space commits, because there is this one guy that uses the CPU overheating when long pressing the space bar as an indication to emacs to send a control key event (xkcd 1172). But the universe hasn't provided us an army of people to test the devices, an infinite amount of resources and a lot of time to spare. So making true CI on actual physical devices is hard. That's a pity, really. Luckily, we have computers, and that's a start. In this talk we will show how we moved from basically no regression tests 10 years ago to a state where now every commit gets tested against a good amount of various devices. We will show how we can do CI on the kernel side, and how we can do CI on the user space side. markdown
Comment:	production notes