From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for CPU + GPU synchronised priority scheduling (rev2)
Date: Mon, 04 Oct 2021 16:17:00 -0000 [thread overview]
Message-ID: <163336422049.1480.11440821032562102227@emeril.freedesktop.org> (raw)
In-Reply-To: <20211004143650.699120-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: CPU + GPU synchronised priority scheduling (rev2)
URL : https://patchwork.freedesktop.org/series/95294/
State : failure
== Summary ==
fatal: empty ident name (for <>) not allowed
Applying: effective and consolidated user experience. In other words why user would not be
next prev parent reply other threads:[~2021-10-04 16:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 14:36 [RFC v2 0/8] CPU + GPU synchronised priority scheduling Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 1/8] sched: Add nice value change notifier Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-06 4:10 ` Wanghui (John)
2021-10-06 4:10 ` [Intel-gfx] " Wanghui (John)
2021-10-06 7:58 ` Barry Song
2021-10-06 7:58 ` [Intel-gfx] " Barry Song
2021-10-06 13:44 ` Tvrtko Ursulin
2021-10-06 13:44 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-06 20:21 ` Barry Song
2021-10-06 20:21 ` [Intel-gfx] " Barry Song
2021-10-07 8:50 ` Tvrtko Ursulin
2021-10-07 8:50 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-07 9:09 ` Tvrtko Ursulin
2021-10-07 9:09 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-07 10:00 ` Barry Song
2021-10-07 10:00 ` [Intel-gfx] " Barry Song
2021-10-04 14:36 ` [RFC 2/8] drm/i915: Explicitly track DRM clients Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 3/8] drm/i915: Make GEM contexts " Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 4/8] drm/i915: Track all user contexts per client Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 5/8] drm/i915: Keep track of registered clients indexed by task struct Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 6/8] drm/i915: Make some recently added vfuncs use full scheduling attribute Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-06 17:12 ` Matthew Brost
2021-10-06 17:12 ` [Intel-gfx] " Matthew Brost
2021-10-06 19:06 ` Tvrtko Ursulin
2021-10-06 19:06 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-13 12:01 ` Daniel Vetter
2021-10-13 15:50 ` Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 7/8] drm/i915: Inherit process nice for context scheduling priority Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-06 17:16 ` Matthew Brost
2021-10-06 17:24 ` Matthew Brost
2021-10-06 18:42 ` Tvrtko Ursulin
2021-10-04 14:36 ` [RFC 8/8] drm/i915: Connect with the process nice change notifier Tvrtko Ursulin
2021-10-04 14:36 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 16:17 ` Patchwork [this message]
2021-10-05 12:10 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for CPU + GPU synchronised priority scheduling (rev3) Patchwork
2021-10-05 23:48 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for CPU + GPU synchronised priority scheduling (rev4) 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=163336422049.1480.11440821032562102227@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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.