public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Zack Rusin <zack@kde.org>
To: igt-dev@lists.freedesktop.org
Cc: krastevm@vmware.com, banackm@vmware.com, mombasawalam@vmware.com
Subject: [igt-dev] [PATCH i-g-t 3/3] igt: Switch warning to an info when not using i915
Date: Tue, 29 Nov 2022 12:27:18 -0500	[thread overview]
Message-ID: <20221129172718.151773-4-zack@kde.org> (raw)
In-Reply-To: <20221129172718.151773-1-zack@kde.org>

From: Zack Rusin <zackr@vmware.com>

Because igt always tries to load i915 driver first for DRIVER_ANY every
test using DRIVER_ANY on anything but i915 starts by printing a warning
that i915 couldn't be loaded.
Lets switch it to a general info line because it makes it hard to spot
actual warnings when every subtest starts by warning about not being
able to load i915.

Signed-off-by: Zack Rusin <zackr@vmware.com>
---
 lib/igt_kmod.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c
index bcf7dfeb..74924b5f 100644
--- a/lib/igt_kmod.c
+++ b/lib/igt_kmod.c
@@ -389,7 +389,7 @@ igt_i915_driver_load(const char *opts)
 
 	ret = igt_kmod_load("i915", opts);
 	if (ret) {
-		igt_warn("Could not load i915\n");
+		igt_debug("Could not load i915\n");
 		return ret;
 	}
 
-- 
2.37.2

  parent reply	other threads:[~2022-11-29 17:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 17:27 [igt-dev] [PATCH i-g-t 0/3] Add vmwgfx support Zack Rusin
2022-11-29 17:27 ` [igt-dev] [PATCH i-g-t 1/3] igt/vmwgfx: Add support for testing vmwgfx Zack Rusin
2023-01-26 18:13   ` Kamil Konieczny
2023-01-26 19:06     ` Zack Rusin
2023-02-17 17:50       ` Kamil Konieczny
2022-11-29 17:27 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_kms: vmwgfx returns 8 crtc Zack Rusin
2023-02-17 17:32   ` Kamil Konieczny
2022-11-29 17:27 ` Zack Rusin [this message]
2023-01-26 18:17   ` [igt-dev] [PATCH i-g-t 3/3] igt: Switch warning to an info when not using i915 Kamil Konieczny
2023-01-26 19:11     ` Zack Rusin
2023-01-27 14:29       ` Kamil Konieczny
2023-01-27 14:35         ` Petri Latvala
2023-01-27 16:51           ` Kamil Konieczny
2023-02-17 17:35       ` Kamil Konieczny
2022-11-29 19:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add vmwgfx support Patchwork
2022-11-29 20:02 ` [igt-dev] ✗ Fi.CI.BAT: failure " 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=20221129172718.151773-4-zack@kde.org \
    --to=zack@kde.org \
    --cc=banackm@vmware.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=krastevm@vmware.com \
    --cc=mombasawalam@vmware.com \
    --cc=zackr@vmware.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