All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for GVT device model split
Date: Mon, 26 Nov 2018 06:23:04 -0000	[thread overview]
Message-ID: <20181126062304.25188.42380@emeril.freedesktop.org> (raw)
In-Reply-To: <20181126060554.16481-1-zhenyuw@linux.intel.com>

== Series Details ==

Series: GVT device model split
URL   : https://patchwork.freedesktop.org/series/52994/
State : failure

== Summary ==

CALL    scripts/checksyscalls.sh
  DESCEND  objtool
  CHK     include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready  (#1)
  Building modules, stage 2.
  MODPOST 112 modules
ERROR: "i915_fence_ops" [drivers/gpu/drm/i915/gvt/i915_gvt.ko] undefined!
scripts/Makefile.modpost:92: recipe for target '__modpost' failed
make[1]: *** [__modpost] Error 1
Makefile:1269: recipe for target 'modules' failed
make: *** [modules] Error 2

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

      parent reply	other threads:[~2018-11-26  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  6:05 [RFC PATCH v2 0/2] GVT device model split Zhenyu Wang
2018-11-26  6:05 ` [RFC PATCH v2 1/2] drm/i915: Export current required functions for GVT Zhenyu Wang
2018-12-20  9:56   ` Joonas Lahtinen
2018-11-26  6:05 ` [RFC PATCH v2 2/2] drm/i915: Move GVT device model into separate module Zhenyu Wang
2018-12-20  9:58   ` Joonas Lahtinen
2018-11-26  6:23 ` 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=20181126062304.25188.42380@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=zhenyuw@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.