torvalds/linux

Choose this fork if your target is Apple Silicon hardware and you need the extra platform support. Choose upstream Linux if you want the broadest compatibility, fastest access to mainline fixes, and minimal downstream divergence.

Choose this fork if you want a performance-tuned, prepatched kernel and are willing to trade upstream freshness and supportability for those gains. Avoid it if you need maximum upstream compatibility, fastest security/fix intake, or a conservative production kernel.

Choose this fork if you need Arch Linux kernel packaging and maintenance workflows. Choose upstream directly if you want the newest kernel commits and do not need Arch-specific distro integration.

Prefer this fork if you need Linux kernel behavior as a library or test harness inside another system. Prefer upstream if you need a current, general-purpose kernel with the broadest hardware support and fastest security fix uptake.

Choose this fork only if Apple M1 support is the goal. It looks valuable as a specialized bring-up tree, but it is far too stale and divergent to use as a modern general-purpose Linux base.

Choose this fork only if your goal is PS4-specific Linux support. For anything else, upstream Linux is the better default because this branch is highly specialized, very stale, and far behind current kernel development.

Choose this fork only if you are maintaining legacy sunxi hardware and need its platform-specific fixes. If you want a current, broadly supported kernel, upstream Linux is the better base.

Choose this fork only if you need its Nintendo Switch Horizon OS compatibility work. For anything else, upstream Linux is the better default because this fork is highly specialized, very stale, and far behind mainline.

Choose this fork if you are targeting ODROID hardware and want vendor-added board support, overlays, and sensor enablement. Avoid it if you want a current Linux kernel base, broad upstream compatibility, or low-maintenance security tracking.