From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Fix build with WERROR=y
Date: Mon, 13 Mar 2023 13:08:35 +0200 [thread overview]
Message-ID: <ZA8EM6TXxenI38Gg@intel.com> (raw)
In-Reply-To: <167870533713.1029.7537039656477322671@emeril.freedesktop.org>
On Mon, Mar 13, 2023 at 11:02:17AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix build with WERROR=y
> URL : https://patchwork.freedesktop.org/series/115046/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> CC [M] drivers/gpu/drm/i915/gt/intel_workarounds.o
> In file included from drivers/gpu/drm/i915/gt/intel_workarounds.c:6:
> drivers/gpu/drm/i915/gt/intel_workarounds.c: In function ‘dg1_gt_workarounds_init’:
> drivers/gpu/drm/i915/gt/intel_workarounds.c:1482:13: error: ‘i915’ undeclared (first use in this function); did you mean ‘to_i915’?
Huh. I guess CI keeps on trying to build against the last succesfully
built drm-tip tag? But there is no hint here about that...
Ewelina, this seems to be another place where CI needs improvements:
- report the baseline against which the patch was applied
- report drm-tip build failures
> 1482 | if (IS_DG1(i915))
> | ^~~~
> ./drivers/gpu/drm/i915/i915_drv.h:559:45: note: in definition of macro ‘IS_DG1’
> 559 | #define IS_DG1(dev_priv) IS_PLATFORM(dev_priv, INTEL_DG1)
> | ^~~~~~~~
> drivers/gpu/drm/i915/gt/intel_workarounds.c:1482:13: note: each undeclared identifier is reported only once for each function it appears in
> 1482 | if (IS_DG1(i915))
> | ^~~~
> ./drivers/gpu/drm/i915/i915_drv.h:559:45: note: in definition of macro ‘IS_DG1’
> 559 | #define IS_DG1(dev_priv) IS_PLATFORM(dev_priv, INTEL_DG1)
> | ^~~~~~~~
> make[5]: *** [scripts/Makefile.build:252: drivers/gpu/drm/i915/gt/intel_workarounds.o] Error 1
> make[4]: *** [scripts/Makefile.build:494: drivers/gpu/drm/i915] Error 2
> make[3]: *** [scripts/Makefile.build:494: drivers/gpu/drm] Error 2
> make[2]: *** [scripts/Makefile.build:494: drivers/gpu] Error 2
> make[1]: *** [scripts/Makefile.build:494: drivers] Error 2
> make: *** [Makefile:2028: .] Error 2
>
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-03-13 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 9:39 [Intel-gfx] [PATCH] drm/i915: Fix build with WERROR=y Ville Syrjala
2023-03-13 10:20 ` Matthew Auld
2023-03-13 10:44 ` Ville Syrjälä
2023-03-13 10:59 ` Ville Syrjälä
2023-03-13 11:02 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2023-03-13 11:08 ` Ville Syrjälä [this message]
2023-03-13 11:24 ` Musial, Ewelina
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=ZA8EM6TXxenI38Gg@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.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;
as well as URLs for NNTP newsgroup(s).