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 add more probe failures (rev4)
Date: Thu, 01 Aug 2019 21:39:04 -0000 [thread overview]
Message-ID: <20190801213904.30399.311@emeril.freedesktop.org> (raw)
In-Reply-To: <20190801161059.36844-1-michal.wajdeczko@intel.com>
== Series Details ==
Series: add more probe failures (rev4)
URL : https://patchwork.freedesktop.org/series/64390/
State : failure
== Summary ==
Applying: drm/i915: Add i915 to i915_inject_probe_failure
Applying: drm/i915/uc: Inject probe errors into intel_uc_init_hw
Applying: drm/i915/wopcm: Don't fail on WOPCM partitioning failure
error: sha1 information is lacking or useless (drivers/gpu/drm/i915/gt/uc/intel_uc.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch' to see the failed patch
Patch failed at 0003 drm/i915/wopcm: Don't fail on WOPCM partitioning failure
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
prev parent reply other threads:[~2019-08-01 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:10 [CI 0/3] add more probe failures Michal Wajdeczko
2019-08-01 16:10 ` [CI 1/3] drm/i915: Add i915 to i915_inject_probe_failure Michal Wajdeczko
2019-08-01 16:10 ` [CI 2/3] drm/i915/uc: Inject probe errors into intel_uc_init_hw Michal Wajdeczko
2019-08-01 16:10 ` [CI 3/3] drm/i915/wopcm: Don't fail on WOPCM partitioning failure Michal Wajdeczko
2019-08-01 21:39 ` 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=20190801213904.30399.311@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.