From: Mark Brown <broonie@kernel.org>
To: "Alexander Usyskin" <alexander.usyskin@intel.com>,
"Brian Nguyen" <brian3.nguyen@intel.com>,
"Shuicheng Lin" <shuicheng.lin@intel.com>,
"Ashutosh Dixit" <ashutosh.dixit@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"DRM XE List" <intel-xe@lists.freedesktop.org>,
"Dave Airlie" <airlied@redhat.com>,
DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the drm tree
Date: Tue, 10 Feb 2026 21:08:06 +0000 [thread overview]
Message-ID: <aYueNunEXamKtZad@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
/tmp/next/build/drivers/gpu/drm/xe/xe_survivability_mode.c: In function 'xe_survivability_mode_fini':
/tmp/next/build/drivers/gpu/drm/xe/xe_survivability_mode.c:241:17: error: implicit declaration of function 'xe_nvm_fini'; did you mean 'xe_nvm_init'? [-Wimplicit-function-declaration]
241 | xe_nvm_fini(xe);
| ^~~~~~~~~~~
| xe_nvm_init
Caused by the absence of commit
11035eab1b7d8 (drm/xe/nvm: Manage nvm aux cleanup with devres)
from the drm-xe tree. I have ignored this for today, the relevant
commits also seem to have been in the drm tree yesterday.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-02-10 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 21:08 Mark Brown [this message]
[not found] <20250428133013.5ad6b6b7@canb.auug.org.au>
2025-04-28 4:24 ` linux-next: build failure after merge of the drm tree Stephen Rothwell
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=aYueNunEXamKtZad@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@redhat.com \
--cc=alexander.usyskin@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=brian3.nguyen@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=shuicheng.lin@intel.com \
--cc=thomas.hellstrom@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox