From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Danilo Krummrich <dakr@kernel•org>
Cc: Asahi Lina <lina+kernel@asahilina•net>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the drm-nova tree
Date: Tue, 29 Apr 2025 12:45:49 +1000 [thread overview]
Message-ID: <20250429124549.0c0d8b91@canb.auug.org.au> (raw)
In-Reply-To: <aA9F2_yyIGqLFWKU@cassiopeiae>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hi Danilo,
On Mon, 28 Apr 2025 11:09:47 +0200 Danilo Krummrich <dakr@kernel•org> wrote:
>
> On Mon, Apr 28, 2025 at 02:24:36PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the drm-nova tree, today's linux-next build (KCONFIG_NAME)
> > failed like this:
> >
> > x86_64-linux-gnu-ld: vmlinux.o: in function `rust_helper_drm_gem_object_put':
> > (.text+0x1b6cd15): undefined reference to `drm_gem_object_free'
> >
> > Caused by commit
> >
> > be8d1a24798f ("rust: drm: gem: Add GEM object abstraction")
> >
> > I have used the drm-nova tree from next-20250414 for today.
>
> This issue was caused by rust/helpers/drm.c not having the required CONFIG_DRM
> guards.
So the build was x86_64 allmodconfig, so CONFIG_DRM=m. The build works
now, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-04-29 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 4:24 linux-next: build failure after merge of the drm-nova tree Stephen Rothwell
2025-04-28 9:09 ` Danilo Krummrich
2025-04-29 2:45 ` Stephen Rothwell [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=20250429124549.0c0d8b91@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dakr@kernel$(echo .)org \
--cc=lina+kernel@asahilina$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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