From: "liu,lei" <lei.a.liu@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: yex.tian@intel.com, "liu,lei" <lei.a.liu@intel.com>,
gordon.jin@intel.com
Subject: [PATCH] Correct kms_fbc_crc case Debugfs i915_fbc_status shows "FBC unsupported on this chipset" not "unsupported by this chipset" if the platform doesn't support FBC feature. That typo will cause case fail on some platforms such as byt , bsw.
Date: Thu, 9 Apr 2015 13:51:24 +0800 [thread overview]
Message-ID: <1428558684-19299-1-git-send-email-lei.a.liu@intel.com> (raw)
From: "liu,lei" <lei.a.liu@intel.com>
---
tests/kms_fbc_crc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/kms_fbc_crc.c b/tests/kms_fbc_crc.c
index ccdec33..1320bad 100644
--- a/tests/kms_fbc_crc.c
+++ b/tests/kms_fbc_crc.c
@@ -513,7 +513,7 @@ igt_main
igt_assert_lt(0, fread(buf, 1, sizeof(buf), status));
fclose(status);
buf[sizeof(buf) - 1] = '\0';
- igt_require_f(!strstr(buf, "unsupported by this chipset") &&
+ igt_require_f(!strstr(buf, "unsupported on this chipset") &&
!strstr(buf, "disabled per module param") &&
!strstr(buf, "disabled per chip default"),
"FBC not supported/enabled\n");
--
1.8.3.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-04-09 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 5:51 liu,lei [this message]
2015-04-09 12:23 ` [PATCH] Correct kms_fbc_crc case Debugfs i915_fbc_status shows "FBC unsupported on this chipset" not "unsupported by this chipset" if the platform doesn't support FBC feature. That typo will cause case fail on some platforms such as byt , bsw Daniel Vetter
2015-04-09 13:28 ` [PATCH] Correct kms_fbc_crc case Debugfs i915_fbc_status shows "FBC unsupported on this chipset" not "unsupported by this chipset" if the platform doesn't support FBC feature. That typo will cause case fail on some platforms such as byt Liu, Lei A
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=1428558684-19299-1-git-send-email-lei.a.liu@intel.com \
--to=lei.a.liu@intel.com \
--cc=gordon.jin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yex.tian@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.