Commit 3d42fca0 authored by Eric Anholt's avatar Eric Anholt

drm/doc: Allow new UAPI to be used once it's in drm-next/drm-misc-next.

I was trying to figure out if it was permissible to merge the Mesa
side of V3D's CSD support yet while it's in drm-misc-next but not
drm-next, and developers on #dri-devel IRC had differing opinions of
what the requirement was.

v2: Restrict to just drm-next or drm-misc-next on airlied's request.
Signed-off-by: default avatarEric Anholt <eric@anholt.net>
Link: https://patchwork.freedesktop.org/patch/msgid/20190424220638.16222-1-eric@anholt.netReviewed-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
parent 05865769
...@@ -92,9 +92,9 @@ leads to a few additional requirements: ...@@ -92,9 +92,9 @@ leads to a few additional requirements:
requirements by doing a quick fork. requirements by doing a quick fork.
- The kernel patch can only be merged after all the above requirements are met, - The kernel patch can only be merged after all the above requirements are met,
but it **must** be merged **before** the userspace patches land. uAPI always flows but it **must** be merged to either drm-next or drm-misc-next **before** the
from the kernel, doing things the other way round risks divergence of the uAPI userspace patches land. uAPI always flows from the kernel, doing things the
definitions and header files. other way round risks divergence of the uAPI definitions and header files.
These are fairly steep requirements, but have grown out from years of shared These are fairly steep requirements, but have grown out from years of shared
pain and experience with uAPI added hastily, and almost always regretted about pain and experience with uAPI added hastily, and almost always regretted about
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment