Hi Jason,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next v5.13-rc5 next-20210608]
[cannot apply to drm-intel/for-linux-next drm/drm-next]
[If your patch is app
Hi Jason,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[also build test ERROR on drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next v5.13-rc5 next-20210608]
[cannot apply to drm-intel/for-linux-next drm/drm-next]
[If your patch is applied to
Hi Jason,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[also build test ERROR on drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next v5.13-rc5 next-20210608]
[cannot apply to drm-intel/for-linux-next drm/drm-next]
[If your patch is applied to
The current context uAPI allows for two methods of setting context
parameters: SET_CONTEXT_PARAM and CONTEXT_CREATE_EXT_SETPARAM. The
former is allowed to be called at any time while the later happens as
part of GEM_CONTEXT_CREATE. Currently, everything settable via one is
settable via the other.