From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>,
Vivek Kasireddy <vivek.kasireddy@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (rev2)
Date: Mon, 7 Feb 2022 10:51:54 +0000 [thread overview]
Message-ID: <7d4c2ea8-5740-b64c-6dad-e554d5863607@linux.intel.com> (raw)
In-Reply-To: <164393912057.12040.4398452822283629082@emeril.freedesktop.org>
On 04/02/2022 01:45, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (rev2)
> URL : https://patchwork.freedesktop.org/series/99597/
> 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/i915_gem.o
> drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_object_fits_in_aperture’:
> drivers/gpu/drm/i915/i915_gem.c:944:2: error: implicit declaration of function ‘drm_mm_for_each_suitable_hole’; did you mean ‘drm_mm_for_each_best_hole’? [-Werror=implicit-function-declaration]
> drm_mm_for_each_suitable_hole(hole, &ggtt->vm.mm, 0, ggtt->mappable_end,
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drm_mm_for_each_best_hole
> drivers/gpu/drm/i915/i915_gem.c:945:41: error: expected ‘;’ before ‘{’ token
> fence_size, DRM_MM_INSERT_LOW) {
> ^~
> ;
> drivers/gpu/drm/i915/i915_gem.c:889:15: error: unused variable ‘count’ [-Werror=unused-variable]
> unsigned int count = 0;
> ^~~~~
> drivers/gpu/drm/i915/i915_gem.c:887:35: error: unused variable ‘end’ [-Werror=unused-variable]
> u64 hole_start, hole_end, start, end;
> ^~~
> drivers/gpu/drm/i915/i915_gem.c:887:28: error: unused variable ‘start’ [-Werror=unused-variable]
> u64 hole_start, hole_end, start, end;
> ^~~~~
> drivers/gpu/drm/i915/i915_gem.c:887:18: error: unused variable ‘hole_end’ [-Werror=unused-variable]
> u64 hole_start, hole_end, start, end;
> ^~~~~~~~
> drivers/gpu/drm/i915/i915_gem.c:887:6: error: unused variable ‘hole_start’ [-Werror=unused-variable]
> u64 hole_start, hole_end, start, end;
> ^~~~~~~~~~
> drivers/gpu/drm/i915/i915_gem.c:964:1: error: control reaches end of non-void function [-Werror=return-type]
> }
> ^
> cc1: all warnings being treated as errors
> scripts/Makefile.build:288: recipe for target 'drivers/gpu/drm/i915/i915_gem.o' failed
> make[4]: *** [drivers/gpu/drm/i915/i915_gem.o] Error 1
> scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm/i915' failed
> make[3]: *** [drivers/gpu/drm/i915] Error 2
> scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm' failed
> make[2]: *** [drivers/gpu/drm] Error 2
> scripts/Makefile.build:550: recipe for target 'drivers/gpu' failed
> make[1]: *** [drivers/gpu] Error 2
> Makefile:1831: recipe for target 'drivers' failed
> make: *** [drivers] Error 2
Just post both patches to both intel-gfx and dri-devel as a series so
patchwork picks it up correctly.
It is needed to give context to dri-devel folks anyway.
Regards,
Tvrtko
prev parent reply other threads:[~2022-02-07 10:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 1:11 [Intel-gfx] [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation Vivek Kasireddy
2022-02-02 1:11 ` [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v5) Vivek Kasireddy
2022-02-02 13:19 ` Tvrtko Ursulin
2022-02-04 1:22 ` [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6) Vivek Kasireddy
2022-02-07 10:49 ` Tvrtko Ursulin
2022-02-07 10:58 ` Ville Syrjälä
2022-02-07 11:47 ` Tvrtko Ursulin
2022-02-07 13:24 ` Ville Syrjälä
2022-02-07 13:36 ` Tvrtko Ursulin
2022-02-08 5:10 ` Kasireddy, Vivek
2022-02-08 5:43 ` Ville Syrjälä
2022-02-09 1:47 ` Kasireddy, Vivek
2022-02-09 7:42 ` Ville Syrjälä
2022-02-10 1:41 ` Kasireddy, Vivek
2022-02-02 1:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation Patchwork
2022-02-02 1:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-02 2:09 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-04 1:45 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (rev2) Patchwork
2022-02-07 10:51 ` Tvrtko Ursulin [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=7d4c2ea8-5740-b64c-6dad-e554d5863607@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=vivek.kasireddy@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.