From: Patchwork <patchwork@emeril.freedesktop.org>
To: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for GuC suspend paths cleanup (rev2)
Date: Wed, 20 Feb 2019 01:29:34 -0000 [thread overview]
Message-ID: <20190220012934.5013.94902@emeril.freedesktop.org> (raw)
In-Reply-To: <20190220004102.459-1-sujaritha.sundaresan@intel.com>
== Series Details ==
Series: GuC suspend paths cleanup (rev2)
URL : https://patchwork.freedesktop.org/series/56697/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC [M] drivers/gpu/drm/i915/intel_guc_ct.o
drivers/gpu/drm/i915/intel_guc_ct.c: In function ‘ctch_enable’:
drivers/gpu/drm/i915/intel_guc_ct.c:229:2: error: expected ‘;’ before ‘base’
base = intel_guc_ggtt_offset(guc, ctch->vma);
^~~~
scripts/Makefile.build:276: recipe for target 'drivers/gpu/drm/i915/intel_guc_ct.o' failed
make[4]: *** [drivers/gpu/drm/i915/intel_guc_ct.o] Error 1
scripts/Makefile.build:492: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:492: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:492: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1043: recipe for target 'drivers' failed
make: *** [drivers] Error 2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-02-20 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 0:41 [PATCH v2 0/2] GuC suspend paths cleanup Sujaritha Sundaresan
2019-02-20 0:41 ` [PATCH v2 1/2] drm/i915/guc: Splitting CT channel open/close functions Sujaritha Sundaresan
2019-02-20 0:41 ` [PATCH v2 2/2] drm/i915/guc: Calling guc_disable_communication in all suspend paths Sujaritha Sundaresan
2019-02-20 1:29 ` 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=20190220012934.5013.94902@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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