Contributing to Zephyr vs (Linux and U-boot)
summary
Compares contribution workflows and shows a live PR fix: Zephyr uses GitHub PR workflow with CI checks (checkpatch, format, sign-offs) instead of Linux’s email patch series, requires linear rebased commits that each compile, and assigns maintainers automatically. Uses West tool for repo/module management and CMake/Kconfig/device tree layouts; bootloader support via MCUboot modules. Demonstrates fixing a sensor driver indentation, pushing a branch, opening a PR and getting automated checks; backports land from main into LTS (2.7) via cherry-picks.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:43Prerequisites
- 3:56Directory Structure
- 18:16Forking Your Repository
- 27:02Good Commit and Bad Commit Message
related talks
36mHow to Get Your Zephyr Patches Merged
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
40mBoF: Zephyr: Meet the Maintainers
40m9 Years in the Making, the Story of Zephyr, Starting with Commit Nr. 1
27mZephyr Porting Efforts in High Performance SoCs
56mMeet the Maintainers BoF
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
48mGraphing Zephyr Development and Project Health and How Visualizing Data Help with Gr...