From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] tests: New dir structure for intel specific tests
Date: Wed, 26 Apr 2023 10:44:42 +0200 [thread overview]
Message-ID: <20230426104442.6fa26e13@maurocar-mobl2> (raw)
In-Reply-To: <20230424080233.2016931-1-bhanuprakash.modem@intel.com>
On Mon, 24 Apr 2023 13:32:33 +0530
Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
> As we have many KMS tests those can support both i915 & XE, we
> can have new dir structure to place tests in a proper location.
>
> Below is the new dir structure:
> - tests/intel/i915/ : All i915 specific tests should move here.
> - tests/intel/xe/ : All XE specific tests should move here.
> - tests/intel/ : Tests those supports both i915 & XE should
> move here. Example: kms_psr
Hmm... having xe and i915 common tests under tests/intel makes sense
to me.
Yet, IMO, if we're doing a change like that, IMO we also need to:
- do a similar change for lib/ - which also has some parts that
are common to both drivers and some that are driver-specific;
- double-check the IGT test namespace for it to properly reflect
the Intel common testset;
- Maybe split the test lists into 3 separate sets.
Regards,
Mauro
next prev parent reply other threads:[~2023-04-26 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 8:02 [igt-dev] [i-g-t] tests: New dir structure for intel specific tests Bhanuprakash Modem
2023-04-24 11:01 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-24 13:05 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-04-25 3:53 ` [igt-dev] [i-g-t] " Zbigniew Kempczyński
2023-04-26 8:44 ` Mauro Carvalho Chehab [this message]
2023-04-26 13:53 ` Kamil Konieczny
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=20230426104442.6fa26e13@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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