Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] intel-ci/xe-fast-feedback.testlist: use xe_module_load@load
Date: Wed, 29 Mar 2023 14:37:07 +0200	[thread overview]
Message-ID: <20230329123707.2590437-1-mauro.chehab@linux.intel.com> (raw)

From: Mauro Carvalho Chehab <mchehab@kernel.org>

Provided that the force_load parameter is already set either as:

- boot time: xe.force_load=<value>
- modprobe time: adding "option xe force_load=<value>" to a
  /etc/modprobe.d/ file;
- at boot time, via CONFIG_DRM_XE_FORCE_PROBE="<value>"

There's no need to use igt@xe_module_load@force_load. Use
instead the cleaner test: igt@xe_module_load@load.

Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
 tests/intel-ci/xe-fast-feedback.testlist | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
index 3140d648833a..5f3bd2e917d5 100644
--- a/tests/intel-ci/xe-fast-feedback.testlist
+++ b/tests/intel-ci/xe-fast-feedback.testlist
@@ -1,5 +1,5 @@
 # Should be the first test
-igt@xe_module_load@force-load
+igt@xe_module_load@load
 
 igt@xe_compute@compute-square
 igt@xe_debugfs@base
-- 
2.39.2

             reply	other threads:[~2023-03-29 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 12:37 Mauro Carvalho Chehab [this message]
2023-03-29 13:02 ` [igt-dev] [PATCH i-g-t] intel-ci/xe-fast-feedback.testlist: use xe_module_load@load Dec, Katarzyna
2023-03-29 13:04 ` Mauro Carvalho Chehab
2023-03-29 13:39 ` [igt-dev] ✗ Fi.CI.BAT: failure for intel-ci/xe-fast-feedback.testlist: use xe_module_load@load (rev2) Patchwork
2023-03-30  3:12 ` [igt-dev] ✓ Fi.CI.IGT: success for intel-ci/xe-fast-feedback.testlist: use xe_module_load@load 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=20230329123707.2590437-1-mauro.chehab@linux.intel.com \
    --to=mauro.chehab@linux.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