From: Karthik B S <karthik.b.s@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v3 5/5] tests/prime_udl: Move into intel/ and add documentation
Date: Thu, 11 Jun 2026 07:44:45 +0530 [thread overview]
Message-ID: <c88bae25-6b0e-48d6-ad3f-00a7a8ae1032@intel.com> (raw)
In-Reply-To: <20260521174820.167237-6-kamil.konieczny@linux.intel.com>
On 5/21/2026 11:18 PM, Kamil Konieczny wrote:
> This is an i915 test so move it to tests/intel/ folder.
> Add also documentation so build will not become broken.
>
> v3: keep old name, add documentation in subject (Kamil)
>
> Cc: Karthik B S <karthik.b.s@intel.com>
> Suggested-by: Karthik B S <karthik.b.s@intel.com>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
> ---
> tests/{ => intel}/prime_udl.c | 17 +++++++++++++++++
> tests/meson.build | 2 +-
> 2 files changed, 18 insertions(+), 1 deletion(-)
> rename tests/{ => intel}/prime_udl.c (88%)
>
> diff --git a/tests/prime_udl.c b/tests/intel/prime_udl.c
> similarity index 88%
> rename from tests/prime_udl.c
> rename to tests/intel/prime_udl.c
> index db83152fc..c6ef4a750 100644
> --- a/tests/prime_udl.c
> +++ b/tests/intel/prime_udl.c
> @@ -13,6 +13,23 @@
>
> #include "i915/gem_create.h"
>
> +/**
> + * TEST: prime udl
> + * Category: Display
> + * Description: Basic set of prime tests between Intel and DisplayLink.
> + * Driver requirement: i915
> + * Mega feature: General Display Features
> + * Sub-category: Memory management tests
> + * Functionality: prime import/export
> + * Test category: GEM_Legacy
> + * Feature: prime
> + *
> + * SUBTEST: share-import
> + *
> + * SUBTEST: share-import-addfb
> + *
> + */
> +
> IGT_TEST_DESCRIPTION("Basic set of prime tests between Intel and DisplayLink");
>
> int intel_fd = -1, udl_fd = -1;
> diff --git a/tests/meson.build b/tests/meson.build
> index fe0818118..0207b7da8 100644
> --- a/tests/meson.build
> +++ b/tests/meson.build
> @@ -72,7 +72,6 @@ test_progs = [
> 'kms_vrr',
> 'kms_writeback',
> 'meta_test',
> - 'prime_udl',
> 'prime_vgem',
> 'sriov_basic',
> 'syncobj_basic',
> @@ -239,6 +238,7 @@ intel_i915_progs = [
> 'prime_mmap_coherency',
> 'prime_mmap_kms',
> 'prime_self_import',
> + 'prime_udl',
> 'sysfs_defaults',
> 'sysfs_heartbeat_interval',
> 'sysfs_preempt_timeout',
next prev parent reply other threads:[~2026-06-11 2:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 17:48 [PATCH i-g-t v3 0/5] Various fixes for prime_udl test Kamil Konieczny
2026-05-21 17:48 ` [PATCH i-g-t v3 1/5] tests/prime_udl: Fix opening Kamil Konieczny
2026-05-21 17:48 ` [PATCH i-g-t v3 2/5] tests/prime_udl: Create subtests Kamil Konieczny
2026-05-21 17:48 ` [PATCH i-g-t v3 3/5] tests/prime_udl: Fix error handling Kamil Konieczny
2026-05-21 17:48 ` [PATCH i-g-t v3 4/5] tests/prime_udl: Fix i915 device opening Kamil Konieczny
2026-05-21 17:48 ` [PATCH i-g-t v3 5/5] tests/prime_udl: Move into intel/ and add documentation Kamil Konieczny
2026-06-11 2:14 ` Karthik B S [this message]
2026-05-22 0:42 ` ✓ Xe.CI.BAT: success for Various fixes for prime_udl test (rev4) Patchwork
2026-05-22 0:56 ` ✓ i915.CI.BAT: " Patchwork
2026-05-22 8:30 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-23 8:31 ` ✓ i915.CI.Full: " Patchwork
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=c88bae25-6b0e-48d6-ad3f-00a7a8ae1032@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.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