From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/2] Selftest fixes for 6.1
Date: Wed, 19 Oct 2022 16:01:04 +0100 [thread overview]
Message-ID: <42c62a7c-f063-ee66-c643-c5d5d55ff2cf@linux.intel.com> (raw)
In-Reply-To: <20221019121007.3229024-1-tvrtko.ursulin@linux.intel.com>
On 19/10/2022 13:10, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Warning - not much tested, mainly bypassing trybot for quick turnaround.
Please ignore - this is quite broken and problem more complicated.
Regards,
Tvrtko
> Tvrtko Ursulin (2):
> drm/i915/selftests: Fix waiting for threads to start
> drm/i915/selftests: Fix selftests for 6.1 kthread_stop semantics
>
> .../drm/i915/gem/selftests/i915_gem_context.c | 9 +-
> drivers/gpu/drm/i915/gt/selftest_execlists.c | 13 +-
> drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 5 +-
> drivers/gpu/drm/i915/i915_selftest.h | 14 ++
> drivers/gpu/drm/i915/selftests/i915_request.c | 136 ++++++++++++------
> .../gpu/drm/i915/selftests/i915_selftest.c | 18 +++
> 6 files changed, 140 insertions(+), 55 deletions(-)
>
prev parent reply other threads:[~2022-10-19 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 12:10 [Intel-gfx] [PATCH 0/2] Selftest fixes for 6.1 Tvrtko Ursulin
2022-10-19 12:10 ` [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Fix waiting for threads to start Tvrtko Ursulin
2022-10-19 12:10 ` [Intel-gfx] [PATCH 2/2] drm/i915/selftests: Fix selftests for 6.1 kthread_stop semantics Tvrtko Ursulin
2022-10-19 14:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Selftest fixes for 6.1 Patchwork
2022-10-19 14:28 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-19 14:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-19 15:01 ` Tvrtko Ursulin [this message]
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=42c62a7c-f063-ee66-c643-c5d5d55ff2cf@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox