-
Jani Nikula authored
Switching from using drm-intel-next-queued to drm-intel-next requires a flag-day change. This is the dim change to switch to drm-intel-next. For now, keep the sub-command names such as "conq" and "push-queued", and change everything under the hood. Prevent pushes to drm-intel-next-queued. The flag-day change should be rolled with: 1) Bump minimum dim version with DIM_MIN_VERSION=1 in nightly.conf 2) Sync drm-intel-next-queued to drm-intel-next 3) Push this change to maintainer-tools Cc: Daniel Vetter <daniel@ffwll.ch> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by:
Rodrigo Vivi <rodrigo.vivi@intel.com> Acked-by:
Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
Jani Nikula authoredSwitching from using drm-intel-next-queued to drm-intel-next requires a flag-day change. This is the dim change to switch to drm-intel-next. For now, keep the sub-command names such as "conq" and "push-queued", and change everything under the hood. Prevent pushes to drm-intel-next-queued. The flag-day change should be rolled with: 1) Bump minimum dim version with DIM_MIN_VERSION=1 in nightly.conf 2) Sync drm-intel-next-queued to drm-intel-next 3) Push this change to maintainer-tools Cc: Daniel Vetter <daniel@ffwll.ch> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by:
