dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: daniels@collabora.com, helen.fornazier@gmail.com,
	airlied@gmail.com, simona.vetter@ffwll.ch, robdclark@gmail.com,
	guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
	valentine.burley@collabora.com, lumag@kernel.org,
	quic_abhinavk@quicinc.com, mripard@kernel.org,
	maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
	linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] drm/ci: Add devicetree validation and KUnit tests
Date: Thu, 27 Mar 2025 21:31:09 +0530	[thread overview]
Message-ID: <20250327160117.945165-1-vignesh.raman@collabora.com> (raw)

Add jobs to validate devicetrees and run KUnit tests.

Pipeline link,
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1390797

Vignesh Raman (3):
  drm/ci: force use of BFD linker
  drm/ci: Add jobs to validate devicetrees
  drm/ci: Add jobs to run KUnit tests

 drivers/gpu/drm/ci/build.sh                | 14 ++------
 drivers/gpu/drm/ci/check-devicetrees.yml   | 38 ++++++++++++++++++++
 drivers/gpu/drm/ci/dt-binding-check.sh     | 18 ++++++++++
 drivers/gpu/drm/ci/dtbs-check.sh           | 41 ++++++++++++++++++++++
 drivers/gpu/drm/ci/gitlab-ci.yml           |  2 ++
 drivers/gpu/drm/ci/kunit.sh                | 34 ++++++++++++++++++
 drivers/gpu/drm/ci/kunit.yml               | 19 ++++++++++
 drivers/gpu/drm/ci/override-ld-with-bfd.sh | 16 +++++++++
 8 files changed, 170 insertions(+), 12 deletions(-)
 create mode 100644 drivers/gpu/drm/ci/check-devicetrees.yml
 create mode 100755 drivers/gpu/drm/ci/dt-binding-check.sh
 create mode 100755 drivers/gpu/drm/ci/dtbs-check.sh
 create mode 100755 drivers/gpu/drm/ci/kunit.sh
 create mode 100644 drivers/gpu/drm/ci/kunit.yml
 create mode 100755 drivers/gpu/drm/ci/override-ld-with-bfd.sh

-- 
2.47.2


             reply	other threads:[~2025-03-27 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 16:01 Vignesh Raman [this message]
2025-03-27 16:01 ` [PATCH v1 1/3] drm/ci: force use of BFD linker Vignesh Raman
2025-03-27 16:01 ` [PATCH v1 2/3] drm/ci: Add jobs to validate devicetrees Vignesh Raman
2025-03-30 17:06   ` Dmitry Baryshkov
2025-03-31  7:53     ` Maxime Ripard
2025-03-31  7:55       ` Dmitry Baryshkov
2025-04-01  2:15         ` Vignesh Raman
2025-04-01  1:56     ` Vignesh Raman
2025-04-01 15:14       ` Maxime Ripard
2025-03-27 16:01 ` [PATCH v1 3/3] drm/ci: Add jobs to run KUnit tests Vignesh Raman
2025-03-28 15:10   ` Maxime Ripard
2025-04-01  2:17     ` Vignesh Raman
2025-04-07 12:35       ` Maxime Ripard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250327160117.945165-1-vignesh.raman@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guilherme.gallo@collabora.com \
    --cc=helen.fornazier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sergi.blanch.torne@collabora.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=valentine.burley@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).