All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [1/7] drm/i915/selftests: Smoketest preemption (rev2)
Date: Tue, 25 Sep 2018 10:31:32 -0000	[thread overview]
Message-ID: <20180925103132.24226.77020@emeril.freedesktop.org> (raw)
In-Reply-To: <20180925083205.2229-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/7] drm/i915/selftests: Smoketest preemption (rev2)
URL   : https://patchwork.freedesktop.org/series/50137/
State : warning

== Summary ==

$ dim sparse origin/drm-tip
Commit: drm/i915/selftests: Smoketest preemption
+./include/linux/slab.h:631:13: error: undefined identifier '__builtin_mul_overflow'
+./include/linux/slab.h:631:13: warning: call with no type!

Commit: drm/i915/execlists: Avoid kicking priority on the current context
Okay!

Commit: drm/i915: Reserve some priority bits for internal use
Okay!

Commit: drm/i915: Combine multiple internal plists into the same i915_priolist bucket
Okay!

Commit: drm/i915: Priority boost for new clients
Okay!

Commit: drm/i915: Pull scheduling under standalone lock
+./include/uapi/linux/perf_event.h:147:56: warning: cast truncates bits from constant value (8000000000000000 becomes 0)

Commit: drm/i915: Priority boost for waiting clients
Okay!

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-09-25 10:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  8:31 [PATCH 1/7] drm/i915/selftests: Smoketest preemption Chris Wilson
2018-09-25  8:31 ` [PATCH 2/7] drm/i915/execlists: Avoid kicking priority on the current context Chris Wilson
2018-09-25 10:14   ` Tvrtko Ursulin
2018-09-25  8:32 ` [PATCH 3/7] drm/i915: Reserve some priority bits for internal use Chris Wilson
2018-09-25  8:32 ` [PATCH 4/7] drm/i915: Combine multiple internal plists into the same i915_priolist bucket Chris Wilson
2018-09-25  9:48   ` Tvrtko Ursulin
2018-09-27 13:05     ` Chris Wilson
2018-09-28 13:04       ` Tvrtko Ursulin
2018-09-28 13:08         ` Chris Wilson
2018-09-28 13:25           ` Tvrtko Ursulin
2018-09-25  8:32 ` [PATCH 5/7] drm/i915: Priority boost for new clients Chris Wilson
2018-09-25  8:32 ` [PATCH 6/7] drm/i915: Pull scheduling under standalone lock Chris Wilson
2018-09-25  8:32 ` [PATCH 7/7] drm/i915: Priority boost for waiting clients Chris Wilson
2018-09-25  9:04   ` [PATCH v2] " Chris Wilson
2018-09-25  9:09 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915/selftests: Smoketest preemption Patchwork
2018-09-25  9:12 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-09-25  9:31 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-25  9:39 ` [PATCH 1/7] " Tvrtko Ursulin
2018-09-25 10:17   ` Chris Wilson
2018-09-25 10:24     ` Tvrtko Ursulin
2018-09-25 10:28 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915/selftests: Smoketest preemption (rev2) Patchwork
2018-09-25 10:31 ` Patchwork [this message]
2018-09-25 10:50 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-25 12:21 ` ✓ Fi.CI.IGT: " 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=20180925103132.24226.77020@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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.