From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ser, Simon" <simon.ser@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "paul.kocialkowski@linux.intel.com" <paul.kocialkowski@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] audio: Avoid test_integrity failing if there's no HW support
Date: Wed, 24 Apr 2019 15:50:19 +0300 [thread overview]
Message-ID: <87o94vtvn8.fsf@intel.com> (raw)
In-Reply-To: <2928dcec0ecacd3d471c70c0d7baf54770f7e9a1.camel@intel.com>
On Tue, 23 Apr 2019, "Ser, Simon" <simon.ser@intel.com> wrote:
> Oh, I mixed up igt_assert and igt_require again.
Don't worry, I still have to look it up every time.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-24 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 7:52 [igt-dev] [PATCH i-g-t] tests/intel-ci: blacklist audio tests Simon Ser
2019-04-23 8:09 ` [igt-dev] [PATCH i-g-t] audio: Avoid test_integrity failing if there's no HW support Chris Wilson
2019-04-23 9:09 ` Chris Wilson
2019-04-23 11:45 ` Ser, Simon
2019-04-23 12:00 ` Chris Wilson
2019-04-23 13:09 ` Ser, Simon
2019-04-24 12:50 ` Jani Nikula [this message]
2019-04-25 11:12 ` Ser, Simon
2019-04-23 9:05 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/intel-ci: blacklist audio tests (rev2) Patchwork
2019-04-23 9:10 ` [igt-dev] [PATCH i-g-t] audio: Avoid test_integrity failing if there's no HW support Chris Wilson
2019-04-23 9:52 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/intel-ci: blacklist audio tests (rev3) Patchwork
2019-04-23 11:07 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/intel-ci: blacklist audio tests (rev2) 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=87o94vtvn8.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=paul.kocialkowski@linux.intel.com \
--cc=simon.ser@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