From: Mark Brown <broonie@kernel.org>
To: Lyude Paul <lyude@redhat.com>
Cc: Alice Ryhl <aliceryhl@google.com>,
Daniel Almeida <daniel.almeida@collabora.com>,
Janne Grunau <j@jananu.net>, Danilo Krummrich <dakr@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure in final build
Date: Thu, 26 Mar 2026 16:04:23 +0000 [thread overview]
Message-ID: <acVZB6iMoUrV45zH@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 4078 bytes --]
Hi all,
During the final builds, today's linux-next build (arm64 allyesconfig)
failed like this:
error[E0405]: cannot find trait `AlwaysRefCounted` in module
`$crate::types`
--> /tmp/next/build/rust/kernel/drm/gem/mod.rs:42:62
|
42 | unsafe impl $( <$( $tparam_id ),+> )? $crate::types::AlwaysRefCounted
for $type
| ^^^^^^^^^^^^^^^^
| not
| found in
| `$crate::types`
... 308 | impl_aref_for_gem_obj!(impl<T> for Object<T> where T:
DriverObject);
| -------------------------------------------------------------------
| in this macro invocation
|
= note: this error originates in the macro `impl_aref_for_gem_obj` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this trait
|
7 + use crate::sync::aref::AlwaysRefCounted;
|
error[E0277]: the trait bound `Object<T>: aref::AlwaysRefCounted` is
not satisfied
--> /tmp/next/build/rust/kernel/drm/gem/mod.rs:142:41
|
142 | impl<T: DriverObject> IntoGEMObject for Object<T> {
| ^^^^^^^^^ the trait
| `aref::AlwaysRefCounted`
| is not implemented for
| `Object<T>`
|
= help: the following other types implement trait `aref::AlwaysRefCounted`:
Chip<T>
Credential
FwNode
I2cAdapter
I2cClient
Interface
LocalFile
Mm
and 12 others
note: required by a bound in `IntoGEMObject`
--> /tmp/next/build/rust/kernel/drm/gem/mod.rs:96:59
|
96 | pub trait IntoGEMObject: Sized + super::private::Sealed +
AlwaysRefCounted {
| ^^^^^^^^^^^^^^^^
| required
| by this
| bound in
| `IntoGEMObject`
error[E0277]: the trait bound `Object<T>: aref::AlwaysRefCounted` is
not satisfied
--> /tmp/next/build/rust/kernel/drm/gem/mod.rs:320:37
|
320 | impl<T: DriverObject> AllocImpl for Object<T> {
| ^^^^^^^^^ the trait
| `aref::AlwaysRefCounted` is
| not implemented for `Object<T>`
|
= help: the following other types implement trait `aref::AlwaysRefCounted`:
Chip<T>
Credential
FwNode
I2cAdapter
I2cClient
Interface
LocalFile
Mm
and 12 others
note: required for `Object<T>` to implement `IntoGEMObject`
--> /tmp/next/build/rust/kernel/drm/gem/mod.rs:96:11
|
96 | pub trait IntoGEMObject: Sized + super::private::Sealed +
AlwaysRefCounted {
| ^^^^^^^^^^^^^
note: required by a bound in `AllocImpl`
--> /tmp/next/build/rust/kernel/drm/driver.rs:90:47
|
90 | pub trait AllocImpl: super::private::Sealed + drm::gem::IntoGEMObject
{
| ^^^^^^^^^^^^^^^^^^^^^^^
| required by this
| bound in `AllocImpl`
error: aborting due to 3 previous errors
Some errors have detailed explanations: E0277, E0405. For more
information about an error, try `rustc --explain E0277`.
Presumably caused by one of these commits:
442ba16a5a513 (rust: gem: Introduce DriverObject::Args)
e64b9cc293ae7 (rust: drm: Add gem::impl_aref_for_gem_obj!)
I have ignored this for today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-26 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 16:04 Mark Brown [this message]
2026-03-26 17:05 ` linux-next: build failure in final build Danilo Krummrich
-- strict thread matches above, loose matches on Subject: below --
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28 2:18 ` Steven Rostedt
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32 ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20 8:36 ` Alice Ryhl
2026-01-20 10:01 ` Danilo Krummrich
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=acVZB6iMoUrV45zH@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=j@jananu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lyude@redhat.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