drm-misc

The DRM misc repository. Maintained by Maarten Lankhorst, Maxime Ripard, and Thomas Zimmermann, with a large pool of committers.

This repository consists mostly of the core drm code as well as DRM drivers that do not have a dedicated repository.

See the main DRM DRIVERS AND MISC GPU PATCHES MAINTAINERS entry, as well as all the other MAINTAINERS entries that reference the drm-misc repository, for current information on maintainers, mailing lists, bug reporting, etc.

Repository and Branches

https://gitlab.freedesktop.org/drm/misc/kernel

drm-misc-next

This is the main feature branch where most of the patches land. This branch is always open to “hide” the merge window from developers. To avoid upsetting linux-next and causing mayhem in the merge window, in general no pull requests are sent to upstream after rc6 of the current kernel release. Outside of that feature freeze period, pull requests are sent to upstream roughly every 1-2 weeks, to avoid too much coordination pains.

If you’re unsure, apply your patch here, it can always be cherry-picked to one of the -fixes branches later on. But in contrast to the drm-intel and drm-xe flow cherry-picking is not the default.

drm-misc-next-fixes

During the time between rc6 of kernel version X and rc1 of X+1, drm-misc-next will be targeting kernel version X+2 and drm-misc-fixes still targets kernel version X. This branch is for fixes to bugs introduced in the drm-misc-next pull request that was sent for X+1, which aren’t present in the drm-misc-fixes branch.

drm-misc-fixes

This is for bugfixes which target the current -rc cycle.

Merge Timeline

This chart describes the merge timelines for various branches in terms of one kernel release cycle. Worth noting is that we’re working on two or three kernel releases at the same time. Big features take a long time to hit a kernel release. There are no fast paths.