From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH igt] lib: Check and report if a subtest triggers a new kernel taint
Date: Mon, 04 Dec 2017 15:46:31 +0200 [thread overview]
Message-ID: <1512395191.4394.40.camel@linux.intel.com> (raw)
In-Reply-To: <20171129123023.4050-1-chris@chris-wilson.co.uk>
On Wed, 2017-11-29 at 12:30 +0000, Chris Wilson wrote:
> Checking for a tainted kernel is a convenient way to see if the test
> generated a critical error such as a oops, or machine check.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Radoslaw Szwichtenberg <radoslaw.szwichtenberg@intel.com>
Reviewed-by: Joonas Lahtien <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-12-04 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 12:30 [PATCH igt] lib: Check and report if a subtest triggers a new kernel taint Chris Wilson
2017-11-29 12:40 ` Chris Wilson
2017-11-29 13:14 ` Szwichtenberg, Radoslaw
2017-11-29 13:23 ` Chris Wilson
2017-11-29 13:43 ` Chris Wilson
2017-11-29 14:34 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-29 17:46 ` ✓ Fi.CI.IGT: " Patchwork
2017-12-04 13:46 ` Joonas Lahtinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 12:24 [PATCH igt] " Chris Wilson
2017-12-05 12:32 ` Petri Latvala
2017-12-05 12:38 ` Chris Wilson
2017-12-05 13:01 ` Petri Latvala
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=1512395191.4394.40.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@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 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.