Re: [PATCH v2] drm/ci: Add CI pipeline for drm-misc branches

[Vignesh Raman <vignesh.raman@collabora.com>]

Hi Maxime,

On 19/10/26 19:56, Maxime Ripard wrote:
> Hi Vignesh,
> 
> On Mon, Oct 19, 2026 at 03:30:54PM +0530, Vignesh Raman wrote:
>> Hi,
>>
>> On 11/09/26 17:48, Maxime Ripard wrote:
>>> The DRM CI infrastructure builds upon Mesa's CI to run IGT tests on
>>> hardware. Its focus is on functional testing on a selected number of
>>> targets.
>>>
>>> The concern for drm-misc is different: it merges a large number of
>>> patches across many platforms, and build or unit test breakages happen
>>> on a regular basis. Adding build and unit testing for drm-misc has been
>>> on the back of our minds, and a first attempt was made last year. The
>>> feedback was to rely more on the existing infrastructure.
>>>
>>> Introduce a CI entry point that runs on pushes to drm-misc-next,
>>> drm-misc-fixes, and drm-misc-next-fixes. It reuses kunit.yml,
>>> check-devicetrees.yml, and the freedesktop ci-templates, while defining
>>> build templates inline to avoid pulling in the Mesa pipeline.
>>>
>>> A single Debian container with LLVM handles cross-compilation to all
>>> three architectures. The pipeline compiles the kernel using defconfigs
>>> from the drm/tip rerere-cache branch, runs the DRM KUnit tests, and
>>> checks device tree bindings.
>>>
>>> Link: https://lore.kernel.org/all/20250319-greedy-sturgeon-from-avalon-ac758f@houat/
>>> Acked-by: Vignesh Raman <vignesh.raman@collabora.com>
>>> Signed-off-by: Maxime Ripard <mripard@kernel.org>
>>> ---
>>> Changes in v2:
>>> - Run dt_bindings_check
>>> - Run on push instead of MR after some discussions with Dave and Sima
>>> - Test run here: https://gitlab.freedesktop.org/mripard/kernel/-/pipelines/1744733
>>> - Link to v1: https://lore.kernel.org/r/20260902-drm-drm-misc-ci-v1-1-49d05e228eab@kernel.org
>>
>> Acked-by: Vignesh Raman <vignesh.raman@collabora.com>
> 
> Thanks for the review, see below
> 
>>> ---
>>>    drivers/gpu/drm/ci/drm-misc-ci.yml | 147 +++++++++++++++++++++++++++++++++++++
>>>    1 file changed, 147 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/ci/drm-misc-ci.yml b/drivers/gpu/drm/ci/drm-misc-ci.yml
>>> new file mode 100644
>>> index 000000000000..4ab87547794e
>>> --- /dev/null
>>> +++ b/drivers/gpu/drm/ci/drm-misc-ci.yml
>>> @@ -0,0 +1,147 @@
>>> +# CI pipeline for drm-misc-next, drm-misc-fixes, and drm-misc-next-fixes.
>>> +#
>>> +# Runs on pushes to drm-misc-next, drm-misc-fixes, and
>>> +# drm-misc-next-fixes. Compiles the kernel for arm, arm64, and
>>> +# x86_64, runs the DRM KUnit tests, and checks device tree bindings.
>>> +#
>>> +# A single container image is built using freedesktop ci-templates with
>>> +# the packages needed for kernel compilation and LLVM for
>>> +# cross-compilation. QEMU is installed at runtime by the KUnit jobs.
>>> +#
>>> +# check-devicetrees.yml and kunit.yml are included directly. build.yml
>>> +# and the Mesa container/build pipelines are not:
>>> +# they pull in hundreds of Mesa-specific jobs and templates that would
>>> +# each need to be individually stubbed or disabled. The build templates
>>> +# (.build:arm32, .build:arm64, .build:x86_64) are defined inline.
>>> +
>>> +variables:
>>> +  CI_TEMPLATES_COMMIT: &ci-templates-commit aec7a6ce7bb38902c70641526f6611e27141784a
>>> +  # Project whose container registry stores the built images
>>> +  FDO_UPSTREAM_REPO: mripard/kernel
>>> +  KERNEL_BUILD_CONTAINER_TAG: "2026-09-11-01"
>>> +  LLVM_VERSION: "19"
> 
> I just realised there's still my personal repo being used as the
> container registry. Are you ok if I change it to drm/misc/kernel when
> applying?


Yes, please change it when applying. Thanks.

Regards,
Vignesh

> 
> Thanks again,
> Maxime