drm-tip¶
The DRM subsystem configuration and integration repository.
Repository and Branches¶
https://gitlab.freedesktop.org/drm/tip
drm-tip¶
The drm-tip branch is the common DRM subsystem testing and integration tree (or “pile” to complete the reverse acronym). It’s a bit like linux-next for graphics. It gets automatically rebuilt and pushed every time one of the branches maintained using dim is updated.
It should be emphasized that no patch ever gets pushed to drm-tip directly, drm-tip is not upstream per se, and no pull requests are ever sent to or from drm-tip. It is, however, the merge result of a number of upstream branches like that. It is the combined bleeding edge of kernel graphics.
It is generally recommended to do graphics subsystem development on top of drm-tip.
drm-for-linux-next¶
The drm-for-linux-next branch is the unified branch for linux-next to pull,
replacing the per-repository for-linux-next* branches. It is rebuilt and
pushed together with drm-tip, and is simply the drm-tip merge result up to, but
excluding, the topic/* branches, i.e. everything that is headed upstream
soon, without the integration manifest commit.
Consequently the topic/* branches must be listed last in nightly.conf;
dim warns about any branch that is merged after a topic branch and thus
left out of drm-for-linux-next.
drm-rerere¶
The drm-rerere branch contains the nightly.conf configuration file that describes the repositories and branches managed by dim that get merged to drm-tip, the shared git rerere conflict resolutions for dim to generate drm-tip, as well as some kernel defconfig files for build testing.