public inbox for intel-gfx@lists.freedesktop.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.BAT: failure for series starting with [1/9] drm/i915/execlists: Avoid kicking priority on the current context (rev2)
Date: Wed, 05 Sep 2018 09:01:25 -0000	[thread overview]
Message-ID: <20180905090125.5308.21607@emeril.freedesktop.org> (raw)
In-Reply-To: <20180830100731.23085-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/9] drm/i915/execlists: Avoid kicking priority on the current context (rev2)
URL   : https://patchwork.freedesktop.org/series/48936/
State : failure

== Summary ==

Applying: drm/i915/execlists: Avoid kicking priority on the current context
Applying: drm/i915: Missed interrupt simulation is no more, tell the world
Applying: drm/i915/selftests: Basic stress test for rapid context switching
Applying: drm/i915/execlists: Delay updating ring register state after resume
Applying: drm/i915/execlists: Use coherent writes into the context image
Using index info to reconstruct a base tree...
M	drivers/gpu/drm/i915/i915_drv.h
M	drivers/gpu/drm/i915/i915_gem.c
M	drivers/gpu/drm/i915/i915_perf.c
M	drivers/gpu/drm/i915/intel_engine_cs.c
M	drivers/gpu/drm/i915/intel_lrc.c
M	drivers/gpu/drm/i915/intel_ringbuffer.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/intel_ringbuffer.c
Auto-merging drivers/gpu/drm/i915/intel_lrc.c
Auto-merging drivers/gpu/drm/i915/intel_engine_cs.c
Auto-merging drivers/gpu/drm/i915/i915_perf.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/i915_perf.c
Auto-merging drivers/gpu/drm/i915/i915_gem.c
Auto-merging drivers/gpu/drm/i915/i915_drv.h
error: Failed to merge in the changes.
Patch failed at 0005 drm/i915/execlists: Use coherent writes into the context image
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

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

      parent reply	other threads:[~2018-09-05  9:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 10:07 [PATCH 1/9] drm/i915/execlists: Avoid kicking priority on the current context Chris Wilson
2018-08-30 10:07 ` [PATCH 2/9] drm/i915: Missed interrupt simulation is no more, tell the world Chris Wilson
2018-08-30 10:07 ` [PATCH 3/9] drm/i915/selftests: Basic stress test for rapid context switching Chris Wilson
2018-09-05  7:24   ` [Intel-gfx] " Dan Carpenter
2018-09-05  8:50   ` [PATCH] " Chris Wilson
2018-08-30 10:07 ` [PATCH 4/9] drm/i915/execlists: Delay updating ring register state after resume Chris Wilson
2018-08-30 10:07 ` [PATCH 5/9] drm/i915/execlists: Use coherent writes into the context image Chris Wilson
2018-08-30 10:07 ` [PATCH 6/9] drm/i915/execlists: Onion unwind for logical_ring_init() failure Chris Wilson
2018-08-30 10:07 ` [PATCH 7/9] drm/i915: Report the number of closed vma held by each context in debugfs Chris Wilson
2018-08-30 10:07 ` [PATCH 8/9] drm/i915: Remove debugfs/i915_ppgtt_info Chris Wilson
2018-08-30 10:07 ` [PATCH 9/9] drm/i915/execlists: Assert the queue is non-empty on unsubmitting Chris Wilson
2018-08-30 12:15 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915/execlists: Avoid kicking priority on the current context Patchwork
2018-08-30 12:17 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-08-30 12:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-30 16:27 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-05  9:01 ` Patchwork [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=20180905090125.5308.21607@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox