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 drm/i915: include reductions
Date: Fri, 10 Dec 2021 15:03:38 +0200 [thread overview]
Message-ID: <87k0gc1uj9.fsf@intel.com> (raw)
In-Reply-To: <163910251850.3444.12839279379507056697@emeril.freedesktop.org>
On Fri, 10 Dec 2021, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/i915: include reductions
> URL : https://patchwork.freedesktop.org/series/97789/
> State : failure
>
> == Summary ==
>
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> CHK include/generated/compile.h
> CC [M] drivers/gpu/drm/i915/gem/i915_gem_create.o
> In file included from drivers/gpu/drm/i915/gem/i915_gem_create.c:9:
> ./drivers/gpu/drm/i915/pxp/intel_pxp.h: In function ‘intel_pxp_start’:
> ./drivers/gpu/drm/i915/pxp/intel_pxp.h:45:10: error: ‘ENODEV’ undeclared (first use in this function)
> return -ENODEV;
> ^~~~~~
> ./drivers/gpu/drm/i915/pxp/intel_pxp.h:45:10: note: each undeclared identifier is reported only once for each function it appears in
> ./drivers/gpu/drm/i915/pxp/intel_pxp.h: In function ‘intel_pxp_key_check’:
> ./drivers/gpu/drm/i915/pxp/intel_pxp.h:62:10: error: ‘ENODEV’ undeclared (first use in this function)
> return -ENODEV;
> ^~~~~~
> scripts/Makefile.build:287: recipe for target 'drivers/gpu/drm/i915/gem/i915_gem_create.o' failed
> make[4]: *** [drivers/gpu/drm/i915/gem/i915_gem_create.o] 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
I guess this means we have CONFIG_DRM_I915_PXP=n in CI.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2021-12-10 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 13:50 [Intel-gfx] [PATCH 0/7] drm/i915: include reductions Jani Nikula
2021-12-09 13:50 ` [Intel-gfx] [PATCH 1/7] drm/i915/reset: remove useless intel_display_types.h include Jani Nikula
2021-12-09 17:29 ` Ville Syrjälä
2021-12-09 19:17 ` Jani Nikula
2021-12-09 13:50 ` [Intel-gfx] [PATCH 2/7] drm/i915/active: remove useless i915_utils.h include Jani Nikula
2021-12-09 13:50 ` [Intel-gfx] [PATCH 3/7] drm/i915/psr: avoid intel_frontbuffer.h include with declaration Jani Nikula
2021-12-09 13:50 ` [Intel-gfx] [PATCH 4/7] drm/i915/fbc: " Jani Nikula
2021-12-09 13:51 ` [Intel-gfx] [PATCH 5/7] drm/i915/fb: reduce include dependencies Jani Nikula
2021-12-09 13:51 ` [Intel-gfx] [PATCH 6/7] drm/i915/pxp: un-inline intel_pxp_is_enabled() Jani Nikula
2021-12-09 13:51 ` [Intel-gfx] [PATCH 7/7] drm/i915/pxp: remove useless includes Jani Nikula
2021-12-09 17:32 ` [Intel-gfx] [PATCH 0/7] drm/i915: include reductions Ville Syrjälä
2021-12-10 2:15 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2021-12-10 13:03 ` 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=87k0gc1uj9.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