Speaker
Description
Kernel Maintainers are supposed to send pull requests with code adhering to some standards, which are not always well documented and might be difficult to figure out for new Kernel Maintainers. The talk will present current best-practices for handling the code and sending it further to the upstream Maintainer:
1. Improvements to email workflow: b4, useful simple hooks for verifying commits (because checkpatch is not enough).
2. Get yourself in linux-next and get tested by community Continuous Integration/Testing.
3. Add yourself to kernel.org keyring, sign your tags and pushes (for transparency log).
4. Dump the mailing lists: use lei and lore.
The talk is directed towards fresh Kernel Maintainers and to all who want to improve their workflow.
