From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel graphics driver community testing & development
<intel-gfx@lists.freedesktop.org>,
Thomas Wood <thomas.wood@intel.com>
Subject: Re: [PATCH i-g-t] Add dmesg capture and dumping to tests and a test for it.
Date: Wed, 18 Nov 2015 17:32:59 +0000 [thread overview]
Message-ID: <20151118173259.GB1043@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20151118154420.GC20799@phenom.ffwll.local>
On Wed, Nov 18, 2015 at 04:44:20PM +0100, Daniel Vetter wrote:
> On Mon, Nov 16, 2015 at 03:22:23PM +0200, Joonas Lahtinen wrote:
> > Cc: Thomas Wood <thomas.wood@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Damien Lespiau <damien.lespiau@intel.com>
> > Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>
> Given that we have all that in piglit already the commit message is a bit
> thin on justification. Why do we need this in igt too? How does this
> interact with the piglit dmesg capture?
It's doesn't interfere with anyone else parsing kmsg/dmesg for
themselves, but it adds very useful functionality to standalone igt.
Which to me is significantly more valuable and I have been patching it
into igt for over a year and wished it was taken more seriously given
the number of incorrect bug reports generated.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-18 17:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 13:22 [PATCH i-g-t] Add dmesg capture and dumping to tests and a test for it Joonas Lahtinen
2015-11-16 14:06 ` Chris Wilson
2015-11-17 8:24 ` Joonas Lahtinen
2015-11-17 13:05 ` Thomas Wood
2015-11-17 13:34 ` Joonas Lahtinen
2015-11-18 15:44 ` Daniel Vetter
2015-11-18 17:32 ` Chris Wilson [this message]
2015-11-19 9:38 ` Daniel Vetter
2015-11-19 9:41 ` Daniel Vetter
2015-11-20 11:22 ` Joonas Lahtinen
2015-11-20 11:34 ` Chris Wilson
2015-11-23 10:31 ` Joonas Lahtinen
2015-11-19 10:35 ` [PATCH i-g-t v2] lib/igt_core: Add kmsg capture and dumping Joonas Lahtinen
2015-11-19 11:32 ` Chris Wilson
2015-11-20 11:46 ` Joonas Lahtinen
2015-11-26 12:17 ` [PATCH i-g-t v4] " Joonas Lahtinen
2015-11-26 14:34 ` Daniel Vetter
2015-11-26 15:00 ` Joonas Lahtinen
2015-11-27 10:31 ` Daniel Vetter
2015-11-27 11:46 ` Joonas Lahtinen
2015-11-30 8:09 ` Daniel Vetter
2015-11-18 17:41 ` [PATCH i-g-t] Add dmesg capture and dumping to tests and a test for it Thomas Wood
2015-11-18 18:12 ` Joonas Lahtinen
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=20151118173259.GB1043@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@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.