linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maxime Ripard" <mripard@kernel.org>
To: "Vignesh Raman" <vignesh.raman@collabora.com>
Cc: airlied@gmail.com, daniel@fooishbar.org, daniels@collabora.com,
	dri-devel@lists.freedesktop.org, guilherme.gallo@collabora.com,
	helen.fornazier@gmail.com, linux-kernel@vger.kernel.org,
	lumag@kernel.org, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, quic_abhinavk@quicinc.com,
	robdclark@gmail.com, sergi.blanch.torne@collabora.com,
	simona.vetter@ffwll.ch, tzimmermann@suse.de,
	valentine.burley@collabora.com,
	"Maxime Ripard" <mripard@kernel.org>
Subject: Re: [PATCH v2 2/2] drm/ci: Add jobs to run KUnit tests
Date: Wed, 09 Apr 2025 09:53:24 +0000	[thread overview]
Message-ID: <7718bcfa86013d711e209f65ee398c3d@kernel.org> (raw)
In-Reply-To: <20250409061543.311184-3-vignesh.raman@collabora.com>

On Wed, 9 Apr 2025 11:45:39 +0530, Vignesh Raman wrote:
> Add jobs to run KUnit tests using tools/testing/kunit/kunit.py tool.
> 
> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>

Reviewed-by: Maxime Ripard <mripard@kernel.org>

Thanks!
Maxime

  reply	other threads:[~2025-04-09  9:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  6:15 [PATCH v2 0/2] drm/ci: Add devicetree validation and KUnit tests Vignesh Raman
2025-04-09  6:15 ` [PATCH v2 1/2] drm/ci: Add jobs to validate devicetrees Vignesh Raman
2025-04-09  9:53   ` Maxime Ripard
2025-04-10 19:32   ` Dmitry Baryshkov
2025-04-11  8:32     ` Vignesh Raman
2025-04-11  9:58       ` Dmitry Baryshkov
2025-04-09  6:15 ` [PATCH v2 2/2] drm/ci: Add jobs to run KUnit tests Vignesh Raman
2025-04-09  9:53   ` Maxime Ripard [this message]
2025-04-09 18:23 ` [PATCH v2 0/2] drm/ci: Add devicetree validation and " Helen Koike
2025-04-10  8:07   ` Vignesh Raman
2025-04-10 14:40     ` Helen Koike
2025-04-11  8:35       ` Vignesh Raman

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=7718bcfa86013d711e209f65ee398c3d@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=daniel@fooishbar.org \
    --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=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 \
    --cc=vignesh.raman@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).