SmoothKernel builds from a pristine kernel.org tarball plus patch lanes committed to this repository. This keeps the kernel source reproducible from git history: there is no hidden local tree and no dependency on a downstream source checkout at build time.
Patches are applied in this exact order:
patches/cachyos-<kernel-version>/
patches/nobara-picks/
patches/post-nobara-<kernel-version>/
Within each directory, *.patch files are sorted by filename before being
applied. Prefix patches with 0001-, 0002-, and so on to make ordering
explicit.
The first lane contains the downstream scheduler/kernel base material for the specific kernel version. For the current line this is the BORE patch that applies cleanly to a pristine kernel.org tree.
Do not assume every patch from a downstream project applies to a pristine kernel.org tarball. Some downstream patchsets are authored against their own already-modified tree. If a patch depends on hidden source deltas, either rebase it explicitly or do not carry it.
This lane contains narrow Nobara cherry-picks that are useful across Smooth* flavors, currently HID/controller improvements. These patches are deliberately not a full Nobara patch import.
Good candidates:
- Driver-level hardware enablement.
- Patches that have no runtime cost unless matching hardware is present.
- Patches that apply cleanly after the base lane.
Bad candidates:
- Fedora packaging changes.
- Build-system assumptions tied to Nobara's SRPM pipeline.
- Broad desktop policy changes that do not help headless flavors.
The CachyOS base lane is cut against an early point release of a kernel line and
is not necessarily refreshed as that line advances. The 7.1 lane was
authored against 7.1-rc1 (BORE 6.6.3, committed 2026-05-04) and had not been
touched by the time 7.1.8 shipped three months later; upstream BORE itself
only published a 7.1-rc1 patch. The result is that a lane which is nominally
"for 7.1" can fail against a current 7.1.x.
Expect this on every major bump. Budget for a rebase rather than assuming the
lane is ready, and check both CachyOS and
firelzrd/bore-scheduler for a
newer revision before hand-rebasing. If you do rebase, record it in the lane
README with the failing hunk, what upstream changed underneath it, and the
condition for dropping the local delta — see patches/cachyos-7.1.8/README.md
for the worked example.
Fuzz is the early warning. A hunk that applies "with fuzz N" is telling you upstream is drifting under the patch; record it, and rebase rather than accept once the fuzz reaches code (as opposed to documentation) hunks.
This lane is for local carry patches and rebased follow-ons that must apply after the secondary lane. It should stay small. A growing final lane is a signal that we are maintaining too much kernel code ourselves.
Kernel lanes are not the only patch stack. recipes/build-zfs.sh applies
patches/$ZFS_PATCHSET/*.patch to the extracted OpenZFS release tarball before
autogen.sh, using the same conventions: ordered numeric prefixes, vendored in
git, README with source, reason and removal condition.
This lane exists because OpenZFS' META carries a Linux-Maximum cap that
configure enforces as a hard error, and that cap routinely lags the kernels we
ship. Keep the lane as small as the kernel lanes — a growing ZFS lane means we
are maintaining a fork of a storage layer, which is a much worse place to be
than maintaining kernel deltas.
ZFS_PATCHSET is optional. The current OpenZFS 2.4.4 release supports Linux
7.2 upstream, so the 7.2.10 examples leave it empty and retain zfs-2.4.3 only
as an archived lane for older builds. Leave it unset when the OpenZFS release needs no
patches, which is the state we want to return to.
Every patch directory should include a README that records:
- Kernel version or version range.
- Patch source and upstream reference.
- Why the patch is carried.
- Any local rebase notes.
- Removal condition.
For small single-purpose lanes, the README can be short. For local carry patches, include enough context that a maintainer can decide whether to drop or rebase the patch during the next kernel bump.
- Choose the correct lane.
- Name the file with an ordered numeric prefix.
- Keep the patch in
git format-patchstyle when possible. - Add or update the lane README.
- Run
make kernel-config-update-allif the patch adds or removes Kconfig symbols. - Run
make kernel DEB_ARCH=<arch>for each affected architecture. - Install on the relevant hardware path before promotion.
If a patch is hardware-specific, document the hardware tested. If no hardware is available, document that explicitly and do not treat the patch as fully validated.
For a point release:
- Create the new versioned lane directories.
- Rebase or replace the base lane for the new kernel.
- Re-test
nobara-picks; keep the lane unversioned only while the patches continue to apply cleanly across current supported versions. - Rebase local carry patches into the new
post-nobara-<version>/lane. - Run
make kernel-config-update-all. - Review the config diff.
- Run kernel and ZFS builds for each supported architecture.
The full bump process is in bumping-kernel.md.
Before merging a patch-stack change:
- Does every patch apply to a pristine kernel.org tree after earlier lanes?
- Is the patch source documented?
- Is the reason documented in user/workload terms?
- Is the removal condition known?
- Does the patch affect config symbols, ABI, module names, or userspace APIs?
- Did the maintainer run the affected
make kernel DEB_ARCH=<arch>builds? - Did the maintainer run the relevant hardware or flavor smoke test?
Avoid carrying patches that:
- Only improve synthetic benchmarks without a Smooth* workload reason.
- Require a large downstream source base not present in this repo.
- Are security-sensitive and better handled by upstream stable.
- Create per-flavor behavior in the shared kernel.
- Replace a runtime userspace tuning knob with a compile-time fork.
The one-kernel model depends on keeping the patch stack understandable. If a patch cannot be explained briefly and tested concretely, it probably does not belong here.