Commit 313e7b83 authored by Daniel Vetter's avatar Daniel Vetter
Browse files

drm-misc: Another check in the bugfix flow

Even in feature freeze it can happen that the broken patch is only in
drm-misc-next, and then applying to drm-misc-next-fixes will
rightfully stumble over dim's Fixes: validation since the sha1 wont be
an ancestor.

Fix that by adding another check.

v2: Less confusing wording (Marek)

Reviewed-by: Marek Vasut's avatarMarek Vasut <>
Cc: Marek Vasut <>
Signed-off-by: Daniel Vetter's avatarDaniel Vetter <>
parent 3b903110
Pipeline #595567 passed with stages
in 38 seconds
digraph {
next_0[shape=box, style=rounded, color=blue, label="drm-misc-next"];
next_1[shape=box, style=rounded, color=blue, label="drm-misc-next"];
next_2[shape=box, style=rounded, color=blue, label="drm-misc-next"];
fixes_0[shape=box, style=rounded, color=blue, label="drm-misc-fixes"];
next_fixes_0[shape=box, style=rounded, color=blue,
......@@ -10,6 +11,8 @@ digraph {
label="Is the bug in the current rc?"];
is_late[shape=diamond, color=red,
label="Is drm in feature freeze?\n(occurs after -rc6)"];
is_next[shape=diamond, color=red,
label="Is the bug both in drm-next\nand in drm-misc-next?"];
is_fix -> next_0[label="no"];
is_fix -> in_origin[label="yes"];
......@@ -18,5 +21,8 @@ digraph {
in_origin -> is_late[label="no"];
is_late -> next_1[label="no"]
is_late -> next_fixes_0[label="yes"]
is_late -> is_next[label="yes"]
is_next -> next_2[label="no"]
is_next -> next_fixes_0[label="yes"]
Supports Markdown
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