All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Ro.CI.BAT: failure for series starting with [1/2] lib/gt: Omit illegal instruction on hang injection with gen 8+
Date: Thu, 23 Jun 2016 08:49:43 -0000	[thread overview]
Message-ID: <20160623084943.30838.38483@emeril.freedesktop.org> (raw)
In-Reply-To: <1465391238-32737-1-git-send-email-mika.kuoppala@intel.com>

== Series Details ==

Series: series starting with [1/2] lib/gt: Omit illegal instruction on hang injection with gen 8+
URL   : https://patchwork.freedesktop.org/series/8452/
State : failure

== Summary ==

Applying: lib/gt: Omit illegal instruction on hang injection with gen 8+
fatal: sha1 information is lacking or useless (lib/igt_gt.c).
error: could not build fake ancestor
Patch failed at 0001 lib/gt: Omit illegal instruction on hang injection with gen 8+
The copy of the patch that failed is found in: .git/rebase-apply/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:[~2016-06-23  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 13:07 [PATCH 1/2] lib/gt: Omit illegal instruction on hang injection with gen 8+ Mika Kuoppala
2016-06-08 13:07 ` [PATCH 2/2] igt/gem_reset_stats: Add time constraints on hang detection Mika Kuoppala
2016-06-08 13:59   ` Chris Wilson
2016-06-08 13:54 ` [PATCH 1/2] lib/gt: Omit illegal instruction on hang injection with gen 8+ Chris Wilson
2016-06-23  8:49 ` 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=20160623084943.30838.38483@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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.