From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: failure for Refactor to expand subslice mask (rev6)
Date: Wed, 1 May 2019 15:36:16 +0000 [thread overview]
Message-ID: <ca4377c7d95e4c361693e84b3213402f011feced.camel@intel.com> (raw)
In-Reply-To: <20190501005822.26874.38164@emeril.freedesktop.org>
[-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --]
On Wed, 2019-05-01 at 00:58 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: Refactor to expand subslice mask (rev6)
> URL : https://patchwork.freedesktop.org/series/59742/
> State : failure
I'm not sure what happened here, but my assumption is that CI didn't
like the fact that I sent a single update to the series without the
entire series. I sent a fully rebased series (as of this morning) to
trybot and had no issues. So I went ahead and sent an updated series to
this list to trigger CI and push for review. Sorry for the spam!
-Stuart
>
> == Summary ==
>
> Applying: drm/i915: Use local variable for SSEU info in GETPARAM
> ioctl
> Applying: drm/i915: Add macro for SSEU stride calculation
> Applying: drm/i915: Move calculation of subslices per slice to new
> function
> Applying: drm/i915: Move sseu helper functions to intel_sseu.h
> Applying: drm/i915: Remove inline from sseu helper functions
> Applying: drm/i915: Expand subslice mask
> error: sha1 information is lacking or useless
> (drivers/gpu/drm/i915/i915_debugfs.c).
> error: could not build fake ancestor
> hint: Use 'git am --show-current-patch' to see the failed patch
> Patch failed at 0006 drm/i915: Expand subslice mask
> 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".
>
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3270 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-05-01 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 23:06 [PATCH 0/6] Refactor to expand subslice mask Stuart Summers
2019-04-30 23:06 ` [PATCH 1/6] drm/i915: Use local variable for SSEU info in GETPARAM ioctl Stuart Summers
2019-05-01 0:44 ` Stuart Summers
2019-04-30 23:06 ` [PATCH 2/6] drm/i915: Add macro for SSEU stride calculation Stuart Summers
2019-04-30 23:06 ` [PATCH 3/6] drm/i915: Move calculation of subslices per slice to new function Stuart Summers
2019-04-30 23:06 ` [PATCH 4/6] drm/i915: Move sseu helper functions to intel_sseu.h Stuart Summers
2019-04-30 23:06 ` [PATCH 5/6] drm/i915: Remove inline from sseu helper functions Stuart Summers
2019-04-30 23:06 ` [PATCH 6/6] drm/i915: Expand subslice mask Stuart Summers
2019-04-30 23:13 ` ✗ Fi.CI.CHECKPATCH: warning for Refactor to expand subslice mask (rev5) Patchwork
2019-04-30 23:16 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-01 0:00 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-01 0:58 ` ✗ Fi.CI.BAT: failure for Refactor to expand subslice mask (rev6) Patchwork
2019-05-01 15:36 ` Summers, Stuart [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=ca4377c7d95e4c361693e84b3213402f011feced.camel@intel.com \
--to=stuart.summers@intel.com \
--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