From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BUILD: failure for series starting with [v3,1/2] drm/i915: Prevent HW access during init from SDVO TV get_modes hook
Date: Fri, 9 Feb 2024 19:48:46 +0200 [thread overview]
Message-ID: <ZcZlfpL29640umQM@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <170749938843.1129907.10081916788868767063@5338d5abeb45>
On Fri, Feb 09, 2024 at 05:23:08PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [v3,1/2] drm/i915: Prevent HW access during init from SDVO TV get_modes hook
> URL : https://patchwork.freedesktop.org/series/129727/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> CC [M] drivers/gpu/drm/i915/display/intel_sdvo.o
> drivers/gpu/drm/i915/display/intel_sdvo.c: In function ‘intel_sdvo_get_tv_modes’:
> drivers/gpu/drm/i915/display/intel_sdvo.c:2305:41: error: ‘i915’ undeclared (first use in this function); did you mean ‘I915’?
> 2305 | if (!intel_display_driver_check_access(i915))
> | ^~~~
> | I915
> drivers/gpu/drm/i915/display/intel_sdvo.c:2305:41: note: each undeclared identifier is reported only once for each function it appears in
> make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/i915/display/intel_sdvo.o] Error 1
> make[5]: *** [scripts/Makefile.build:481: drivers/gpu/drm/i915] Error 2
> make[4]: *** [scripts/Makefile.build:481: drivers/gpu/drm] Error 2
> make[3]: *** [scripts/Makefile.build:481: drivers/gpu] Error 2
> make[2]: *** [scripts/Makefile.build:481: drivers] Error 2
> make[1]: *** [/home/kbuild2/kernel/Makefile:1921: .] Error 2
> make: *** [Makefile:240: __sub-make] Error 2
> Build failed, no error log produced
Not sure why this fails, on latest drm-tip I get a different result, see
below.
Looks like an old tree is used as the base, could someone from the CI
team check this?
$ git fetch drm-tip
$ git reset --hard drm-tip/drm-tip
HEAD is now at 2aceb3c0b9c8c drm-tip: 2024y-02m-09d-12h-48m-25s UTC integration manifest
$ git am ~/imre.mbox
Applying: drm/i915: Prevent HW access during init from SDVO TV get_modes hook
Applying: drm/i915: Prevent HW access during init from connector get_modes hooks
$ make
CALL scripts/checksyscalls.sh
DESCEND objtool
INSTALL libsubcmd_headers
CC [M] drivers/gpu/drm/i915/display/intel_crt.o
CC [M] drivers/gpu/drm/i915/display/intel_dp_mst.o
CC [M] drivers/gpu/drm/i915/display/intel_dvo.o
CC [M] drivers/gpu/drm/i915/display/intel_sdvo.o
LD [M] drivers/gpu/drm/i915/i915.o
CC [M] drivers/gpu/drm/xe/i915-display/intel_dp_mst.o
LD [M] drivers/gpu/drm/xe/xe.o
MODPOST Module.symvers
Kernel: arch/x86/boot/bzImage is ready (#1476)
LD [M] drivers/gpu/drm/i915/i915.ko
LD [M] drivers/gpu/drm/xe/xe.ko
prev parent reply other threads:[~2024-02-09 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 16:03 [PATCH v3 1/2] drm/i915: Prevent HW access during init from SDVO TV get_modes hook Imre Deak
2024-02-09 16:03 ` [PATCH v3 2/2] drm/i915: Prevent HW access during init from connector get_modes hooks Imre Deak
2024-02-09 17:23 ` ✗ Fi.CI.BUILD: failure for series starting with [v3,1/2] drm/i915: Prevent HW access during init from SDVO TV get_modes hook Patchwork
2024-02-09 17:48 ` Imre Deak [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=ZcZlfpL29640umQM@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--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