From: Jani Nikula <jani.nikula@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
Jocelyn Falempe <jfalempe@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BUILD: failure for drm/i915: Add drm_panic support
Date: Mon, 02 Dec 2024 11:59:27 +0200 [thread overview]
Message-ID: <87y10y5rsw.fsf@intel.com> (raw)
In-Reply-To: <173289848796.343649.11337293273413208343@b555e5b46a47>
On Fri, 29 Nov 2024, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/i915: Add drm_panic support
> URL : https://patchwork.freedesktop.org/series/141935/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> CC [M] drivers/gpu/drm/xe/i915-display/intel_atomic_plane.o
> drivers/gpu/drm/i915/display/intel_atomic_plane.c:46:10: fatal error: gem/i915_gem_object.h: No such file or directory
> 46 | #include "gem/i915_gem_object.h"
> | ^~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
The i915 display code is reused in xe with some Makefile magic. You'll
need to enable both i915 and xe configs when making changes.
You can't use gem/i915_gem_object.h from code that gets built for
xe. See intel_bo.[ch] in both i915 and xe for abstraction.
BR,
Jani.
> make[6]: *** [drivers/gpu/drm/xe/Makefile:165: drivers/gpu/drm/xe/i915-display/intel_atomic_plane.o] Error 1
> make[5]: *** [scripts/Makefile.build:478: drivers/gpu/drm/xe] Error 2
> make[4]: *** [scripts/Makefile.build:478: drivers/gpu/drm] Error 2
> make[3]: *** [scripts/Makefile.build:478: drivers/gpu] Error 2
> make[2]: *** [scripts/Makefile.build:478: drivers] Error 2
> make[1]: *** [/home/kbuild2/kernel/Makefile:1936: .] Error 2
> make: *** [Makefile:224: __sub-make] Error 2
> Build failed, no error log produced
>
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-02 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 16:20 [RFC PATCH 0/5] drm/i915: Add drm_panic support Jocelyn Falempe
2024-11-29 16:20 ` [PATCH 1/5] drm/i915/fbdev: Add intel_fbdev_getvaddr() Jocelyn Falempe
2024-11-29 22:39 ` kernel test robot
2024-11-29 23:31 ` kernel test robot
2024-11-29 16:20 ` [PATCH 2/5] drm/i915/display/i9xx: Add a disable_tiling() for i9xx planes Jocelyn Falempe
2024-11-29 16:20 ` [PATCH 3/5] drm/i915/display: Add a disable_tiling() for skl planes Jocelyn Falempe
2024-11-29 16:20 ` [PATCH 4/5] drm/i915/gem: export i915_gem_object_map_page/pfn Jocelyn Falempe
2024-11-29 16:20 ` [PATCH 5/5] drm/i915: Add drm_panic support Jocelyn Falempe
2024-11-29 22:18 ` kernel test robot
2024-11-30 10:48 ` kernel test robot
2024-11-29 16:41 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2024-12-02 9:59 ` Jani Nikula [this message]
2024-12-02 13:36 ` Jocelyn Falempe
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=87y10y5rsw.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--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