From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 3/3] intel_gvtg_test: Handle system(3) return value.
Date: Fri, 3 Nov 2017 12:01:41 +0000 [thread overview]
Message-ID: <2f323f7c-3c99-a84a-84c0-f556f264a189@linux.intel.com> (raw)
In-Reply-To: <150971013404.13980.11217284810430958626@mail.alporthouse.com>
On 03/11/2017 11:55, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2017-11-03 11:47:56)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Avoid the build warning by checking the pkill either did not find
>> any guests or managed to send a signal to all of them.
>
> This is tools, do we have the igt framework so that calling igt_assert
> when lead to a confusing mass of "not in a test" warnings?
Who knows, but the tools was already using them. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-03 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 11:47 [PATCH i-g-t 1/3] lib/core: Avoid unused result in backtrace printing Tvrtko Ursulin
2017-11-03 11:47 ` [PATCH i-g-t 2/3] gem_syslatency: Avoid arithmetic on void * warning Tvrtko Ursulin
2017-11-03 11:53 ` Chris Wilson
2017-11-03 11:47 ` [PATCH i-g-t 3/3] intel_gvtg_test: Handle system(3) return value Tvrtko Ursulin
2017-11-03 11:55 ` Chris Wilson
2017-11-03 12:01 ` Tvrtko Ursulin [this message]
2017-11-03 11:52 ` [PATCH i-g-t 1/3] lib/core: Avoid unused result in backtrace printing Chris Wilson
2017-11-03 12:04 ` Tvrtko Ursulin
2017-11-03 12:10 ` Chris Wilson
2017-11-03 12:56 ` Tvrtko Ursulin
2017-11-03 13:02 ` Chris Wilson
2017-11-03 13:07 ` Tvrtko Ursulin
2017-11-03 13:09 ` [PATCH i-g-t v2 " Tvrtko Ursulin
2017-11-03 12:20 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] " Patchwork
2017-11-03 14:18 ` ✗ Fi.CI.BAT: warning for series starting with [v2,1/3] lib/core: Avoid unused result in backtrace printing (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=2f323f7c-3c99-a84a-84c0-f556f264a189@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=tursulin@ursulin.net \
/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.