public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BUILD: failure for series starting with [1/2] drm/i915: split out intel_vtd.[ch] from i915_drv.h
Date: Wed, 05 Jan 2022 11:42:40 +0200	[thread overview]
Message-ID: <878rvutt67.fsf@intel.com> (raw)
In-Reply-To: <164131025214.30367.4030655070429794711@emeril.freedesktop.org>

On Tue, 04 Jan 2022, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915: split out intel_vtd.[ch] from i915_drv.h
> URL   : https://patchwork.freedesktop.org/series/98471/
> State : failure
>
> == Summary ==
>
> CALL    scripts/checksyscalls.sh
>   CALL    scripts/atomic/check-atomics.sh
>   DESCEND objtool
>   CHK     include/generated/compile.h
>   HDRTEST drivers/gpu/drm/i915/intel_vtd.h
> In file included from ./drivers/gpu/drm/i915/intel_vtd.h:9,
>                  from <command-line>:
> ./arch/x86/include/asm/hypervisor.h:78:15: error: unknown type name ‘bool’
>  static inline bool hypervisor_is_type(enum x86_hypervisor_type type)

Hmph, that file is not self-contained. Sent v2 with the #include order
changed.

BR,
Jani.


>                ^~~~
> drivers/gpu/drm/i915/Makefile:343: recipe for target 'drivers/gpu/drm/i915/intel_vtd.hdrtest' failed
> make[4]: *** [drivers/gpu/drm/i915/intel_vtd.hdrtest] Error 1
> scripts/Makefile.build:549: recipe for target 'drivers/gpu/drm/i915' failed
> make[3]: *** [drivers/gpu/drm/i915] Error 2
> scripts/Makefile.build:549: recipe for target 'drivers/gpu/drm' failed
> make[2]: *** [drivers/gpu/drm] Error 2
> scripts/Makefile.build:549: recipe for target 'drivers/gpu' failed
> make[1]: *** [drivers/gpu] Error 2
> Makefile:1846: recipe for target 'drivers' failed
> make: *** [drivers] Error 2
>
>

-- 
Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2022-01-05  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 11:28 [Intel-gfx] [PATCH 1/2] drm/i915: split out intel_vtd.[ch] from i915_drv.h Jani Nikula
2022-01-04 11:28 ` [Intel-gfx] [PATCH 2/2] drm/i915/vtd: rename functions to have the usual prefix Jani Nikula
2022-01-04 14:54 ` [Intel-gfx] [PATCH 1/2] drm/i915: split out intel_vtd.[ch] from i915_drv.h kernel test robot
2022-01-04 15:30 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/2] " Patchwork
2022-01-05  9:42   ` Jani Nikula [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=878rvutt67.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=patchwork@emeril.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